Re: [avr-gcc-list] Trunk broken for AVR Target?

[Weddington, Eric]

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of Boyapati, Anitha
> Sent: Wednesday, June 08, 2011 8:11 AM
> To: address@hidden
> Subject: [avr-gcc-list] Trunk broken for AVR Target?
> 
> 
> 
> Hi,
> 
> I am trying to build recent snapshot gcc-4.7-20110604 without any patches.
> Build fails for libgcc2.c. Unless I am doing something wrong, I think the
> trunk is broken. Can someone confirm this?
> 
> 
> --------------------------------------------------------------
> checking for suffix of object files... configure: error: in
> `/home/anitha/gcc-4.7-20110604/objdir/avr/libgcc':
> configure: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.
> make[1]: *** [configure-target-libgcc] Error 1
> 
> --------------------------------------------------------------

That is an error in your setup; nothing to do with the trunk. I've ran into 
that error multiple times, and for the life of me it escapes me right now what 
you have to do to get it fixed..... You might want to do some googling on that 
error.





> 
> 
> Further probing shows that dwarf-2 information generation is affected.
> 
> --------------------------------------------------------------
> configure:3056: /home/anitha/gcc-4.7-20110604/objdir/./gcc/xgcc -
> B/home/anitha/gcc-4.7-20110604/objdir/./gcc/ -B/usr/local/avr/bin/ -
> B/usr/local/avr/lib/ -isystem /usr/local/avr/include -isystem
> /usr/local/avr/sys-include    -o conftest -g -O2   conftest.c  >&5
> conftest.c: In function 'main':
> conftest.c:16:1: internal compiler error: in
> compute_frame_pointer_to_fb_displacement, at dwarf2out.c:18342
> 
> --------------------------------------------------------------
> 
> 
> I have done some more analysis on the origin of this error, but before
> that I think it is a good idea if someone can confirm that the build is
> broken.

There is already a bug reported in the GCC Bugzilla about DWARF2 not working 
for the AVR, specifically for 4.6.* and 4.7/trunk. Please double check that 
you're running into the same bug. No, this bug is not fixed yet. I already 
informed Vidya about this bug some time back.

Eric Weddington