From: Frédéric L. W. Meunier <0@pervalidus.net>
To: mike stump <mrs@windriver.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Which egcs ?
Date: Wed, 19 Sep 2001 20:23:00 -0000 [thread overview]
Message-ID: <20010920002358.Z15507@pervalidus> (raw)
In-Reply-To: <200109181820.LAA22134@kankakee.wrs.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On Tue, Sep 18, 2001 at 11:20:03AM -0700, mike stump wrote:
> > Hi. What's the recommended (or most stable) release of egcs ?
>
> Egcs is dead. Egcs is gcc. The latest release of gcc can be found on
> our web site. http://gcc.gnu.org Let use know if the web site doesn't
> make it clear.
I know, but egcs is still the recommended compiler for Kernel
2.4:
"COMPILING the kernel:
- Make sure you have gcc-2.91.66 (egcs-1.1.2) available. gcc 2.95.2 may
also work but is not as safe, and *gcc 2.7.2.3 is no longer supported*."
and rescue disks (to save space).
What I want to know is what's the recommended (or most
stable) release of egcs. 1.1.2 (egcs_1_1_2_release) or
egcs_ss_19990913 (egcs_latest_snapshot), or any other
snapshot.
If 1.1.2, are that any problems fixed by patches ?
And if it's OK to compile egcs with GNU C Library 2.2.4. Or
it generates wrong code. I only need the C part.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-2717-2399 (Niterói-RJ BR)
next prev parent reply other threads:[~2001-09-19 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 11:21 mike stump
2001-09-19 20:23 ` Frédéric L. W. Meunier [this message]
2001-09-19 22:39 ` Per Bothner
-- strict thread matches above, loose matches on Subject: below --
2001-09-20 10:54 mike stump
2001-09-17 20:25 Frédéric L. W. Meunier
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=20010920002358.Z15507@pervalidus \
--to=0@pervalidus.net \
--cc=gcc@gcc.gnu.org \
--cc=mrs@windriver.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).