All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Alan Cox <alan@redhat.com>
Cc: Chris Mason <mason@suse.com>,
	Jan Kasprzak <kas@informatics.muni.cz>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
	"Yury Yu. Rupasov" <yura@yura.polnet.botik.ru>
Subject: Re: [reiserfs-list] Re: ReiserFS Oops (2.4.1, deterministic, symlink
Date: Sat, 03 Feb 2001 01:13:15 +0300	[thread overview]
Message-ID: <3A7B30FB.C63DBD11@namesys.com> (raw)
In-Reply-To: <200102022213.f12MDCR27812@devserv.devel.redhat.com>

Alan Cox wrote:
> 
> > my convenience matters as much as that of the users.  I don't want to use
> > #ifdefs, I want it to die explosively and verbosely informatively.  make isn't
> > the most natural language for that, but I am sure Yura can find a way.
> 
> Run a small shell check and let it fail if the shell stuff errors.
> 
> The fragment you want is
> 
> if [ -e /bin/rpm ]; then
>         X=`rpm -q gcc`
>         if [ "$X" = "gcc-2.96-54" ]; then
>                 echo "*** GCC 2.96-54 will miscompile Reiserfs. Please update your compiler"
>                 echo "See http://www.redhat.com/support/errata/RHBA-2000-132.html"
>                 exit 255
>         fi
> fi
> 
> > Please delay shipping the 3.0 CVS branch on RedHat for a while.:-)  Sorry, I
> > couldn't resist.
> 
> Grin. gcc 3.0 is going to be just as much fun Im sure, but finally should give
> everyone a stable C and more importantly C++ base including the LSB standards.
> 
> Alan

Ok, thanks Alan, we'll use it, Yura, write something resembling or equal to
this, test it, and check it into our CVS branch.

Hans
-
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 22:47 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-02 11:28 ReiserFS Oops (2.4.1, deterministic, symlink related) 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:26   ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-02 15:16     ` Chris Mason
2001-02-02 15:20       ` Alan Cox
2001-02-02 17:34       ` Hans Reiser
2001-02-02 18:25         ` Alan Cox
2001-02-02 20:43           ` Hans Reiser
2001-02-02 21:33             ` Alan Cox
2001-02-02 21:29               ` [reiserfs-list] " Hans Reiser
2001-02-02 22:13                 ` Alan Cox
2001-02-02 22:13                   ` Hans Reiser [this message]
2001-02-02 23:40                     ` J . A . Magallon
2001-02-02 23:34                       ` Hans Reiser
2001-02-03  0:17                       ` Jakub Jelinek
2001-02-03  4:25                         ` Paul Jakma
2001-02-03  7:58                           ` Alan Cox
2001-02-03  9:18                           ` J . A . Magallon
2001-02-03  9:48                           ` Jakub Jelinek
2001-02-03  7:46                       ` Alan Cox
2001-02-03 17:14                   ` David Woodhouse
2001-02-03 17:33                     ` Albert D. Cahalan
2001-02-03 17:56                       ` Alan Cox
2001-02-03 23:49                         ` Albert D. Cahalan
2001-02-02 21:34             ` John Morrison
2001-02-02 21:39               ` Alan Cox
2001-02-02 21:49                 ` John Morrison
2001-02-02 22:03                 ` Hans Reiser
2001-02-02 22:40                   ` Alan Cox
2001-02-02 22:16                     ` Hans Reiser
2001-02-02 22:58                   ` alex
2001-02-03  0:40                     ` Andre Pang
2001-02-03  2:22                   ` James Sutherland
2001-02-02 22:52                 ` Keith Owens
2001-02-09  9:39           ` Thomas Zehetbauer
2001-02-02 12:15 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) 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=3A7B30FB.C63DBD11@namesys.com \
    --to=reiser@namesys.com \
    --cc=alan@redhat.com \
    --cc=kas@informatics.muni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=reiserfs-list@namesys.com \
    --cc=yura@yura.polnet.botik.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.