This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: $tooldir
- To: law at cygnus dot com
- Subject: Re: $tooldir
- From: Bill Currie <bcurrie at tssc dot co dot nz>
- Date: Thu, 21 Jan 1999 14:36:04 +1300
- CC: manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de, oliva at dcc dot unicamp dot br, egcs at egcs dot cygnus dot com
- Organization: NZ Telecommincations Systems Support Center
- References: <3423.916875497@hurl.cygnus.com>
Jeffrey A Law wrote:
>
> In message <36A6398F.3111C7E4@tssc.co.nz>you write:
> > [$tooldir discussion]
> >
> > If gcc can get at it's spec file, why not code all the tool locations in
> > the spec file rather than the program?
> Ewww. Plus things can change dynamically. The compiler still needs to work
> if I (for example) delete "as" from the tooldir -- it would have to fall back
> to its existing built-in search paths, and if those fail the user's path.
>
> Certainly could be done, I don't see the benefit.
Fair enough, it just occured to me while going over the other messages
and I was wandering if it had ever been considered. As to the benifit?
Um, easy re-configurability of where to look for the other tools.
Also, isn't the spec file hard coded into gcc as a default and dumped
out for easy modification? If the existing built-in search paths are
moved to the spec file, then you still have the same functionality as
before, just easily modified (and easily broken as well, I admit).
Bill
--
Leave others their otherness