On Tuesday 18 November 2003 4:22 pm, Paul Stear wrote:
> On Tue 18 November 2003 20:48, Janne Johansson wrote:
> > On Tue, 2003-11-18 at 22:45, Paul Stear wrote:
> > > Hi all,
> > > I wanted to use xconfig to make a new kernel but it fails.
> >
> > How does it fail?
> >
> > > What do I need to use xconfig instead of menu config?
> >
> > Depends.
>
> This is the error output, hope it helps, I seem to remember along time ago
> mention was made of needing something extra for xconfig to work.
>
> bash-2.05b# cd /usr/src/linux
> bash-2.05b# 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.20-gentoo-r1/scripts'
> cat header.tk >> ./kconfig.tk
> ./tkparse < ../arch/i386/config.in >> kconfig.tk
> echo "set defaults \"arch/i386/defconfig\"" >> kconfig.tk
> echo "set ARCH \"i386\"" >> kconfig.tk
> cat tail.tk >> kconfig.tk
> chmod 755 kconfig.tk
> make[1]: Leaving directory `/usr/src/linux-2.4.20-gentoo-r1/scripts'
> wish -f scripts/kconfig.tk
> make: wish: Command not found
> make: *** [xconfig] Error 127
> bash-2.05b#

It's been my experience that some of the later 2.4 kernels didn't support 
xconfig, at least on Gentoo, and I got the same error. I never figured out 
why, and never pursued it, as I've gone to 2.6 kernels anyway. I did compile 
a bunch of 2.4 kernels on Mandrake, but IIRC, I always used xconfig with 
them. Also, xconfig requires qt to be installed, and if you have kde 
installed, qt is too.

Robert Crawford


--
[EMAIL PROTECTED] mailing list

Reply via email to