From: Joe Buck <jbuck@synopsys.com>
To: mrs@wrs.com (Mike Stump)
Cc: egcs@cygnus.com (egcs team)
Subject: Re: Building EGCS from scratch
Date: Tue, 09 Sep 1997 13:30:00 -0000 [thread overview]
Message-ID: <199709092029.NAA28648@atrus.synopsys.com> (raw)
In-Reply-To: <199709091837.LAA18795@kankakee.wrs.com>
> > It seems that EGCS is sorely missing documentation on what needs to be built
> > for <foo> OS, and in what order.
Mike Stump writes:
> It isn't missing, though some of the simplicity seems to have been
> obscured over the years. It is configure; make; make install, that's
> about it, and that is the order.
That procedure doesn't provide a correctly bootstrapped gcc at present for
egcs. If you don't bootstrap, then the gcc binary depends on too many
variables, which will translate into hard-to-reproduce bugs.
Now, if a top-level make did a three-stage build and then built all the
other tools with the newly bootstrapped gcc, then we'd have the simplicity
you speak of.
next prev parent reply other threads:[~1997-09-09 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-09 12:13 Mike Stump
1997-09-09 13:30 ` Joe Buck [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-08 23:44 Steven J. Madsen
1997-09-09 7:50 ` Jeffrey A Law
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=199709092029.NAA28648@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=mrs@wrs.com \
/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).