This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


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: toolchain's sysroot via environment


On Saturday, July 17, 2010 13:08:35 Rod Nussbaumer wrote:
> Mike Frysinger wrote:
> > On Thursday, July 15, 2010 20:08:04 Arno Schuring wrote:
> >> Regarding your first question: that's not possible - the sysroot paths
> >> are compiled-in. If it were just the paths, if would not be much of a
> >> problem - but the toolchain components (compiler, linker) are also
> >> compiled differently based on the libraries available in the sysroot.
> > 
> > the *default* sysroot paths are compiled in, but you can change it on the
> > command line on the fly
> 
> This relates to a problem of mine that was solved here a week or so ago.
> One of the *default* paths was to a directory for which the user (of the
> cross compiler) had no read access ($HOME of the toolchain builder). The
> result was that the compiler bombed. Is there a way of *removing* a path
> from a tool's list of places to find it's stuff? When you say 'you can
> change it on the command line', does the meaning of 'change' only
> include adding paths?

build a proper relocatable toolchain and the default path is always based on 
the toolchain, not the build location (afaik)
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.


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