[uClibc]Anyone found the cause...
Erik Andersen
andersen at codepoet.org
Mon Jan 6 22:11:54 UTC 2003
On Mon Jan 06, 2003 at 03:39:14PM -0500, Thomas Cameron wrote:
> Hello all,
>
> I am _really_ trying to figure out the cause of this problem. I am compiling
> the buildroot environment with the build tools for my development
> environment. I use some custom settings on uClibc, so that I do not get LFS
> or WCHAR support. It seems that every time I attempt to build my environment
> with any customizations to uClibc, it fails while building GCC. Here is the
> output I get...
>
> --- snip ---
> checking whether the C compiler
> (/home/tom/development/buildroot.krd/build/gcc-final/gcc/xgcc
> -B/home/tom/development/buildroot.krd/build/gcc-final/gcc/
> -B/home/tom/development/buildroot.krd/build/staging_dir/i386-linux/bin/
> -B/home/tom/development/buildroot.krd/build/staging_dir/i386-linux/lib/
> -isystem
> /home/tom/development/buildroot.krd/build/staging_dir/i386-linux/include -g
> -Os ) works... no
> configure: error: installation or configuration problem: C compiler cannot
> create executables.
Generally, this happens when people fail to read and follow the
direction in the "NOTE" section of the buildroot README file. :)
Basically, GNU configure doesn't realize you are cross-compiling,
and is trying to compile and run test apps on your build system.
configure can be terribly stupid that way. Anyways, the solution,
is to add a symlink in /lib so that the test apps will in fact be
able to run. See the buildroot README file for more details,
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
More information about the uClibc
mailing list