> > Anyone have a fix, workaround, or other suggestion?
>
> Yes don't use --with-dwarf2 :).
Only a short term workaround... ;)
> This is PR 26504:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26504
Comment #8 there seems on-the-mark, so the PR 26015 fix has
two half-confirmations now:
> Also
On Jul 11, 2006, at 4:49 AM, David Brownell wrote:
Hi,
Anyone have a fix, workaround, or other suggestion?
Yes don't use --with-dwarf2 :).
This is PR 26504:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26504
Also someone should try the patch in PR 26015:
http://gcc.gnu.org/bugzilla/show_bug
David Brownell wrote:
/home/tux/avr/gcc/obj-avr/./gcc/xgcc -B/home/tux/avr/gcc/obj-avr/./gcc/
-B/usr/local/avr/avr/bin/ -B/usr/local/avr/avr/lib/ -isystem
/usr/local/avr/avr/include -isystem /usr/local/avr/avr/sys-include -O2 -O2 -g
-O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Ws
Hi,
I was building a AVR cross compiler from current GCC trunk, and got an error.
Build system was Ubuntu 6.06 on an Athlon, using the latest from CVS binutils
but otherwise configured exactly as shown in
http://www.nongnu.org/avr-libc/user-manual/install_tools.html
The assertion failure that
