Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx> writes:
> Yes, but I tried without --disable-libiberty and without C++!
>
> I just restarted with configure in a new directory and it is
> reproducible.
>
> Here my options:
>
> $ ../gcc-4.6.0/configure \
> --prefix=/usr/local/exp/gcc-4.6.0/ \
> --enable-languages=c \
> --target=arm-elf \
> --program-prefix=arm-elf- \
> --with-sysroot=/usr/local/build/gcc/sysroot/ \
> --enable-interwork --enable-multilib \
> --enable-target-optspace --with-float=soft \
> --with-zlib=no \
> --disable-libssp \
> --disable-shared
>
> Is it correct to disable C++ by giving a --enable-languages list
> with is simply not includeing c++?
Yes. If this tries to build the target libiberty, I think that is a
bug.
> Then I tried:
>
> $ make inhibit_libc=true
That won't help with libiberty, only with libgcc.
> After some hours ("felt-time") compilation time I get:
>
> make[2]: Leaving directory `...gcc/gcc-4.6.0-arm/arm-elf/libquadmath'
> Checking multilib configuration for libiberty...
> mkdir -p -- arm-elf/libiberty
> Configuring in arm-elf/libiberty
> ...
> checking for library containing strerror... configure:
> error: Link tests are not allowed after GCC_NO_EXECUTABLES.
> make[1]: *** [configure-target-libiberty] Error 1
>
> How do I disable libiberty for target?
> My target has no strerror (not even errno).
I guess there isn't a way.
This is a bug but it doesn't matter, in that everything will still
work.
Ian
