Re: Trouble compiling 2.4.21 kernel
On Thursday 26 June 2003 10:00 am, John Foster wrote:
> Travis Crump wrote:
> >> rm -f include/asm
> >> ( cd include ; ln -sf asm-i386 asm)
> >> make -C scripts kconfig.tk
> >> make[1]: Entering directory `/usr/src/kernel-source-2.4.21/scripts'
> >> cat header.tk >> ./kconfig.tk
> >> ./tkparse < ../arch/i386/config.in >> kconfig.tk
> >> crypto/Config.in: 43: unknown command
> >> make[1]: *** [kconfig.tk] Error 1
> >> make[1]: Leaving directory `/usr/src/kernel-source-2.4.21/scripts'
> >> make: *** [xconfig] Error 2
> > I tried turning the elif's into nested else/if[ie:
> > else
> > if [ "$CONFIG_INET_AH" = "m" -o \
> > "$CONFIG_INET_ESP" = "m" -o \
> > "$CONFIG_INET6_AH" = "m" -o \
> > "$CONFIG_INET6_ESP" = "m" ]; then
> > define_tristate CONFIG_CRYPTO_SHA1 m
> > else
> > tristate ' SHA1 digest algorithm' CONFIG_CRYPTO_SHA1
> > instead of:
> > elif [ "$CONFIG_INET_AH" = "m" -o \
> > "$CONFIG_INET_ESP" = "m" -o \
> > "$CONFIG_INET6_AH" = "m" -o \
> > "$CONFIG_INET6_ESP" = "m" ]; then
> > define_tristate CONFIG_CRYPTO_SHA1 m
> > else
> > tristate ' SHA1 digest algorithm' CONFIG_CRYPTO_SHA1
> > fi
> > ]
> > which allowed xconfig to open up, but that section of the config still
> > didn't work[every option was grayed out], I ended up falling back on
> > menuconfig.
Sounds like you had the right idea..
About the grayed-out part.. I didn't try it, but it seems that
crypto/Config.in assumes that all these variables have been defined..
I notice that even after running make oldconfig that the two INET6
variables have not been inserted. (I may have chosen "N" for these in
oldconfig, though, or it may be a bug in oldconfig).. but, actually, it's
crypto/Config.in that's making an unwarranted assumption.. i.e, if it's
absent, it's not "m" and it's not "y", so Config.in assumes "N"..
Before running xconfig, if one were to go in and insert these variables
into .config as either "m" or "y", I'd bet that xconfig would work (after
patching crypto/Config.in).
Reply to: