Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Jens Axboe writes:
> => On a hunch, I tried using egcs-1.1.2 instead of gcc-2.95 (I didn't think
> => I had that on my devel system, but I guess I did...). This has cured
> => the problem for me, so you may want to try that.
> This is probably a FAQ now. I gather XFS and/or the kernel have issues
> with gcc-2.95.
> We build with egcs-2.91.66 here with no problems.
just added it to the faq ...
btw. what kind of problems are that - are they in the gcc 2.95
optimizer or in the i386 backend (because maybe this is also
the reson for the problems on the other arches i tried: ppc
and alpha - i used 2.95 on both - because it's the
standard there ... maybe i should build and try
egcs there too)
t
p.s.: i very often get the following whenever i want to check
something into the web tree - anyone from the sgi people
an idea what this is ?
...
Checking in faq.html;
/cvs/xfs-website/faq.html,v <-- faq.html
new revision: 1.13; previous revision: 1.12
done
cvs [server aborted]: received broken pipe signal
cvs commit: saving log message in /tmp/cvstJJmJa
graichen@h2o ~/xfs-faq/xfs-website %
i am cvs login'ed here and sometimes it also works ...
--
thomas.graichen@xxxxxxxxxxxxx
technical director innominate AG
clustering & security networking people
tel: +49.30.308806-13 fax: -77 http://innominate.de
|