From: Scott R. Grabowski (sg2j+@andrew.cmu.edu)
Date: 09/06/92


From: sg2j+@andrew.cmu.edu (Scott R. Grabowski)
Subject: Help compiling .97 pl3
Date: 7 Sep 1992 00:29:08 GMT

Greetings all, back to school (and FTP 8-)

Anyways, I have been having random problems compiling the kernel the
last couple of times that I have tried. I am using GCC 2.2.2b (not d),
and started all this with .97pl0. Anyways, I grabbed the kernel sources
(made the symln) and tried compiling. Everything went fine until it
tried to compile tools/build.c. I got problems like fcntl.h and
unistd.h not found. So I created sym links for them too. This had (I
thought) fixed my problem. So now, I grab the .97pl3 kernel source, and
try compiling that. Doesn't work. build.c gives warnings about
implicit definitions of read, write, open, and close. If I remove the
sym links, it gives the files not found message. My question is, do I
have something nonstandard in my setup (I don't think so, but the sym
links for unistd and fcntl aren't mentioned in the kernel readme).

Also, I occassionally (sp?) get strange things when trying to compile.
At random points, things like this happen:

chr_drv
chr_drv
chr_drv
.
.
.
etc....

So I break the compile. If I do a 'pwd' I get logged out of the pty.
If I log back in, and try a pwd again, I get logged out again. I have
to reboot in order to restore things to normal. (BTW, this happens with
a self-compiled .97pl1)

So, any clues? If I get GCC 2.2.2d will my problems go away? Any other
thoughts would be appreciated.

BTW, without me joining a mail channel, is there anyone who can point me
to the Beta site for XFree86 2.0 (you know, that has all those _REALLY_
cool features in it like ATI support, configurable drivers, etc...).
Thanks.

Thanks in advance,

-Scott

Scott Grabowski + "I don't pretend to understand women's
sg2j@andrew.cmu.edu + little quirks, just one thing I know for
Physics is Phun! + sure, chicks dig jerks." - Marblehead
Johnson!