Revitalizing this old thread.

On Fri, Nov 20, 2015 at 9:20 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> "Thompson, David" <dthompson2@worcester.edu> skribis:
>
>> Not quite.  The avr-gcc build only provides a single version of
>> libgcc.a, whereas Debian's avr-gcc provides a separate libgcc.a for
>> each supported AVR family (avr2, avr3, avr35, etc.)  Mark thought it
>> might be the fault of the --disable-multilib configure flag, so I
>> removed it but it didn't solve anything.  I'm not sure what to do now.
>> I have no idea what flag or patch could be signalling to the gcc build
>> system that it shouldn't try to compile libraries for all of the
>> various AVR models.
>
> Are you sure the removal of --disable-multilib was effective?
>
> Otherwise no specific idea.  :-/ We’ll have to thoroughly study the
> (avr-)gcc doc.

With much help from Manolis, we were finally able to overcome the
multilib issue!  But there's another roadblock: avr-libc doesn't
build:

avr-gcc -DHAVE_CONFIG_H -I. -I../../../../avr-libc-2.0.0/avr/lib/avr2
-I../../..  -I../../../../avr-libc-2.0.0/common
-I../../../../avr-libc-2.0.0/include -I../../../include
-I../../../../avr-libc-2.0.0/common
-I../../../../avr-libc-2.0.0/include -I../../../include -x
assembler-with-cpp  -mmcu=avr2 -D__COMPILING_AVR_LIBC__   -MT abort.o
-MD -MP -MF .deps/abort.Tpo -c -o abort.o
../../../../avr-libc-2.0.0/libc/stdlib/abort.S
In file included from
/gnu/store/8m00x5x8ykmar27s9248cmhnkdb2n54a-glibc-2.22/include/features.h:389:0,
                 from
/gnu/store/8m00x5x8ykmar27s9248cmhnkdb2n54a-glibc-2.22/include/limits.h:25,
                 from ../../../../avr-libc-2.0.0/libc/stdlib/strtol.c:33:
/gnu/store/8m00x5x8ykmar27s9248cmhnkdb2n54a-glibc-2.22/include/gnu/stubs.h:7:27:
fatal error: gnu/stubs-32.h: No such file or directory
 # include <gnu/stubs-32.h>
                           ^
compilation terminated.


I don't know why it's including headers from the host system's libc.
Manolis was able to get past it by including a cross-libc built for
i686.  Does this seem wrong to anyone else?  Any thoughts on what
might be going on here?

We're closer than ever to having a working AVR toolchain.  I hope we
can iron out these last wrinkles.  Attached is the WIP code for the
toolchain.

- Dave