Re: [avr-gcc-list] avr-libc-20020203 patches for c++ support

[Theodore A. Roth]

I see the same problem. Attached is a patch on the latest patch which got
things to work for me.

Ted

On Fri, 8 Mar 2002, Jason Kyle wrote:

>
>>Attached is a new patch for avr-libc with the added include files
>>needed. I tried to send this last night but it didn't go on to the list
>>as it was larger than 100k. Its gziped now.
>>
>>Thanks for testing that under cygwin, I have not had a chance to
>>re-compile it under cygwin to test it. Could you post to the list what
>>needs to be done under cygwin so other prople can do it too?
>
>Ok, avr-libc-20020203 with c++ patch builds fine (with the missing files 
>added to the patch).  When I try to compile some previously good code which 
>was fine with gcc-3.0.3 (without m128 and c++ patches) I have a 
>problem.  See below
>
>avr-gcc -mmcu=at90s2313 -Wall -W -Wstrict-prototypes  -Os -mtiny-stack 
>-mcall-prologues -mrtl -g   -c -o pavr.o pavr.c
>avr-gcc pavr.o -o a.out -mmcu=at90s2313 -Wl,-M > a.map
>/usr/local/lib/gcc-lib/avr/3.0.4/../../../../avr/lib/crts2313.o: In 
>function `__c_startup__':
>../../libc/gcrt1.S:161: undefined reference to `_data_load_start'
>../../libc/gcrt1.S:162: undefined reference to `_data_load_start'
>../../libc/gcrt1.S:179: undefined reference to `_data_end'
>make: *** [a.out] Error 1
>
>
>You can try this yourself, just run make in uisp-20011025/pavr and let me 
>know if you see the same result.
>

avr-libc-patch.diff
Description: Text document