a few short questions about the development cross-lfs book

Robert P. J. Day rpjday at mindspring.com
Tue Nov 1 07:28:54 PST 2005

  (aside:  i'm comparing the instructions in the book to the actual
code in the "crosstool" utility, and am just trying to reconcile where
there are differences so i understand whether those differences are
meaningful are not.  for my example i'm using the 32-bit PPC book

  to begin with, some questions about chapter 5.

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

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?

  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?

  more later, i'm sure.


More information about the cross-lfs mailing list