Matthew Reppert wrote: > > Michel D�nzer wrote: > > > On Tue, 2001-10-23 at 07:54, Matthew Reppert wrote: > > > > > >>Now, let me say one thing; I've run two different kernels on this > >>system: 2.4.10 and 2.4.12. Note #1: my /usr/include/linux and > >>/usr/include/asm were NOT FHS compliant ... because I'd copied > >>the data into those directories. Note #2: I did this back when > >>I was running 2.4.10. Well, today I noticed this, kicked myself in > >>the arse a few times, and made the proper symlinks ... recompiled > >>just now and X seems to work fine. Heck, Quake 3 runs nice ... ^^; > >> > > > >>From FHS 2.3: > > > > 6.1.7 /usr/include : Header files included by C programs > > > > These symbolic links are required if a C or C++ compiler is > > installed and only for systems not based on glibc. > > > > /usr/include/asm -> /usr/src/linux/include/asm-<arch> > > /usr/include/linux -> /usr/src/linux/include/linux > > > > > > So your system isn't based on glibc? I think you've found out the > > hard way why these really shouldn't be symlinks. > > ... you know, that's a good point. I *am* glibc-based, 2.2.x. > Interesting; well, it may have had to do with some of the stuff I > defined in host.def, though I can't really see what it would be ...
No, I think the problem was clearly the kernel headers. > I'll look into it when I have more time (sometime later this week). > Still suspect the headers. And why not symlinks? Because as you have found out, you're in trouble if they are wrong (your copy of the kernel headers from an older version was no different than wrong symlinks). This has been discussed extensively on l-k. Look at the Debian glibc packages for a solution that works. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
