This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [discuss] Re: --with-sysroot required when building 32->64 bitcrosstoolchain? (was: building a cross-compiler is hard)
- From: Daniel Kegel <dkegel at google dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: Daniel Kegel <dank at kegel dot com>, discuss at x86-64 dot org, binutils at sources dot redhat dot com
- Date: Wed, 07 Jan 2004 17:56:50 -0800
- Subject: Re: [discuss] Re: --with-sysroot required when building 32->64 bitcrosstoolchain? (was: building a cross-compiler is hard)
- References: <3FFC8E2C.9010107@kegel.com> <20040107230644.GA2926@nevyn.them.org>
Daniel Jacobowitz wrote:
On Wed, Jan 07, 2004 at 02:54:36PM -0800, Daniel Kegel wrote:
so I guess ld doesn't obey -L for that file?!
Yes. It doesn't matter that it's a 32/64-bit cross environment, it's
still a cross environment to a hosted target. DT_NEEDED are only
searched via -rpath-link and SEARCH_DIR.
It matters that it's a 32/64 bit cross environment because otherwise
I wouldn't need --with-sysroot...
You can use --with-sysroot for binutils without using it for GCC. It's
not necessarily a good idea though.
I'm trying it throughout. It's hard to figure out how to use, though.
I had been jimmying things so there is no /usr, i.e. so all libraries are
in $PREFIX/lib, all includes in $PREFIX/include, as is customary when
building cross-compilers. But I get the feeling that --with-sysroot wants
me to do things the LSB way, with a split between /lib and /usr/lib,
so I'm giving that a shot. Needless to say, this is painful. I'm
currently stuck building crtbegin.o because for some reason
xgcc is being told to look in $PREFIX/include... gotta figure out
where I missed adding a /usr ... grumble.
- Dan