This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Binutils 2.17: configure in libiberty does not find stdlib.h -> build failure
- From: Alan Modra <amodra at bigpond dot net dot au>
- To: Martin Haupt <martinhaupt at sofortstart dot de>
- Cc: binutils at sourceware dot org
- Date: Mon, 16 Apr 2007 14:12:58 +0930
- Subject: Re: Binutils 2.17: configure in libiberty does not find stdlib.h -> build failure
- References: <op.tqsghpexh21ff2@computername>
On Sat, Apr 14, 2007 at 09:30:51PM +0200, Martin Haupt wrote:
> I am currently trying to build diy-linux with a crosstool compiler on a
> lfs 6.2 live system (64bit).
> But the first binutils build fails in libibery/cplus-dem.c because
> stdlib.h is missing (it's there and the compiler finds it). I looked
> through the logs and found out that configure in the libiberty directory
> is the only configure which is not finding stdlib.h (and other standard
> includes)!
That will be because Daniel made libiberty/configure.ac invoke
AC_PROG_CPP_WERROR, thus turning cpp warnings into errors.
See http://sourceware.org/ml/binutils/2003-09/msg00416.html
configure in other dirs doesn't do this.
> Now there is a strange spot in the config.log:
>
> configure:3691: checking for stdlib.h
> configure:3704: x86_64-unknown-linux-gnu-gcc -Wl,-dynamic-linker
> -Wl,/cross-tools/x86_64-unknown-linux-gnu/sys-root/lib64/ld-linux-x86-64.so.2
> -E conftest.c
> x86_64-unknown-linux-gnu-gcc: -dynamic-linker: linker input file unused
> because linking not done
> x86_64-unknown-linux-gnu-gcc:
> /cross-tools/x86_64-unknown-linux-gnu/sys-root/lib64/ld-linux-x86-64.so.2:
> linker input file unused because linking not done
> configure:3710: $? = 0
It is indeed strange that you have linker options being passed to your
cpp. How are you configuring? Do you specify CPP or CPPFLAGS,
perhaps via your environment?
--
Alan Modra
IBM OzLabs - Linux Technology Centre