From: "Martin Haupt" <martinhaupt@sofortstart.de>
To: binutils@sourceware.org
Subject: Binutils 2.17: configure in libiberty does not find stdlib.h -> build failure
Date: Sat, 14 Apr 2007 20:32:00 -0000 [thread overview]
Message-ID: <op.tqsghpexh21ff2@computername> (raw)
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)!
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
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #include <stdlib.h>
configure:3731: result: no
You see that there is a return value of 0 which should be fine imho.
configure claims now there would be no such file. I think configure is
doing wrong here.
I hope somebody can help me.
Martin Haupt
System:
Lfs live cd 6.2-5
Kernel: 2.6.16.38-64bit
GCC: 4.1.1 (crosstool)
Binutils: 2.16.1 (crosstool)
Glibc: 2.3.6 (with tls) (crosstool)
Target: x86_64-unknown-linux-gnu
Binutils: 2.17
DIY: CVS Release April 10th, 2007
$CC: "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"
next reply other threads:[~2007-04-14 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 20:32 Martin Haupt [this message]
2007-04-16 7:44 ` Alan Modra
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=op.tqsghpexh21ff2@computername \
--to=martinhaupt@sofortstart.de \
--cc=binutils@sourceware.org \
/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).