From: Zack Weinberg <zack@codesourcery.com>
To: schaecsn <schaecsn@gmx.de>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc 2.95.4
Date: Sat, 13 Oct 2001 10:43:00 -0000 [thread overview]
Message-ID: <20011013104321.O379@codesourcery.com> (raw)
In-Reply-To: <3BC7F9A9.654A7D4E@gmx.de>
On Sat, Oct 13, 2001 at 01:22:01AM -0700, schaecsn wrote:
> Hi
>
> The linux-2.4.12 Changes file mentions this "The recommended compiler
> for the kernel is gcc 2.95.3 or .4".
>
> Actually, the last 2.95 version on ftp.gnu.org is .3 and not .4.
>
> where can I get .4? Isn't that an "offical" release?
The official release of 2.95.4 has not yet occurred. However, it is
fairly common for system integrators to ship pre-release versions of
2.95.4 taken from our CVS tree. These identify themselves like this:
$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011006 (Debian prerelease)
This practice is safe, since we are conservative about changes applied
to the 2.95.x CVS branch, and the integrators presumably do their own
testing.
The advice you quote is meant to reassure users that it is okay to use
these pre-release versions to compile the Linux kernel.
zw
next prev parent reply other threads:[~2001-10-13 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 1:27 schaecsn
2001-10-13 10:43 ` Zack Weinberg [this message]
2001-10-13 14:12 =?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=20011013104321.O379@codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=schaecsn@gmx.de \
/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).