[uClibc]Anyone found the cause...

[Thomas Cameron]

Hello again,
	As far as I can tell, the issue appears when the compile of
libiberty (sp?) occours.  It is attempting to compile against "crt1.o",
which obviously is not being found in /lib or /usr/lib of the building
system.  In actuality, I had a crt1.o in /usr/lib, but it was not built
by the buildroot process, AFAIK.

	So, now it just comes down to trying to figure out why the
system fails at this when using custom flags/options for uClibc, and not
any other time.  I recompiled the systm straight from CVS again last
night, and it went flawlessly again...so, I know that it has nothing to
do with me being out-of-sync from CVS, or anything like that.

Thanks for any help!
Thomas Cameron
CEI Systems, Inc.


-----Original Message-----
From: Thomas Cameron 
Sent: Monday, January 06, 2003 7:12 PM
To: Goetz Bock; uclibc at uclibc.org
Cc: Erik Andersen
Subject: Re: [uClibc]Anyone found the cause...


Hello gang,
	Yes, I too read through the README file, and have had the link
there.  
Depending on what packages you choose to compile, things work great, but
as 
soon as you appempt to build a development environment for the "target" 
system (which I use on my development system to ease the compiling of
other 
semi-stupid and stupid `./configure` based packages.  It works well, as
long 
as I grab buildroot from CVS and change NONE of my settings.

	I am attaching a file that contails the last 5 lines from all
config.log 
files so that Erik can take a look at it.  In addition, I have included
the 
config file that uClibc should be using.  Out of chance, could this be 
because the uClibc libraries that are being built (it's done twice if
you 
build a toolchain & uClibc for the target) are different?  Maybe one is 
getting the proper config and other options (applied via a nifty perl 
command)?  Maybe one of them is actually going to the wrong place, and
thus 
the compile of gcc is going awry?  Just a thought.

Thanks all!
Thomas Cameron

On Monday 06 January 2003 06:01 pm, Goetz Bock wrote:
> On Mon, Jan 06 '03 at 15:11, Erik Andersen wrote:
> > > 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. [ ... ]
> > > configure: error: installation or configuration problem: C
compiler
> > > cannot create executables.
>
> first of all I want to welcome Thomas to the club, I'm hafing this 
> problem since weeks/months ... but never got any reply to my mails :-/
>
> > Generally, this happens when people fail to read and follow the 
> > direction in the "NOTE" section of the buildroot README file. :)
>
> bash > ls -l /lib/ld-*
> -rwxr-xr-x    1 root     root       484281 Oct 11 10:19
/lib/ld-2.1.3.so*
> lrwxrwxrwx    1 root     root           11 Feb 24  2002
/lib/ld-linux.so.2
> -> ld-2.1.3.so* lrwxrwxrwx    1 root     root           65 Nov 15
03:06
> /lib/ld-uClibc.so.0 ->
> /home/DEVEL/uclibc/buildroot/build/staging_dir/lib/ld-uClibc.so.0* 
> Just to ilustrate I read the readme but it just does not help :-(
>
> > 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,
>
> I'm not even triing to do a crosscompile, only uclibc for i386 on 
> i386.
>
> But the tusxscreen buildroot does not work for me either, same error 
> ...