Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 18926 - kernel 2..4.0-src is badly packaged.
kernel 2..4.0-src is badly packaged.
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Michael K. Johnson
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2000-10-11 21:40 EDT by Spider
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-10-11 21:40:58 EDT
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 Spider 2000-10-11 21:40:53 EDT
before any configuration would be compiled, we had to do make distclean and
reconfigure, or it would hang somewhere around:
 In file included from ksyms.c:18:
 /usr/src/linux-2.4/include/linux/kernel_stat.h: In function `kstat_irqs':
 /usr/src/linux-2.4/include/linux/kernel_stat.h:98: `smp_num_cpus'
undeclared (first use in this function)

also is there some inconsistence between make menuconfig and make config?
I'm wondering most around the cpu specific changes arch/i386/config.in
since they weren't included in first attempted config (menuconfig) but with
make config they were...
Comment 1 Bill Nottingham 2000-11-04 02:40:15 EST
You need to run 'make mrproper' first.
Comment 2 Rex Henderson 2000-12-04 12:37:02 EST
Given the advice, this package is still badly broken. I still cannot get the 
kernel to compile. But it is not all RedHat's fault. I downloaded the kernel 
source from www.kernel.org and had similar problems dependant on the settings I 
chose (like if I chose a cpu model above i586, I got the same errors).
But the RedHat release takes this a step farther. I cannot get ANY  
configuration to compile...

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