Johannes Berg wrote: > On Wed, 2009-10-07 at 14:55 -0700, Randy Dunlap wrote: >> John W. Linville wrote: >>> Should prevent this build error reported by Randy... >>> >>> net/wireless/wext-priv.c:206: error: implicit declaration of function 'call_commit_handler' >>> make[3]: *** [net/wireless/wext-priv.o] Error 1 >>> >>> Reported-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx> >>> Signed-off-by: John W. Linville <linville@xxxxxxxxxxxxx> >> Sorry, it did not work for me. > >> linux-next-20091007/net/wireless/wext-priv.c:206: error: implicit declaration of function 'call_commit_handler' >> make[3]: *** [net/wireless/wext-priv.o] Error 1 >> >> Drivers like hostap and orinoco (hermes) select WEXT_PRIV regardless >> of the setting of WEXT_CORE. oh, and staging/ drivers do that also. > > But they also select WIRELESS_EXT, which should cause WEXT_CORE to be > turned on. Is it possible that is failing? # CONFIG_WIRELESS is not set CONFIG_WIRELESS_EXT=y CONFIG_WEXT_SPY=y CONFIG_WEXT_PRIV=y WEXT_CORE is not enabled. I haven't found the culprit, but I suspect "select". but what in WIRELESS_EXT would also cause WEXT_CORE to be enabled? ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
