Subject: Re: Why does xconfig not work for me?
From: Avinash Gupta (agupta@mediaone.net)
Date: Tue Jan 01 2002 - 09:46:18 MST
There is a small typo in /usr/src/linux/drivers/net/Config.in
Open the above file in vi and goto line 277. It should read:
dep_tristate ' PPP over ATM (EXPERIMENTAL)' CONFIG_PPPOATM $CONFIG_PP
Change this to read:
dep_tristate ' PPP over ATM (EXPERIMENTAL)' CONFIG_PPPOATM $CONFIG_PPP
and delete the next line that has a 'P' by itself on it.
Now you should be able to do a make xconfig.
-- Avinash Gupta (agupta@mediaone.net)
On Tuesday 01 January 2002 11:30, you wrote:
> Hello!
>
> I should be grateful if someone could help me in solving a small problem.
>
> I have installed YDL 2.1 on my iMac, with MacOS 9. As I wanted to examine
> the kernel, I launched xconfig, but it failed, as shown by this output:
>
> [root@sirius /root]# cd /usr/src/linux-2.4.10
> [root@sirius linux-2.4.10]# make xconfig
> rm -f include/asm
> ( cd include ; ln -sf asm-ppc asm)
> make -C scripts kconfig.tk
> make[1]: Entering directory `/usr/src/linux-2.4.10/scripts'
> cat header.tk >> ./kconfig.tk
> ./tkparse < ../arch/ppc/config.in >> kconfig.tk
> drivers/net/Config.in: 278: unknown command
> make[1]: *** [kconfig.tk] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.4.10/scripts'
> make: *** [xconfig] Error 2
>
> On the other hand, menuconfig seems to work correctly:
>
> [root@sirius linux-2.4.10]# make menuconfig
> rm -f include/asm
> ( cd include ; ln -sf asm-ppc asm)
> make -C scripts/lxdialog all
> make[1]: Entering directory `/usr/src/linux-2.4.10/scripts/lxdialog'
> make[1]: Leaving directory `/usr/src/linux-2.4.10/scripts/lxdialog'
> /bin/sh scripts/Menuconfig arch/ppc/config.in
> Using defaults found in arch/ppc/defconfig
> Preparing scripts: functions,
> parsing....................................................................
>. .done.
> (this is the period during which menuconfig is active)
> Your kernel configuration changes were NOT saved.
> [root@sirius linux-2.4.10]#
>
> I should like to have xconfig work as well. In this case, the reference to
> drivers/net/Config.int seems not to make sense: this directory cannot be
> accessed directly from /scripts; and line 278 reads
>
> dep_tristate'National Semiconduct DP83820 support' CONFIG_NS83820
> $CONFIG_PCI
>
> In what way could this be relevant? Can anyone enlighten me?
>
> R.B.
This archive was generated by hypermail 2a24 : Tue Jan 01 2002 - 09:58:21 MST