public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Stimits" <stimits@idcomm.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4.10] README and Documentation/Changes inconsistent
Date: Wed, 10 Oct 2001 22:48:25 -0600	[thread overview]
Message-ID: <3BC52499.3D60A76D@idcomm.com> (raw)
In-Reply-To: <E15rJnR-0007tO-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > These files state different C compiler requirements.  Which one is
> > correct?
> 
> gcc 2.95.[3,4] is probably the compiler of choice

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? Can kgcc still work for
this? I'm one of the people running XFS filesystem, and the XFS code
works well with kgcc, but it makes me nervous to think about using
anything else with XFS kernels. I would be greatly relieved if 2.91.66
remains useable throughout the 2.4.x series.

D. Stimits, stimits@idcomm.com

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2001-10-11  4:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-11  5:23 =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= 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=3BC52499.3D60A76D@idcomm.com \
    --to=stimits@idcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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