Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 60424 - madwifi-driver-0.1_pre20040726 does not compile with linux-
Summary: madwifi-driver-0.1_pre20040726 does not compile with linux-
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Mobile Herd (OBSOLETE)
: 60626 (view as bug list)
Depends on:
Reported: 2004-08-15 10:11 UTC by Stephen Tallowitz
Modified: 2005-05-21 14:21 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---

proc_dointvec.patch (proc_dointvec.patch,1.69 KB, patch)
2004-08-26 01:19 UTC, Per Cederberg
Details | Diff
madwifi-driver-0.1_pre20040824.ebuild.patch (madwifi-driver-0.1_pre20040824.ebuild.patch,427 bytes, patch)
2004-08-26 01:33 UTC, Per Cederberg
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Tallowitz 2004-08-15 10:11:20 UTC
I didn't have any problems compiling madwifi-driver against kernel 2.6.7, but with recent (development-sources) this is the error message:

/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c: In function `ath_sysctl_handler':
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3389: error: too few arguments to function `proc_dointvec'
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c: At top level:
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3417: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3420: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3422: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3424: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3426: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3428: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3430: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3432: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3434: warning: initialization from incompatible pointer type
distcc[7121] ERROR: compile on localhost failed
make[3]: *** [/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.o] Error 1
make[2]: *** [_module_/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver] Error 2
make[2]: Leaving directory `/usr/src/linux-'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver'
make: *** [all] Fehler 2

!!! ERROR: net-wireless/madwifi-driver-0.1_pre20040726 failed.
!!! Function src_compile, Line 43, Exitcode 2
!!! (no error message)

By the way: I used the same config to compile kernel 2.6.7 and

Reproducible: Always
Steps to Reproduce:
1. emerge, compile & install kernel (development-sources) & boot with new kernel
2. try emerging madwifi-driver

Actual Results:  
compiler error

Expected Results:  
compile madwifi cleanly

You might want to see a bug filed on the project homepage:
Comment 1 ChazeFroy 2004-08-16 20:50:46 UTC
I have the exact same problems as you.  madwifi-driver-0.1_pre20040726.ebuild compiled fine in 2.6.7 (official vanilla sources), but it fails with the error you mentioned above with (official vanilla sources).
Comment 2 Hunter Cook 2004-08-18 13:32:56 UTC
I'm also having the identical problem with gentoo-dev-sources-2.6.8-r1
Comment 3 Jan Mentzel 2004-08-21 05:22:15 UTC
same problem with gentoo-dev-sources-2.6.8 here.
Comment 4 Jan Callewaert 2004-08-23 05:30:45 UTC
Same problem here. I have found a patch on, but I don't know how to patch the ebuild.
Comment 5 Per Cederberg 2004-08-26 01:19:58 UTC
Created attachment 38225 [details, diff]

Cleaned up the patch originating at the SourceForge site (linked from a
previous comment) by removing unneeded/mistakenly included stuff. It should now
apply cleanly to madwifi-driver-0.1_pre20040824 (without any line relocations).
Comment 6 Daniel Drake (RETIRED) gentoo-dev 2004-08-26 01:21:15 UTC
*** Bug 60626 has been marked as a duplicate of this bug. ***
Comment 7 Per Cederberg 2004-08-26 01:33:39 UTC
Created attachment 38228 [details, diff]

Fixed the madwifi ebuild to apply the previous patch.
Comment 8 Per Cederberg 2004-08-26 01:38:18 UTC
Don't know if anybody needs this, but here are the instructions on how to apply the previous two patches (simple but dirty way):

1. cp proc_dointvec.patch /usr/portage/net-wireless/madwifi-driver/files
2. cd /usr/portage/net-wireless/madwifi-driver
3. patch -p0 < madwifi-driver-0.1_pre20040824.ebuild.patch
4. ebuild madwifi-driver-0.1_pre20040824.ebuild digest
5. ACCEPT_KEYWORDS=~x86 emerge madwifi-driver-0.1_pre20040824

Hope it works for you too!
Comment 9 Cory Meisch 2004-08-29 13:46:04 UTC
Also occurs on 2.6.8-r3. Patch works to resolve.
Comment 10 Hunter Cook 2004-08-31 11:59:52 UTC
Things work now with gentoo-dev-sources 2.6.8-r3 and madwifi-driver 0.1_pre20040824-r1. I don't know if that patch was merged or what, but thanks for whomever fixed it...

Comment 11 reillyp 2004-09-01 04:12:57 UTC
Compiles, but in use tells me that the card cannot go into scan mode.
Comment 12 Per Cederberg 2004-09-01 04:43:40 UTC
Mobile Herd: Seems solar has fixed this but not marked this bug as resolved:

  29 Aug 2004; <>
  update for 2.6.8 kernels

reillyp: I suspect that the problem you mention in comment #11 is not related to this bug or the resolution. The patch applied in the new ebuild seems only to adjust for a Linux driver API change.

Maybe you should open another bug describing the exact problems you have? Also, you might want to check the SourceForge bug tracker (although I couldn't find anything similar from a quick look):
Comment 13 solar (RETIRED) gentoo-dev 2004-09-01 09:14:00 UTC
I was not on the CC: of this bug.

Are we happy with madwifi-driver now? Any reason to not mark 0.1_pre20040824-r1 stable? Who has tested on 2.4.x kernels?
Comment 14 solar (RETIRED) gentoo-dev 2004-09-01 09:45:31 UTC
changing resolution to TEST-REQUEST
Comment 15 Per Cederberg 2004-09-01 13:56:55 UTC
Happy? Yes.

Stable? Not really 100%, but (it seems) it is the only option for this hardware. I have experienced total hangs when combining with iproute2 (used by wondershaper) from time to time. Irritating but not frequent enough to merit further investigation (not sure it is even this driver).

2.4 kernels? Works on Debian with CVS from sometime in March, but I haven't tested on Gentoo with a 2.4 kernel.
Comment 16 Jan Callewaert 2004-09-02 01:04:36 UTC
it works for me in gentoo-dev-sources-2.6.8-r3. No hitches whatsoever.
Comment 17 Henrik Brix Andersen 2005-05-21 14:21:00 UTC
Closing as per comment #16.