Summary: | Madwifi-Driver fail to emerge and enter kernel source with 2.6.14-hardened-r4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rob M. <thehandoftyr> |
Component: | New packages | Assignee: | Mobile Herd (OBSOLETE) <mobile+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
madwifi-driver-0.1_pre20050420-r1 errors on emerge
Linux-2.6.14-hardened-r4 Errors for 11706 madwifi build errors from PORT_LOGDIR=/var/log/portage emerge madwifi-driver |
Description
Rob M.
2006-01-18 20:22:39 UTC
Created attachment 77495 [details]
madwifi-driver-0.1_pre20050420-r1 errors on emerge
errors on emerging the oldest drivers (~x86)
Created attachment 77496 [details]
Linux-2.6.14-hardened-r4
config for linux-2.6.14-hardened-r4
Please try with sys-kernel/hardened-sources-2.6.14-r4 and net-wireless/madwifi-driver-0.1401.20060117. Created attachment 77595 [details]
Errors for 11706 madwifi build
errors filed as requested
Please include the entire output from the command along with the command itself. Created attachment 77643 [details]
errors from PORT_LOGDIR=/var/log/portage emerge madwifi-driver
list of errors from "emerge madwifi"
Ok, what does `ls -ld /usr/src/linux/include/asm` say? Do you use KBUILD_OUTPUT to direct the objects from kernel compilation to a different directory? (In reply to comment #7) > Ok, what does `ls -ld /usr/src/linux/include/asm` say? no such file or directory. your direction led me to realize I needed to make a symlink from asm-i386 to asm. (I thought that was taken care of automatically on emerge?) by doing that, and by first doing a inital 'make' before emerging 'madwifi-driver', it is seeming to emerge OK. I need to test to make sure the drivers actually work, but the emerge part looks under control. I'll reboot, and if the drivers work you can mark this CLOSED (unless the symlink was supposed to be made automatically) (In reply to comment #7) the drivers appear to be working just fine - thanks for all of your help! mark CLOSED if appropriate The symlink is made when calling `make` in the kernel sources. Closing as INVALID. |