From: Alan Modra <amodra@bigpond.net.au>
To: Martin Haupt <martinhaupt@sofortstart.de>
Cc: binutils@sourceware.org
Subject: Re: Binutils 2.17: configure in libiberty does not find stdlib.h -> build failure
Date: Mon, 16 Apr 2007 07:44:00 -0000 [thread overview]
Message-ID: <20070416044258.GS28088@bubble.grove.modra.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2007-04-16 4:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 20:32 Martin Haupt
2007-04-16 7:44 ` Alan Modra [this message]
2007-04-16 21:07 ` Martin Haupt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070416044258.GS28088@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sourceware.org \
--cc=martinhaupt@sofortstart.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).