From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: Proposal for new organization of gcc
Date: Mon, 12 Jan 1998 04:09:00 -0000 [thread overview]
Message-ID: <oru3b9aohw.fsf@amazonas.dcc.unicamp.br> (raw)
In-Reply-To: <9801121156.AA07482@vlsi1.ultra.nyu.edu>
Richard Kenner writes:
> Having the C front-end in the base tar file is ok for me, but I don't
> like to be required to build it just because I want to install the
> front-end for one more language.
> "one *more*"?
Let me be clearer. Suppose I had installed gcc-2.7.2.3 and g77-0.5.19
with a few local patches some weeks ago. Then I removed the sources
and the build tree.
Now I'd like to upgrade to g77-0.5.20. In a good world, I wouldn't
have to bootstrap gcc again just to be able to build g77, I could
simply tell g77: hey, use that gcc installed in /usr/local/bin, it
will do. In a perfect world, GCS would have already installed a
library and some include-files that would allow g77 to build *without*
a top-level GCS directory.
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil
next parent reply other threads:[~1998-01-12 4:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9801121156.AA07482@vlsi1.ultra.nyu.edu>
1998-01-12 4:09 ` Alexandre Oliva [this message]
[not found] <9801082336.AA26988@vlsi1.ultra.nyu.edu>
1998-01-08 16:24 ` Alexandre Oliva
1998-01-08 18:28 ` Michael Gschwind
1998-01-11 18:24 ` Richard Stallman
1998-01-11 18:58 ` Alexandre Oliva
1998-01-12 17:55 ` Richard Stallman
1998-01-13 4:31 ` Alexandre Oliva
1998-01-20 12:42 ` Richard Stallman
1998-01-20 14:54 ` Alexandre Oliva
1998-01-21 9:18 ` Richard Stallman
1998-01-22 1:45 ` Richard Earnshaw
1998-01-22 2:29 ` Alexandre Oliva
1998-01-22 4:12 ` Richard Earnshaw
1998-01-22 2:29 ` Alexandre Oliva
1998-01-23 14:48 ` Harvey J. Stein
1998-01-23 14:48 ` amylaar
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=oru3b9aohw.fsf@amazonas.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).