Bug 116757 - /sbin/mkkerneldoth does not initialize SUMMIT to '0'
/sbin/mkkerneldoth does not initialize SUMMIT to '0'
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: initscripts (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2004-02-24 17:18 EST by Don Smith
Modified: 2014-03-16 22:42 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-24 17:22:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Don Smith 2004-02-24 17:18:16 EST
Description of problem:
The /sbin/mkkerneldoth script that rc.sysinit runs to create the
/boot/kernel.h has a small omission in that it doesn't initialize the
SUMMIT variable to '0' like it does with the variables for all the
other kernel types. This means that /boot/kernel.h will end up with an
empty definition on a non-Summit box:


The file 
/lib/modules/`uname -r`/build/include/linux/rhconfig.h #includes
/boot/kernel.h and uses the definitions in its own #define statements.
When it tries to use the __BOOT_KERNEL_SUMMIT definition on line 31:

#if defined(__BOOT_KERNEL_SUMMIT) && (__BOOT_KERNEL_SUMMIT == 1)

it ends up using an empty value in the comparison, and will generate a
syntax error (no left operand) when compiling source that includes
this file.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Include the rhconfig.h file mentioned in some source code
2. Attempt to preprocess/compile the source
Actual results:
An error message like
operator '(' has no left operand"

Expected results:
no error message

Additional info:
Comment 1 Bill Nottingham 2004-02-24 17:22:10 EST
You need to upgrade to the errata.

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