This is the mail archive of the
mailing list for the binutils project.
Re: --with-sysroot=/ linker search path
- From: Alan Modra <amodra at gmail dot com>
- To: Hans-Peter Nilsson <hp at bitrange dot com>
- Cc: binutils at sourceware dot org
- Date: Thu, 5 Sep 2013 12:02:52 +0930
- Subject: Re: --with-sysroot=/ linker search path
- Authentication-results: sourceware.org; auth=none
- References: <20130903151753 dot GW3430 at bubble dot grove dot modra dot org> <alpine dot BSF dot 2 dot 02 dot 1309041709260 dot 58818 at arjuna dot pair dot com> <20130904234817 dot GY3430 at bubble dot grove dot modra dot org> <alpine dot BSF dot 2 dot 02 dot 1309042126580 dot 92727 at arjuna dot pair dot com>
On Wed, Sep 04, 2013 at 09:32:31PM -0400, Hans-Peter Nilsson wrote:
> On Thu, 5 Sep 2013, Alan Modra wrote:
> > On Wed, Sep 04, 2013 at 05:36:19PM -0400, Hans-Peter Nilsson wrote:
> > > So cross targets lose $tooldir/lib?
> > Yes.
> > > $tooldir/lib is where all
> > > libraries and objects are installed for my non-sysrooted cross
> > > builds (actually, that's what I hoped we could make the default
> > > for builds without --with-sysroot some time in the future),
> > How ever does that work? I mean, given an x86_64-linux host with
> > default configured binutils, the directory we're taking about is
> > /usr/local/x86_64-linux-gnu/lib, and you would have this used by
> > any cross target?
> No, the $target in $tooldir here is the cross target.
> ...but that's obvious, there must be something I'm missing.
> Double-checking: we're talking about the contents of the
> SEARCH_DIR parentheses in the default linker script for a cross
> build, right?
Oh, I see the confusion. I'm talking about a native linker with cross
support via --enable-targets. Your cross linker is one just for a
single target, configured with --target. In that case TOOL_DIR is
indeed defined for the target so you won't lose the $tooldir/lib
Australia Development Lab, IBM