Messages in this thread |  | | | From | "Grant R. Guenther" <> | | Subject | Re: CONFIG_PARIDE_PARPORT always set | | Date | Thu, 22 Jan 1998 06:54:54 -0500 (EST) | |
> if [ "$CONFIG_PARPORT" = "y" -o "$CONFIG_PARPORT" = "n" ] ; then
> define_bool CONFIG_PARIDE_PARPORT y
> else
> define_bool CONFIG_PARIDE_PARPORT m
> fi
>
> Is this right? I suspect not, especially since I always get
> CONFIG_PARIDE_PARPORT set to y, and I never select it (or anything
> related to it).
PARIDE can be built with or without PARPORT support. However, if PARPORT
is configured but not present in the kernel, PARIDE must also be built
as a loadable module.
The curious code above defines a bogus config option which is used only
in the very next line (which you omitted) as an input to dep_tristate
So that the user gets the correct options for building PARIDE.
Perhaps there is a better idiom for doing this, but I don't know what it
is. It's not at all clear to me what the valid expression syntax is for
the 'dependency' arguments to dep_tristate.
--------------------------------------------------------------------------
Grant R. Guenther grant@torque.net
--------------------------------------------------------------------------
|  |