Bug 23763

Summary:	Unable to compile certain modules with the kernel headers mismatch
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <pat>
Component:	kernel	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED NOTABUG	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-01-11 05:29:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2001-01-11 05:29:20 UTC

I point out that by default the /usr/include/linux contains the 2.4 kernel
headers,  which means that users trying to compile 2.2 modules that don't
come with the kernel,  will have a lot of trouble.
Please make the current running kernel consistent with /usr/include/linux.
I hope that this is fixed in 7.1.

Comment 1 Jakub Jelinek 2001-01-11 10:48:13 UTC

If 3rd party modules look for /usr/include/linux headers, then they are
broken. This has been decided by Linus and others on lkml, if the modules
are looking for headers of currently running kernel, they should
look for /lib/modules/`uname -r`/build/include/linux/. On 7.0, you can find
the 2.2 headers in /usr/src/linux/include/linux particularly.
/usr/include/{linux,asm} is for headers which glibc has been built with, they
don't have to reflect current kernel at all.