a few short questions about the development cross-lfs book

Jim Gifford lfs at jg555.com
Tue Nov 1 07:53:58 PST 2005

Robert P. J. Day wrote:

>5.2  Build CFLAGS
>  crosstool also insists on unsetting LD_LIBRARY_PATH, which i *have*
>noticed will cause problems if you just happen to be in the directory
>with the cross-compiled library and running a host command tries to
>use that library (or something similar to that, this is from memory).
>  the relevant code from the crosstool script is:
>	test -z "${LD_LIBRARY_PATH}" || abort  "glibc refuses to build if
>	LD_LIBRARY_PATH is set.  Please unset it before running this script.
>  is this worth adding to that page?  or does CLFS not run into this
We don't run into this issue at all.

>5.5  Cross Binutils-2.16.1
>  unlike what's suggested here, crosstool uses neither the
>--with-lib-path option nor the --enable-shared option for that initial
>build of binutils.  thoughts?
We build dynamic libraries, cross-tool does not.

>  also, at the end of that page, there is an explicit copy of
>libiberty.h.  i've successfully built toolchains without ever copying
>that header file.  are you sure it's necessary?
Maybe it actually gets copied now, I'll have to check into that one.

jim at linuxfromscratch.org
lfs at jg555.com

LFS User # 2577
Registered Linux User # 299986

More information about the cross-lfs mailing list