On Mon, 6 Dec 2010 02:13:08 -0700
Dax Mickelson <[email protected]> wrote:
> Well, I've made it this far! :-)
>
> I'm attempting to check that I've properly pointed to the new dynamic
> linker (in /tools) with the test shown on page 42. I'm failing the
> test.
>
> This is my first time going through the LFS book. Can someone
> interpret the output of the "specs" code and the "test dynamic
> linker" code and see what is wrong? (My guess is the too many
> "../../../" shown but if so I don't know how to fix it. Do I just
> start over? How do I clean up in order to start over?)
>
> <snip>
> l...@lfsdevmachine:/mnt/lfs/sources$ rm -rf specs
> l...@lfsdevmachine:/mnt/lfs/sources$ SPECS=`dirname $($LFS_TGT-gcc
> -print-libgcc-file-name)`/specs
> l...@lfsdevmachine:/mnt/lfs/sources$ $LFS_TGT-gcc -dumpspecs | sed \
> > -e 's@/lib\(64\)\?/ld@/tools&@g' \
> > -e "/^\*cpp:$/{n;s,$, -isystem /tools/include,}" > $SPECS
> l...@lfsdevmachine:/mnt/lfs/sources$ echo "New specs file is: $SPECS"
> New specs file is: ./specs
This seems to suggest that
`dirname $($LFS_TGT-gcc -print-libgcc-file-name)` gave no output. Was
the variable $LFS_TGT set in the environment?
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
