This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: --with-sysroot=/ linker search path

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
search path.

Alan Modra
Australia Development Lab, IBM

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]