From: Richard Stallman <rms@santafe.edu>
To: oliva@dcc.unicamp.br
Cc: kenner@vlsi1.ultra.nyu.edu, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: Proposal for new organization of gcc
Date: Tue, 20 Jan 1998 12:42:00 -0000 [thread overview]
Message-ID: <199801201934.MAA01735@wijiji.santafe.edu> (raw)
In-Reply-To: <or4t38iuhi.fsf@amazonas.dcc.unicamp.br>
> In a perfect gcs, I'd be able to
> download the gcs backend and the language front-end, build them with
> the installed C compiler and install that, and I'm done.
> I think that already works now.
I couldn't make it happen, but I can't say I've tried too hard. All I
have to say is that it is not as easy as simply removing the back-end
and the C front-end directory from the source tree,
I would have tried something simpler--just running Make with arguments
that tell it not to build cc1. If that doesn't work, can you try to
find out why not? It might be an easily corrected problem.
next prev parent reply other threads:[~1998-01-20 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
[not found] <9801121156.AA07482@vlsi1.ultra.nyu.edu>
1998-01-12 4:09 ` Alexandre Oliva
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=199801201934.MAA01735@wijiji.santafe.edu \
--to=rms@santafe.edu \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=oliva@dcc.unicamp.br \
/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).