>Vidiot <[EMAIL PROTECTED]> on Tue, Apr 21, 1998 at 01:37:16PM -0500:
>> There appears to be some kind of nasty bug in the code that 2.8.1 produces
>> that causes XFree86 to not start.
>
>No. It is the kernel, compiled with this, that screws up anything that
>accesses ioports. The solution is to use an ioport.c from a development
>kernel, or compile just that file with 2.7.2.3, then link the whole
>thing with 2.8.x . It works fine either way.
Sorry, I thought it was understand it was a result of the recompiled kernel
that resulted in the problem, especially since I said that it was the kernel
that I had recompiled with 2.8.1. I never said that I recompiled XFree86.
I didn't mean to imply otherwise.
In any event, it is nice to know the cause. Actually, I don't know the
cause, only the piece affected. What changed in the compiler to cause
ioport.c not to work with the 2.8.1 compiler?
MB
--
System Administrator - Finnigan FT/MS - Madison WI. URL:http://www.ftms.com/
e-mail: [EMAIL PROTECTED]
phone: (608) 273-8262 ext: 612 fax: (608) 273-8719
Visit - URL:http://www.vidiot.com/ (Your link to Star Trek and UPN)
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
