Bug 64121
Summary: | Typo on line 299 of /usr/src/linux-2.4.18-0.22/include/linux/module.h | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michael St. Laurent <mikes> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
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: | 2003-06-05 17:51:25 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
Michael St. Laurent
2002-04-25 23:21:19 UTC
Humm it actually looks correct it basically creates a string which is "kernel_version=2.4.18-0.22"; C allows 2 string constants to be consecutive and then concatinates them underwater... On my system the line reads: "kernel_version=" UTS_RELEASE; This caused the compiler to error out with something like 'Parse error before UTS_RELEASE' When I changed the line to read like this: "kernel_version=UTS_RELEASE"; the compiler was happy. The compiler might be happy but it's wrong. UTS_RELEASE is a string with the kernel version number, and that needs to be concatinated there, eg to create "kernel_version=2.4.18-0.22". Now UTS_RELEASE is from version.h which is autogenerated at build time; could you say how you are building the kernel since I get the idea something is going funny there that causes a weird version.h to be present I'm not actually building the kernel, I'm building the linux-wlan-ng package which requires the kernel and pcmcia-cs sources (which it borrows files from). linux-wlan-ng is broken then. It should not ever depend on the kernel sources. It can use the glibc headers (from glibc-devel and glibc-kernheaders)..... |