This is the mail archive of the
mailing list for the crossgcc project.
Re: GNU toolchain working in other directories ?
- To: email@example.com
- Subject: Re: GNU toolchain working in other directories ?
- From: Mumit Khan <firstname.lastname@example.org>
- Date: Fri, 09 Jul 1999 02:24:18 -0500
- Reply-To: email@example.com
Jeffrey A Law <firstname.lastname@example.org> writes:
> In message <199907090026.UAA08595@light.lexra.com>you write:
> > > > Is it possible to make it work in any
> > > > directory with just changing some environment variables ?
> > > > Thanks
> > > GCC_EXEC_PREFIX
> > For those who use this technique. How do you avoid conflict
> > with any number of GNU compilers that you might also use
> > in the same environment? i.e. The native GNU C compiler will
> > also use this environment variable.
> Nothing good that I'm aware of.
> One could make an alias for the various compilers which first sets a
> suitable GCC_EXEC_PREFIX, calls the desired compiler, then unsets
> GCC_EXEC_PREFIX or something like that.
> Another approach is to use the -B argument to the compiler, which (effectivel
> allows you to specify a prefix on the command line.
Or, you can use what I call "relative pathname fix" authored primarily
by Michael Meissner and Ian Taylor that allows you to freely move around
the tree and have it "just work". I know Jeff knows about all this,
and he knows the caveats, but I don't hear complaints from all the users
who use my win32 binary distribs of egcs.
The patch is slightly different for egcs-1.1.x and gcc-2.95, and both
versions are available in my patchsets.
for not-yet-released gcc-2.95:
After downloading the patchset, look for a file named *relative-path*
and that's the file you want.
It's unsupported, so please don't ask me how or if it works.
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
To remove yourself from the crossgcc list, send
mail to email@example.com with the
text 'unsubscribe' (without the quotes) in the
body of the message.