xfs
[Top] [All Lists]

Re: redhat 7.1

To: Martin Stricker <shugal@xxxxxx>
Subject: Re: redhat 7.1
From: utz lehmann <xfs@xxxxxxxxxx>
Date: Fri, 1 Jun 2001 01:58:37 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <3B16DFA0.AEFA4C50@xxxxxx>
References: <011101c0e97b$35e98700$0a01a8c0@den2> <3B16DFA0.AEFA4C50@xxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
Martin Stricker [shugal@xxxxxx] wrote:
> 
> 
> Juha Saarinen wrote:
> > Kevin Lochner wrote:
> > :: Redhat linux 7.1 is supposed to have all the compiler
> > :: problems ironed out
> > :: (I'm able to build 2.4.2+ kernels with no problems),
> > ::
> > :: After I install the patches provided at the SGI site for
> > :: 2.4.2 to provide
> > :: xfs capability, I'm no longer able to compile the kernel
> > :: until I download
> > :: kgcc. (I get errors about 'cc0' and 'cc1' as documented in your
> > :: mail archive about RHat 7.0)
> > ::
> > :: Could you clear this up for me, is the problem that gcc is
> > :: still broken in
> > :: redhat 7.1, or is there some problem that the sgi patches are
> > :: introducing??  If the latter, you may want to look at your patches.
> > ::
> > :: btw -- no problems using kgcc, but odd that I had to install
> > :: kgcc for a
> > :: supposedly *fixed* compiler.
> > 
> > Well, is it gcc 2.96-81, or is it the code itself? I think that's the
> > question everybody would like to have answered, but I think SGI's OSS
> > team is a little pressed for time at the moment.
> > 
> > I got file system corruption with 2.96-81, but it went away with
> > 2.91-66. I can't tell you why exactly though.
> 
> Not the compiler is broken but the source code! See
> http://www.bero.org/gcc296.html for more information. After a close look
> of some of my own source and contemplating about Beros comments I
> finally got to the conclusion Red Hat did a Good Thing (TM) deciding to
> use gcc 2.96-RH. But decide yourself. It may take *some* fixing in the
> XFS code but after that you're standards compliant, so your code should
> work with any compiler (that is, if that compilers is ANSI C compliant!
> Not all are...)

I'm sure there are bugs in gcc 2.96-81. The same kernel compiled for k6 made
filecorruptions and complied for i586 it worked. I think even in 2.91.66 are
(unknown) bugs. Compiler are very complex.

I dont use a experimental state filesytem (or kernel) with an experimental
state compiler.


I also think redhat ist right using gcc 2.96. I had too many bad experience
with 2.95.2. But compiler for kernels are a different thing.


utz

<Prev in Thread] Current Thread [Next in Thread>