In LFS6.4 step 5.8.The dynamic linker in specs and the one in use is not the same.But why?

Chris Staub chris at beaker67.com
Wed Feb 3 08:23:36 PST 2010


On 02/03/2010 06:20 AM, haiye1018 wrote:
> In LFS6.4 step 5.8.When having adjusted the toolchain,the dynamic linker
> in specs and in use(gcc -print-libgcc-file-name) is not the same.But
> why,despite the construction is ok(when chroot to ,all other
> constructions is ok )?
>
>
> (gcc -print-libgcc-file-name is
> /home/lfs/mnt/tools/bin/../lib/gcc/i686-pc-linux-gnu/4.3.2/libgcc.a)
> cat `dirname $(gcc -print-libgcc-file-name)`/specs:
>
>
> *link_emulation:
> elf_i386
>
> *dynamic_linker:
> %{muclibc:%{mglibc:%e-mglibc and -muclibc used
> together}/lib/ld-uClibc.so.0;:/tools/lib/ld-linux.so.2}
>
> *link_command:
> %{!fsyntax-only:%{!c:%{!M:%{!MM:%{!E:%{!S: %(linker) %l %{pie:-pie} %X
> %{o*} %{A} %{d} %{e*} %{m} %{N} %{n} %{r}
>
>
> when running commmand gcc -dumpspecs | grep ld-linux.so.2 ,the result is:
>
> %{muclibc:%{mglibc:%e-mglibc and -muclibc used
> together}/lib/ld-uClibc.so.0;:/lib/ld-linux.so.2}
>
> Any one can tell me why?I think I don't comprehend whole
> progress,although I can run these commands correctly.
>
>

If I understand correctly, you are saying you get different results when 
viewing the specs files, and when running "gcc -dumpspecs". The reason 
for this is simply that "gcc -dumpspecs" shows GCC's default specs, 
which at this stage still looks at /lib, while the first command is 
looking at the specs file in /tools, which overrides GCC's internal specs.



More information about the lfs-support mailing list