Re: $tooldir

[Donn Terry <donn at interix dot com>]

Alexandre Oliva wrote:
> 
> On Jan 26, 1999, Jeffrey A Law <law@hurl.cygnus.com> wrote:
> 
> >   In message <orww2izgoa.fsf@araguaia.dcc.unicamp.br>you write:
> >> The problem is that sometimes I'd like to try a new assembler or a new
> >> linker, and I wouldn't like to have to rebuild gcc in order to try
> >> them, and I don't want to install versions of as and ld that might
> >> break egcs while other users are using it.
> >>
> >> So I came up with the following idea: if any -Bdir argument is given,
> >> gcc would search for as and ld in those directories before trying to
> >> use the hard-coded pathnames.
> >>
> >> Does this sound reasonable?
> > Yes/no.  Part of me sez, if a path was spec'd at configure time, then it
> > should override everything, even -B args.
> 
> > Your suggested change would have the effect of overriding the configured
> > assembler during bootstraps.
> 
> Wouldn't that be good?  Then, it would use the build-tooldir as even
> though it was not installed it.  I agree that this might have other
> unwanted side-effects, though.

-B should take precedence; it's something the user (OK, "I") specified,
so it should be presumed to be more recent (and thus, "more right").

In my case, I do a full compiler path bootstrap (compiler, gas,
ld), and I want to be able to build subseqent pieces with the
pieces I just built (without installing them).  I use -B to
achieve that now (non-egcs gcc).

Donn
-- 

===================================================
Donn Terry                  mailto:donn@interix.com
Softway Systems, Inc.        http://www.interix.com
2850 McClelland Dr, Ste. 1800   Ft.Collins CO 80525
Tel: +1-970-204-9900           Fax: +1-970-204-9951
===================================================