madwifi ARCH emerge failure
Could someone please explain this error to me:
============================================== * Converting madwifi-0.9.3.3/ath_rate/onoe/Makefile to use M= instead of SUBDIRS= ... [ ok ] * Converting madwifi-0.9.3.3/ath_rate/sample/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Source unpacked. >>> Compiling source in /var/tmp/portage/net-wireless/madwifi-ng-0.9.3.3/work/madwifi-0.9.3.3 ... * Preparing ath_hal module ../scripts/get_arch.mk:44: *** ARCH mismatch: supplied "x86", determined "i386". Stop. * * ERROR: net-wireless/madwifi-ng-0.9.3.3 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3184: Called linux-mod_src_compile * environment, line 2433: Called die * The specific snippet of code: * eval "emake HOSTCC="$(tc-getBUILD_CC)" CC="$(get-KERNEL_CC)" LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CC="$(get-KERNEL_CC)" LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CC=i686-pc-linux-gnu-gcc LDFLAGS= KERNELPATH=/lib/modules/2.6.24-gentoo-r8/build all * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/net-wireless:madwifi-ng-0.9.3.3:20080607-150744.log'. * The ebuild environment file is located at '/var/tmp/portage/net-wireless/madwifi-ng-0.9.3.3/temp/environment'. * ============================================== Where is the i386 coming from? -- Regards, Mick |
| All times are GMT. The time now is 09:50 PM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.