Re: [avr-gcc-list] Re: avr-gcc-4.0.0 for Win (Jurek Szczesiul)

[Jurek Szczesiul]

Hi.

'Abort' line commented and then compilation ( MinGW32 )
succesful.

I've tried the new toolset (gcc-4.0.0 + binutils-2.15 + avr-libc-1.2.3 )
with some short test projects ( atmega8 , atmega32 ),
using -gdwarf-2 option.

No errors reported but..
when I  load output elf file into AvrStudio - everything stops
with runtime error.

I will try with Cygwin version later, but I'm afraid there are still some 
dwarf2 issues to fix  :-(


Best regards
Jurek S.


----- Original Message ----- 
From: "Björn Haase" <address@hidden>
To: <address@hidden>
Cc: "Jurek Szczesiul" <address@hidden>
Sent: Monday, May 09, 2005 10:58 PM
Subject: Re: [avr-gcc-list] Re: avr-gcc-4.0.0 for Win (Jurek Szczesiul)


Hi,

I have observed the same thing today on a windows box. If you comment out 
completly the "abort" in varasm.c:2139, you could at least compile libgcc. 
(Have a look at my earlier post in the bugzilla thread.)
It seems that the background of the problem is, that within the code at some 
place there is the latent assumption that pointers are at least 4 byte wide. 
Yours,

Björn

Am Montag, 9. Mai 2005 18:55 schrieb Jurek Szczesiul:
> Thanks for advice !
>
> I've tried under Msys/MinGW first.
> Unfortunately, the next error has appeared immediately :
>
> <Msys output>
> make[2]: Entering directory `/inst/avrgcc1/objdir/gcc'
> /inst/avrgcc1/objdir/gcc/xgcc -B/inst/avrgcc1/objdir/gcc/
> -Bc:/AvrSide/gcc-current/avr/bin/ -Bc:/Avr Side/gcc-current/avr/lib/
> -isystem c:/AvrSide/gcc-current/avr/include -isystem c:/AvrSide/gcc-curren
> t/avr/sys-include -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings
> -Wstrict-prototypes -Wmis sing-prototypes -Wold-style-definition  -isystem
> ./include  -DDF=SF -Dinhibit_libc -mcall-prologues -g  -DIN_LIBGCC2
> -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I -I../../gcc-4.0.0/gcc
> -I../../gcc-4. 0.0/gcc/ -I../../gcc-4.0.0/gcc/../include
> -I../../gcc-4.0.0/gcc/../libcpp/include  -DL_muldi3 -c ../
> ../gcc-4.0.0/gcc/libgcc2.c -o libgcc/./_muldi3.o
> ../../gcc-4.0.0/gcc/libgcc2.c:533: internal compiler error: in
> assemble_integer, at varasm.c:2139 Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> make[2]: *** [libgcc/./_muldi3.o] Error 1
> make[2]: Leaving directory `/inst/avrgcc1/objdir/gcc'
> make[1]: *** [stmp-multilib] Error 2
> make[1]: Leaving directory `/inst/avrgcc1/objdir/gcc'
> make: *** [all-gcc] Error 2
> </Msys>
>
> I'll try with Cygwin soon.
>
> Best regards
> Jurek Szczesiul
>
>
>
>
> ----- Original Message -----
> From: "Björn Haase" <address@hidden>
> To: <address@hidden>
> Cc: <address@hidden>
> Sent: Monday, May 09, 2005 7:52 AM
> Subject: Re: avr-gcc-4.0.0 for Win (Jurek Szczesiul)
>
>
> What You are observing is the known problem
>
> [Bug debug/19885] [4.0/4.1 Regression] avr dwarf-2 support is broken for
> head 4.0/4.1
>
> Look at
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19885
>
> . There you'll find a patch with which 4.0.0 should build. So far, I did
> not test, actually, whether the debugging information then is ok. I did not
> have access to a Windows host with avrstudio last week. So any report would
> be welcome.
>
> Best regards,
>
> Björn
>
>
>
>
> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-gcc-list