probs cross-building current libstdc++-v3, because of need to link?

[cgd@broadcom.com]

At Mon, 11 Aug 2003 23:56:20 -0700, Eric Christopher wrote:
> > if you get an absolute path, you'll lose like i did methinks.  8-)
> 
> Why does yours give an absolute path? Or is the way that the OS builds
> ld a little weird? (not that i've looked)

because gcc -print-file-name=ld happens to give an absolute path.

probably because for the configure/build of those tools, i did a
binutils configure/build/install followed by a gcc
configure/build/install.  I use --with-gnu-as / --with-gnu-ld for that
configure, but no explicit paths.  (i.e., those arguments, no
=anything, etc.)

Anyway, I don't really know *why* but that's how it comes out, and my
native compilers seem to work just fine.  That *is*, after all, a
good linker for native use.


I think if you want to simulate my experience, if you ran the gcc
top-level configure with "env LD=/usr/bin/ld configure..." that would
have the "desired" effect for your environment.



cgd