Configure eglibc-2_13 and build-libc-startfiles library linking

[Kyle Grieb <grieb dot kyle at gmail dot com>]

During ct-ng build.

/home/tc/data/package/toolchain-build/x86_64-pc-linux-gnu/build/gcc-core-static/libexec/gcc/x86_64-pc-linux-gnu/4.5.2/cc1:
error while loading shared libraries: libmpfr.so.4: cannot open shared
object file: No such file or directory

configure:2501: error: in
`/home/tc/data/package/toolchain-build/x86_64-pc-linux-gnu/build/build-li
bc-startfiles': configure:2503: error: cannot compute suffix of object
files: cannot compile

./toolchain-build/x86_64-pc-linux-gnu/build/build-mpfr/.libs/libmpfr.so.4.0.0
./toolchain-build/x86_64-pc-linux-gnu/build/build-mpfr/.libs/libmpfr.so.4
./toolchain-build/x86_64-pc-linux-gnu/build/build-mpfr/.libs/libmpfr.so
./toolchain-build/x86_64-pc-linux-gnu/build/build-mpfr/.libs/libmpfr.lai
./toolchain-build/x86_64-pc-linux-gnu/build/build-mpfr/.libs/libmpfr.la
./toolchain-build/x86_64-pc-linux-gnu/build/build-mpfr/libmpfr.la
./toolchain/usr/local/x86_64-pc-linux-gnu/lib/libmpfr.so.4.0.0
./toolchain/usr/local/x86_64-pc-linux-gnu/lib/libmpfr.so.4
./toolchain/usr/local/x86_64-pc-linux-gnu/lib/libmpfr.so
./toolchain/usr/local/x86_64-pc-linux-gnu/lib/libmpfr.la

I think a solution is with LD_LIBRARY_PATH/LDFLAGS. I am under the
impression that crosstool-ng declares and exports all related
environment paths/variables/flags internally so as to allow built files
to be found and used.

Also, I notice that --with-headers= contains $TARGET string twice for
the path. Is this an incorrect path, TARGET twice? Maybe this is just
for during the build process (still have not completed successfully).

Why is #crosstool-ng vacant?!
-- 
Kyle Grieb

Attachment: config.log
Description: Text document

Attachment: .config
Description: Text document

--
For unsubscribe information see http://sourceware.org/lists.html#faq