From: Benjamin Scott <bscott@ntisys.com>
To: linux-lvm@sistina.com
Subject: Re: [OT]: Re: [linux-lvm] RH7.2 + kernel 2.4.17(or 16) + LVM 1.0.2
Date: Mon Feb 18 22:26:02 2002 [thread overview]
Message-ID: <Pine.LNX.4.44.0202182322300.3200-100000@dragon.inside.ntisys.com> (raw)
In-Reply-To: <3C71A746.7000707@birddog.com>
On Mon, 18 Feb 2002, Kirby C. Bohling wrote:
>> You should make sure you do NOT use GCC that comes with RH 7.2 as it is
>> broken.
>
> That is a curious remark, on several occasions Alan Cox has said that he
> compiles and runs his kernels using a current RedHat compiler.
The "GCC 2.96" that Red Hat ships is still (1) not a "real" GCC release
and (2) rather new. GCC 3.x is a "real" release but is even newer. Both
may have behaviors with LVM does not like. The LVM code may have bugs which
the more "traditional" GCC 2.91 allows but newer GCCs do not.
All in all, while Red Hat's "GCC 2.96" may work, it is a good idea to try
a more conservative compiler release when problems occur.
--
Ben Scott <bscott@ntisys.com>
| The opinions expressed in this message are those of the author and do not |
| necessarily represent the views or policy of any other person, entity or |
| organization. All information is provided without warranty of any kind. |
prev parent reply other threads:[~2002-02-18 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 18:34 [linux-lvm] RH7.2 + kernel 2.4.17(or 16) + LVM 1.0.2 Chris Rutledge
2002-02-18 18:52 ` Anders Widman
2002-02-18 19:18 ` [OT]: " Kirby C. Bohling
2002-02-18 19:43 ` [linux-lvm] snapshot safetynet? Steve Wray
2002-02-19 2:36 ` Anselm Kruis
2002-02-18 22:26 ` Benjamin Scott [this message]
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=Pine.LNX.4.44.0202182322300.3200-100000@dragon.inside.ntisys.com \
--to=bscott@ntisys.com \
--cc=linux-lvm@sistina.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 NNTP newsgroup(s).