Summary: | net-wireless/ndiswrapper - No kernel config checks used | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Roger <rogerx.oss> |
Component: | New packages | Assignee: | Mobile Herd (OBSOLETE) <mobile+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Roger
2008-07-20 02:41:54 UTC
Both ebuilds do check for it ('old' wireless stack) and abort without required kernel options. Following is pasted from madwifi-ng ebuild. ---8< snip ---- CONFIG_CHECK="CRYPTO WIRELESS_EXT SYSCTL KMOD" ERROR_CRYPTO="${P} requires Cryptographic API support (CONFIG_CRYPTO)." ERROR_WIRELESS_EXT="${P} requires CONFIG_WIRELESS_EXT selected by Wireless LAN drivers (non-hamradio) & Wireless Extensions" ---8< snip --- So the question is, why did it fail to not catch the lack of wireless_ext within my /usr/src/linux/.config? For some reason, on both the latest ndiswrapper & madwifi-ng ebuilds, they both passed the checks, but failed while compiling with a compiler complaint of something to the extent "no wireless_ext defined". After figuring out I was lacking the old deprecated code (config option), I then enabled it and things compiled just fine. <stumped> === Summaries Are Not Like Titles At All === === But More Like a Sentence Describing === === What the Actual Bug Report Is About === Please file a similar bug report for net-wireless/madwifi-ng - the ebuilds for either package are maintained by different groups of developers. As for the summary, I try to make it as descriptive as possible for users searching for bugs via bugs.gentoo.org as they get truncated after five to six words. Sounds good, thanks for moving to madwifi-ng. successfully fails for me on 1.56 |