Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 64416 - ndiswrapper broken when using koutput-enabled kernel configuration
Summary: ndiswrapper broken when using koutput-enabled kernel configuration
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Mobile Herd (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-17 09:43 UTC by Kevin Williams
Modified: 2004-10-03 22:30 UTC (History)
1 user (show)

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


Attachments
Fix for koutput enabled kernel (ndiswrapper.patch,467 bytes, patch)
2004-09-24 01:16 UTC, marchino
Details | Diff
A better (=working ;-) ) fix (ndiswrapper.patch,522 bytes, patch)
2004-09-24 01:35 UTC, marchino
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Williams 2004-09-17 09:43:52 UTC
I just set up my kernel with the koutput option (config-kernel --output-dir /var/tmp/kernel-output) and began updating my extra kernel modules. The net-wireless/ndiswrapper-0.10 ebuild gives me this error:


You don't seem to have sources for your kernel;  install them in /usr/src, link //usr/src/linux to it and try again.
Comment 1 Devon Jones 2004-09-23 09:48:40 UTC
I show the same error with kernel 2.6.8-gentoo-r3.  I looekd at the make file for ndiswrapper, and it seems to be looking for some kernel files in the wrong places (probably these files got moved) such as /usr/src/linux/includes/version.h

I am using genkernel, it's possible this is the culprit.

Running a 'make && make modules && make modules_install' to see if that helps
Comment 2 Devon Jones 2004-09-23 10:31:56 UTC
ok, I have confirmed - the issue is if you use genkernel.  As a work around until there is a fix for this, build your kernel once by hand and ndiswrapper will build fine.

Comment 3 Kevin Williams 2004-09-23 16:06:27 UTC
It's not just genkernel. By using the new config-kernel tool to specify an alternate build output, external kernel modules cannot find the objects they need to link to. Apparently genkernel now uses this tool.

http://packages.gentoo.org/ebuilds/?config-kernel-0.3.3
Comment 4 marchino 2004-09-24 01:16:04 UTC
Created attachment 40277 [details, diff]
Fix for koutput enabled kernel

It let build ndiswrapper if you're using koutput, it doesn't check anything, so
a better fix is needed.
Comment 5 marchino 2004-09-24 01:35:49 UTC
Created attachment 40278 [details, diff]
A better (=working ;-) ) fix

This fix should work better ;)
Comment 6 Doug Goldstein (RETIRED) gentoo-dev 2004-10-03 22:30:17 UTC
koutput is depreciated and no longer used maintained. This is because of the build system fixes that the kernel developers commited to the 2.6.6 kernel. As as result, it is no longer supported by Gentoo Mobile team.

Below is the post to gentoo-dev mailing list by the creator of the koutput system.

Hey all,

Been busy with lots of other things, and dreading sending this anyway,
but I wanted to clear things up Re: the koutput/kbuild stuff that I'd
worked on to fix some problems previously related to 2.6 kernel build
issues.

Unfortunately, the fix that was 95% implemented, and had the beginnings
of code in the tree got ham-strung by a combination of kernel stuff
changing under my/our feet, and Real Life (tm) things coming in at just
the wrong time.

As a result, the kmod.eclass, and config-kernel have several problems,
and are only 1/2 implemented anyway. Sooo, don't use kmod.eclass. Just
don't. config-kernel i will be package.masking as well soon. I know
there are a few ebuilds out there that currently use kmod.eclass for a
few things. I'll be contacting those maintainers over the next few days
to address things with them, and get them sorted out with how to get
things working with 2.6.6 and newer kernels. If you get any bugs from
people complaining about such and such ebuild not working with koutput,
assing or CC me, and i'll deal with it. Thanks.

Sorry for any confusion folks.

-pete