Hi Fathi,
This seems like something that module-assistant could/should provide, so that
_all_ modules benefit, rather than a ndiswrapper specific hack.
If it turns out that ndiswrapper is actually at fault, and not just a victim
of some gcc transistion, then we can do something locally.
What d
Package: ndiswrapper
Severity: normal
hi,
due to recent changes in gcc default version (4.1), we have again a
compilation using the wrong gcc as kernel are built with 4.0
As a workaround, i used MAKEFLAGS="CC=gcc-4.0" m-a build ndiswrapper
Could we have a long term solution like detecting which
2 matches
Mail list logo