Message-ID: <9DA8D24B915BD1118911006094516EAF019C7F95@umr-mail02.cc.umr.edu>
From: "Neulinger, Nathan R." <nneul AT umr DOT edu>
To: "'pgcc AT delorie DOT com'" <pgcc AT delorie DOT com>
Subject: My problem report about kernel problems
Date: Tue, 2 Mar 1999 15:17:01 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="iso-8859-1"
Reply-To: pgcc AT delorie DOT com

I wasn't subscribed to the mailing list, so didn't get any of your
questions, and didn't realize you asked them till I went and looked at the
archive.

Let's see, someone already said where to get arla. You're probably going to
have a fair bit of trouble building it though, as it requires kerberos and
libkafs.

The options, well, I normally use -O6 -mpentium for the kernel builds. And,
as I believe I said in my original note - I normally have _ZERO_ problems
with kernels built with pgcc - this problem has only cropped up when using
arla. I've got a whole slew of machines that are built this way that are
working flawlessly (well, except for one that is having tulip driver
problems, but that may or may not have anything to do with pgcc.)

gcc kernel, gcc arla: no problems
gcc kernel, pgcc arla: has problem
pgcc kernel, gcc arla: I believe this has problem, but am not positive
pgcc kernel, pgcc arla: has problem

The only clear symptom I can describe is the SIG: sigpending lied stuff.
That should never happen as far as I can tell, but it happens with 100%
reliability if I build arla or the kernel with pgcc.

This occurs whether I use the default -O2 -m486 stuff or setting full
optimization.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul AT umr DOT edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216