The compiler is a good candidate here - we do have some issues still with
later versions of gcc, it just has not made it to the top of the list
for fixing yet. If you can try with an older gcc (the suggestion about kgcc
from redhat 7 is a good one - it is what I am using) and let the list
know if your problem goes away.
We will eventually get to be compiler neutral in XFS, in the mean time
if someone out there is feeling brave, they could try and work out what
is wrong with XFS (or the compiler) when using a later gcc.....
Steve
> On Wed, Jan 31, 2001 at 03:29:41AM -0600, Rahul Jain wrote:
> > On a CVS checkout of xfs-2.4-linux compiled with gcc 2.95.3 (in debian sid)
> ,
> > with -march=k6 added to the compilation flags, I ran the fsstress test prog
> ram,
> > and after some time, recieved the following error:
>
> I'm pretty sure XFS still wants gcc 2.91.66. You must have hacked the
> Makefile to get it to compile, right?
>
> I realize that that specific version of gcc isn't in Debian, however you
> can take Redhat's RPM of kgcc from 7.0 and use alien to convert it to
> deb. You can then do this in the toplevel Makefile:
>
> #comment out this line if compiling on RH 7.0
> #CC = $(CROSS_COMPILE)gcc -V egcs-2.91.66
> # AND uncomment the following line
> CC = $(CROSS_COMPILE)kgcc
>
> I haven't had any problems with this setup yet (going on a few months
> with /home on XFS).
>
> --
> Drew Bloechl
> drew@xxxxxxxxxxxx
> PGP key ID: 33855516
|