When emerging ipw2100 with development-kernel 2.6.7, I get: # emerge ipw2100 Calculating dependencies ...done! >>> emerge (1 of 1) net-wireless/ipw2100-0.51 to / >>> md5 src_uri ;-) ipw2100-0.51.tgz >>> md5 src_uri ;-) ipw2100-fw-1.2.tgz >>> Unpacking source... >>> Unpacking ipw2100-0.51.tgz to /var/tmp/portage/ipw2100-0.51/work >>> Unpacking ipw2100-fw-1.2.tgz to /var/tmp/portage/ipw2100-0.51/work * /usr/src/linux is a symbolic link * Determining the real directory of the Linux kernel source code * Building for Linux 2.6.7 found in /usr/src/linux >>> Source unpacked. make -C //usr/src/linux M=/var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51 MODVERDIR=/var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51 modules make[1]: Entering directory `/usr/src/linux-2.6.7' CC [M] /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ieee80211_module.o CC [M] /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ieee80211_tx.o CC [M] /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ieee80211_rx.o CC [M] /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ieee80211_wx.o CC [M] /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.o CC [M] /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_fw.o CC [M] /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_wx.o CC [M] /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ieee80211_crypt.o CC [M] /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ieee80211_crypt_wep.o /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.c:6443:52: macro "create_workqueue" requires 2 arguments, but only 1 given /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.c: In function `ipw2100_alloc_device': /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.c:6443: error: `create_workqueue' undeclared (first use in this function) /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.c:6443: error: (Each undeclared identifier is reported only once /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.c:6443: error: for each function it appears in.) /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.c: At top level: /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.c:5329: warning: `ipw2100_disassociate_bssid' defined but not used /var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.c:5385: warning: `ipw2100_set_wpa_ie' defined but not used make[2]: *** [/var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51/ipw2100_main.o] Error 1 make[1]: *** [_module_/var/tmp/portage/ipw2100-0.51/work/ipw2100-0.51] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.7' make: *** [modules] Error 2 !!! ERROR: net-wireless/ipw2100-0.51 failed. !!! Function src_compile, Line 61, Exitcode 2 !!! (no error message) Reproducible: Always Steps to Reproduce: 1.try to emerge ipw2100 with 2.6.7 2.watch it crash and burn 3. Actual Results: ipw2100 fails to build Expected Results: ipw2100 should have emerged and been working. :)
same here. but his happens aswell with version 0.50
Created attachment 36581 [details, diff] ipw2100_main.c.diff I think, the flags parameter in the create_workqueue function is not needed, so I put a NULL argument in it.
Created attachment 36582 [details] ipw2100-0.51.ebuild The ebuild includes the patch above.
This is likely to be related to the reporter using a kernel with the swsusp2 patches applied. See http://sourceforge.net/mailarchive/message.php?msg_id=9243751 for more information.
Could the reporter please try the ebuild for ipw2100-0.53 as attached to bug #60791 and see if this fixes the compilation? The ChangeLog for ipw2100-0.53 says (see http://ipw2100.sourceforge.net for full ChangeLog): Fixed SWSUSP2 build dependency check to CONFIG_SOFTWARE_SUSPEND2
works for me.
the next ipw2100 driver, ipw2100 0.53 is now available. It fixes oopses as well as this issue, so this issue is now moot. I installed it yesterday and it works. You need to follow the instructions in bug #61078 to make it go until it gets updated in the portage tree (involves copying 0.52 ebuild to 0.53 and then emerging).
Grrr. I guess it helps to actually <i>understand</i> Henrik's reply. Sorry. Ah well. Either way it works and this bug is now moot.
