(usagi-users 01429) Re: Latest snapshot and crypto/IPsec configure options

[KANDA Mitsuru <mk@xxxxxxxxxxxxxx>]

Hello,


CONFIG_CRYPTO is specified by bool (not tristate) in our crypto/Config.in.
So it never defined ad 'm'.
(If both crypt and ipv6 are defined module, it will caused symbol problem...)


> I ran into very strange trouble on configuring kernel options using
> "make menuconfig"
> 
> Crypto options always forced to "m"odule, even if I select "y"es (in
> menuconfig or in .config by hand and a new menuconfig).
Umm, as I mentioned above, CONFIG_CRYPTO is specified 'bool'.
very strange...

Regards,
-mk

> 
> But if Crypto is "m", IPsec option in net isn't shown.
> 
> Very bad temp fix:
> --- net/Config.in.usagi Fri May  3 10:36:06 2002
> +++ net/Config.in       Fri May  3 10:36:25 2002
> @@ -24,7 +24,7 @@
>     source net/tux/Config.in
>     source net/ipv4/Config.in
>     if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then
> -      if [ "$CONFIG_CRYPTO" = "y" ]; then
> +      if [ "$CONFIG_CRYPTO" = "y" -o "$CONFIG_CRYPTO" = "m" ]; then
>           bool '   The IPsec protocol (EXPERIMENTAL)' CONFIG_IPSEC
>           if [ "$CONFIG_IPSEC" != "n" ]; then
>              source net/key/Config.in
>
> 
> But the problem is sure somewhere else. I don't understand why crypto
> settings are forced to module, even if selected as static.