public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier <0@pervalidus.net>
To: "D. Stimits" <stimits@idcomm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.4.10] README and Documentation/Changes inconsistent
Date: Thu, 11 Oct 2001 02:23:54 -0300	[thread overview]
Message-ID: <20011011022354.O249@pervalidus> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 794 bytes --]

D. Stimits wrote:

> My first attempt at this question didn't seem to make it in.
> On RH 7.1, which has kgcc (2.91.66) and gcc 2.96, will it be
> necessary to install a third compiler for stable 2.4.10+
> compiles?

AFAIK not for 2.4.

> Can kgcc still work for this?

If kgcc = egcs 1.1.2, I suppose so. I compiled 2.4.10 and all
earlier 2.4 with it.

Anyway, I compiled 2.95.4 right now and 2.4.11 will use it.
Time to remove egcs. Maybe it's the recommended compiler for
2.2 (?), but I don't intend to downgrade.

BTW, these files don't say that 2.95.4 is from CVS and not a
final release.

If you have the 2.95.3 sources, then

cvs rdiff -u -r gcc-2_95_3 -r gcc-2_95-branch gcc > gcc-2.95.4.patch

is your friend.

-- 
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-2717-2399 (Niterói-RJ BR)

             reply	other threads:[~2001-10-11  5:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  5:23 =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-10 13:37 [2.4.10] README and Documentation/Changes inconsistent Florian Weimer
2001-10-10 13:53 ` Alan Cox
2001-10-11  4:48   ` D. Stimits

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=20011011022354.O249@pervalidus \
    --to=0@pervalidus.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stimits@idcomm.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