Bug 29393 - building kernel make xconfig doesn't work
Summary: building kernel make xconfig doesn't work
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-02-25 16:05 UTC by Tim Clymo
Modified: 2007-04-18 16:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-25 16:05:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Tim Clymo 2001-02-25 16:05:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.1-0.1.9 i686)

There seems to be a bug in the kernel-source distribution. Specifically, in

When trying to configure a new kernel, make xconfig returns an error
referring to line 9 of this file. Worked around by using make menuconfig

Reproducible: Always
Steps to Reproduce:
1. cd /usr/src/linux-2.4
2. make xconfig

Actual Results:  error

Expected Results:  should have displayed kernel configuration xclient

[root@tcpc linux-2.4]# make xconfig
rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
make -C scripts kconfig.tk
make[1]: Entering directory `/usr/src/linux-2.4.1/scripts'
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkparse.o
tkparse.cgcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o
tkcond.o tkcond.c
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkgen.o
gcc -o tkparse tkparse.o tkcond.o tkgen.o
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
net/ipv4/netfilter/ip_vs/Config.in: 9: incorrect argument
make[1]: *** [kconfig.tk] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.1/scripts'
make: *** [xconfig] Error 2

Comment 1 Arjan van de Ven 2001-02-26 09:57:06 UTC
The fix for this problem will be in the next kernel build.
In the mean time, you can look at bug 29449  for a workaround.

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