[lfs-support] Cannot build test program in 6.10

Ken Moffat zarniwhoop at ntlworld.com
Sun Jan 6 10:10:16 PST 2013


On Sun, Jan 06, 2013 at 11:57:41AM -0600, Bruce Dubbs wrote:
> First add a subject
> 
> matthew gruda wrote:
> > now i got up to 6.10 and i tried:
> > echo 'main(){}' > dummy.c
> > cc dummy.c -v -Wl, --verbose
> >
> > and got:
> 
> Lets break this down:
> 
> > GNU assembler version 2.22 (x86_64-unknown-linux-gnu) using BFD version
> > (GNU Binutils) 2.22
> 
> > COMPILER_PATH=/tools/libexec/gcc/x86_64-unknown-linux-gnu/4.7.1/:
>  > /tools/libexec/gcc/x86_64-unknown-linux-gnu/4.7.1/:
>  > /tools/libexec/gcc/x86_64-unknown-linux-gnu/:
>  > /tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/:
>  > /tools/lib/gcc/x86_64-unknown-linux-gnu/:
>  > /tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/
>  >   ../../../../x86_64-unknown-linux-gnu/bin/
> 
> This indicates to me that the previous sed was not done properly.  The 
> /tools portions should have been removed.
> 
 Nice spotting, Bruce.  I overlooked that and was about to reply on
the part below.

> > /tools/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/
>  >    ../../../../x86_64-unknown-linux-gnu/bin/ld:
> > cannot find : No such file or directory
> > collect2: error: ld returned 1 exit status
> >

 This appears to show something went wrong with fixing up ld. The
"cannot find" message implies the change to ld went wrong.  It should
be a symlink to /tools/bin/ld (and that should now be the new
version).

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce



More information about the lfs-support mailing list