Bug 60780 - Bad: make xconfig generates an error
Summary: Bad: make xconfig generates an error
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: kernel-utils
Version: pensacola
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-06 16:12 UTC by Alex Pearsall
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-03-06 16:12:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Alex Pearsall 2002-03-06 16:12:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.0.3 (X11; Linux i686; U;) Gecko/20020214

Description of problem:
running make xconfig after installing the kernel-source beta package for
Pensacola, generates an error.  The error is as follows:
"drivers/net/Config.in: 252: can't handle dep_bool/dep_mbool/dep_tristate condition"

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


How reproducible:
Always

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

Actual Results:  [root@minos 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.9-26beta.31/scripts'
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
drivers/net/Config.in: 252: can't handle dep_bool/dep_mbool/dep_tristate condition
make[1]: *** [kconfig.tk] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.9-26beta.31/scripts'
make: *** [xconfig] Error 2
[root@minos linux-2.4]# 

Expected Results:  Graphical TK Kernel configuration menu to configure my kernel.

Additional info:

kernel-utils and tk/tcl are both installed.  everything that should be there is
there.  I've double and triple checked this.  So I believe its a flat out bug.

Comment 1 Arjan van de Ven 2002-03-06 16:17:22 UTC
Indeed it is. I wonder why make menuconfig doesn't complain....
Anyway, fixed for the next build; thanks for the report!


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