Madwifi-Driver will not emerge at all with 2.6.14-hardened-r4. this is repeatable at will. I've tried - first, emerging 1. net-wireless/madwifi-driver-0.1_pre20050420-r1, (~x86) then, emerging 2. madwifi-driver-0.1_pre20051111, and brix's net-wireless overlay of madwifi-driver with madwifi-driver-0.1401.20060117 from http://dev.gentoo.org/~brix/files/overlay/net-wireless/madwifi-driver/ (~x86, package.mask) emerge --info for madwifi-drivers is as follows, my .config and error messages will be added as files. --- Portage 2.0.53 (hardened/x86/2.6, gcc-3.3.6, glibc-2.3.4.20041102-r1, 2.6.14-hardened-r3 i686) ================================================================= System uname: 2.6.14-hardened-r3 i686 Intel(R) Pentium(R) M processor 1.60GHz Gentoo Base System version 1.12.0_pre8 ccache version 2.3 [enabled] dev-lang/python: 2.3.5-r2, 2.4.1-r1 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i586-pc-linux-gnu" CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer -fforce-addr" CHOST="i586-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer -fforce-addr" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" PKGDIR="/usr/portage//packages/x86/" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage/" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 Oozp3p X X509 acpi aim alsa audiofile avi bash-completion berkdb bitmap-fonts bluetooth browserplugin bzip2 cap caps cdr chroot cracklib crypt cscope cups curl dlloader droproot dvd dvdread ecc eds emacs esd ethereal exif expat fam fbcon ffmpeg flac fortran gd gdbm geoip gif glut gmail gmp gnome gpm gps gstreamer gtk gtk2 gtkhtml guile hardened icq idn imagemagick imap imlib jabber java jce jpeg junit kerberos lcms ldap libreadline libwww mad madwifi-HEAD mhash mng motif mozilla mp3 mpeg multitarget mysql mysqli mysqlpnp ncurses nls nsplugin ocaml octave offensive ogg openal opengl oscar pam pam_chroot pam_console pam_timestamp pcap pcmcia pcre pdflib perl pic pie png postgres prelude prism54 python qemu-fast qt readline ruby sdl silc skey slang smime sockets ssl svg symlink tcltk tcpd tetex theora tiff truetype truetype-fonts udev usb userlocales vcd vorbis wifi win32codecs wlan wxwindows xine xinerama xml xml2 xmms xv xvid yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
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.