public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	reiser@namesys.com (Hans Reiser),
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
	kas@informatics.muni.cz (Jan Kasprzak)
Subject: Re: [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related)
Date: Fri, 2 Feb 2001 13:22:38 -0800	[thread overview]
Message-ID: <200102022122.f12LMct11509@moisil.dev.hydraweb.com> (raw)
In-Reply-To: <cs.lists.linux-kernel/E14OjME-0006nU-00@the-village.bc.nu>

On Fri, 2 Feb 2001 16:46:45 +0000 (GMT), Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> : 	It is the original one. I'll try with the -69:
>> : 
>> 	With 2.96-69 the reiserfs seems to work well.
>> Sorry for the confusion, I forgot to upgrade the gcc on my machine.
> 
> Excellent. Im just glad to know its a fixed bug.

Yes. But since Red Hat took upon themselves to define "gcc 2.96", they
should have created a new patchlevel (2.96.1) for their fixed compiler.

As it stands, there is no way to determine programatically whether
gcc-2.96 is broken or now. The only way to do it is to check the RPM
version -- which, needless to say, is a bit difficult to do from the
C code about to be compiled. So I can't really blame Hans if he decides
to outlaw gcc-2.96[.0] for reiserfs compiles.

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~2001-02-02 21:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cs.lists.linux-kernel/E14OjME-0006nU-00@the-village.bc.nu>
2001-02-02 21:22 ` Ion Badulescu [this message]
2001-02-02 21:57   ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Alan Cox
2001-02-02 22:06     ` Arthur Erhardt
2001-02-02 22:06     ` Hans Reiser
2001-02-02 22:57       ` Ion Badulescu
2001-02-05  2:50       ` Brian Wolfe
2001-02-05  4:08         ` Albert D. Cahalan
2001-02-05 11:58           ` Alan Cox
2001-02-05 11:36             ` Hans Reiser
2001-02-05 12:44               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-05 12:16                 ` Hans Reiser
2001-02-05 12:52                   ` Alan Cox
2001-02-05 12:33                     ` Hans Reiser
2001-02-05 12:57                   ` Dr. David Gilbert
2001-02-05 16:57               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) James Sutherland
2001-02-12  3:41               ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Albert D. Cahalan
2001-02-12  9:45                 ` Hans Reiser
2001-02-05 12:16             ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Dr. David Gilbert
2001-02-05  5:21         ` Gregory Maxwell
2001-02-05 12:02           ` Alan Cox
2001-02-05 11:38             ` Hans Reiser
2001-02-05 11:55         ` Alan Cox
2001-02-05 11:35           ` Hans Reiser
2001-02-05 20:19           ` Brian Wolfe
2001-02-02 22:42     ` Ion Badulescu
2001-02-03  3:43       ` Johan Kullstam
2001-02-03  8:57     ` [reiserfs-list] " David Ford
2001-02-03 10:00       ` J . A . Magallon
2001-02-03 23:26         ` Felix von Leitner
2001-02-04 11:04           ` Alan Cox
2001-02-04  3:24       ` John Alvord
2001-02-02 11:28 Jan Kasprzak
2001-02-02 11:04 ` [reiserfs-list] " Hans Reiser
2001-02-02 12:16   ` Jan Kasprzak
2001-02-02 12:34     ` Alan Cox
2001-02-02 13:09       ` Jan Kasprzak
2001-02-02 16:36         ` Jan Kasprzak
2001-02-02 16:46           ` Alan Cox
2001-02-02 12:15 ` John Morrison

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=200102022122.f12LMct11509@moisil.dev.hydraweb.com \
    --to=ionut@moisil.cs.columbia.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kas@informatics.muni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.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