From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: law@cygnus.com
Cc: Manfred Hollstein <manfred@s-direktnet.de>, egcs@egcs.cygnus.com
Subject: Re: $tooldir
Date: Sun, 28 Feb 1999 22:53:00 -0000 [thread overview]
Message-ID: <ork8y2cx7d.fsf@araguaia.dcc.unicamp.br> (raw)
Message-ID: <19990228225300.pvrrb-tA5iMRFRiAE2FKWtbkZd42mQEh2ZOz8EspRAk@z> (raw)
In-Reply-To: <18553.917828496@upchuck>
On Jan 31, 1999, Jeffrey A Law <law@upchuck.cygnus.com> wrote:
> In message <orhftducc1.fsf@araguaia.dcc.unicamp.br>you write:
>> > 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.
> Well, I thought the whole idea of that built-in name was to override
> everything. Maybe I misunderstood the original intentions of including
> a pathname for the assembler in the first place.
Yep, the original idea was that, but then I found out it was not such
a good idea because it was not possible to override the hard-coded
names, whereas it is possible to override any other hard-coded path.
Maybe assuming -B is supposed to override it is not a good idea, and
we should just add new flags to allow the user to specify the linker
and the assembler names.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
next prev parent reply other threads:[~1999-02-28 22:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 23:58 $tooldir Jeffrey A Law
1999-01-31 23:58 ` $tooldir Alexandre Oliva
1999-01-26 7:17 ` $tooldir Jeffrey A Law
1999-01-26 10:26 ` $tooldir Alexandre Oliva
1999-01-26 10:58 ` $tooldir Donn Terry
1999-01-31 23:58 ` $tooldir Donn Terry
1999-01-31 20:13 ` $tooldir Jeffrey A Law
1999-02-01 1:09 ` Alexandre Oliva [this message]
[not found] ` < ork8y2cx7d.fsf@araguaia.dcc.unicamp.br >
1999-02-01 9:11 ` $tooldir Jeffrey A Law
1999-02-01 9:16 ` $tooldir Alexandre Oliva
1999-02-28 22:53 ` $tooldir Alexandre Oliva
1999-02-28 22:53 ` $tooldir Jeffrey A Law
1999-02-28 22:53 ` $tooldir Alexandre Oliva
1999-01-31 23:58 ` $tooldir Alexandre Oliva
1999-01-31 23:58 ` $tooldir Jeffrey A Law
1999-01-31 23:58 ` $tooldir Manfred Hollstein
1999-01-31 23:58 ` $tooldir Alexandre Oliva
1999-01-31 23:58 ` $tooldir Manfred Hollstein
1999-01-31 23:58 ` $tooldir Jeffrey A Law
1999-01-31 23:58 ` $tooldir Bill Currie
1999-01-31 23:58 ` $tooldir Jeffrey A Law
1999-01-20 17:37 ` $tooldir Bill Currie
1999-01-20 23:28 ` $tooldir Jeffrey A Law
1999-01-31 23:58 ` $tooldir Jeffrey A Law
1999-01-31 23:58 ` $tooldir Bill Currie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ork8y2cx7d.fsf@araguaia.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=egcs@egcs.cygnus.com \
--cc=law@cygnus.com \
--cc=manfred@s-direktnet.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).