From: "Eric M. Hopper" <hopper@omnifarious.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Segment Failure ,while doing lvcreate
Date: Thu Oct 25 07:44:01 2001 [thread overview]
Message-ID: <20011025074500.A4615@omnifarious.org> (raw)
In-Reply-To: <3BD80807.4725174F@carolina.rr.com>; from jedgecombe@carolina.rr.com on Thu, Oct 25, 2001 at 08:39:35AM -0400
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Thu, Oct 25, 2001 at 08:39:35AM -0400, Jason Edgecombe wrote:
> hi,
>
> recompile lvm tools with the -O0 flag (no optimization).
> this is because of redhat's 7.x borken gcc compiler
>
> I believe that this fix is in the archive.
Which version of their compiler are you using? Is it
gcc-2.96-88, or gcc-2.96-96? Is it even earlier?
Does gcc 3.0.1 have this same problem? Are you sure the bug
isn't in the code? (i.e. having a non-volatile variable randomly
modified under your nose, or some such that would tend to not work so
well under optimization.)
If gcc-2.96-96 doesn't have the problem, RH 7.2 should work just
fine.
Have fun (if at all possible),
--
"It does me no injury for my neighbor to say there are twenty gods or no God.
It neither picks my pocket nor breaks my leg." --- Thomas Jefferson
"Go to Heaven for the climate, Hell for the company." -- Mark Twain
-- Eric Hopper (hopper@omnifarious.org http://www.omnifarious.org/~hopper) --
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-10-25 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 6:44 [linux-lvm] Segment Failure ,while doing lvcreate David Chang
2001-10-25 7:38 ` Thomas Svedberg
2001-10-25 7:38 ` Jason Edgecombe
2001-10-25 7:44 ` Eric M. Hopper [this message]
2001-10-25 7:48 ` Jason Edgecombe
2001-10-26 7:56 ` Eric M. Hopper
2001-10-25 8:14 ` Markus Dobel
2001-10-26 7:50 ` Eric M. Hopper
2001-10-25 18:36 ` Sean Burford
-- strict thread matches above, loose matches on Subject: below --
2001-10-26 8:02 Jean-Eric Cuendet
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=20011025074500.A4615@omnifarious.org \
--to=hopper@omnifarious.org \
--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