Messages in this thread | | | Date | Tue, 21 Apr 2009 20:00:37 -0700 | From | Randy Dunlap <> | Subject | Re: [BUILD FAILURE 11/12] Next April 21 : PPC64 randconfig [drivers/usb/host/ohci-hcd.o] |
| |
David Brownell wrote: > On Tuesday 21 April 2009, Randy Dunlap wrote: >>> Since its feasible to say 'n' to both we get the compile error. How do >>> we enforce having at least one set? >> Looks like using "choice" without "optional" would do it. >> See Documentation/kbuild/kconfig-language.txt and various examples >> in Kconfig* files. > > That won't quite work ... "at least one" includes "two" > (i.e. a PCI card in little-endian, a native controller > in big-endian). Real-world systems need such configs, > or so I'm told, and that's why their supported.
Yes, I see.
> Is there maybe a way to force Kconfig to just reject > such illegal configs -- neither option set -- rather > than trying some how to fix it?
Not that I know of. cc-ing Sam.
> Or maybe ... if neither one is set, have the header > force both on, and issue a warning.
That should be doable. We'd prefer to catch it via Kconfig, but that doesn't look promising just now.
-- ~Randy
| |