$(build_tooldir)/lib (was Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html)

[H . J . Lu]

On Fri, Jul 21, 2000 at 10:46:30AM -0700, Geoff Keating wrote:
> > Date: Fri, 21 Jul 2000 07:49:20 -0700
> > From: "H . J . Lu" <hjl@lucon.org>
> 
> > Exactly. BTW, you won't see it if you use newlib. It is too bad not
> > many people use glibc for cross compiling instead of newlibc. At least,
> > they don't maintain gcc :-(. It is a fun to build a complete cross
> > compiler from Linux/ia32 to Linux/ia64 :-). You will see a few build
> > problems.
> 
> Actually, at Red Hat we cross-compile to various versions of linux all
> the time, and our release engineering people don't see any particular
> problems that would be fixed by this patch.

Well, it starts all over again :-). When you build the Linux cross
compiling environment, which includes gcc, ld, as, libiberty and
libstdc++ in one pass, how do you find the crt files under
$(build_tooldir)/lib?  They are needed at least by the target version
of libiberty. Gcc finds them by

$(prefix)/lib/gcc-lib/cpu-vendor-os/version/../../../../cpu-vendor-os/lib

When you build the new verion of the compiler the first time,

$(prefix)/lib/gcc-lib/cpu-vendor-os/version

may not exist. Gcc won't find those crt files and the build will fail
at least in the target version of libiberty. That is what
-B$(build_tooldir)/lib/ is used for.



H.J.