Bug 23763 - Unable to compile certain modules with the kernel headers mismatch
Summary: Unable to compile certain modules with the kernel headers mismatch
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 7.0
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-11 05:29 UTC by Need Real Name
Modified: 2007-04-18 16:30 UTC (History)
0 users

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: ---


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.