Hi Ian, On Monday 13 November 2006 03:20, Ian MacDonald wrote: > Package: madwifi-source > Version: 1:0.9.2+r1784.20061027-1 > Severity: important > > The following is from the buildlog after executing #m-a a-i madwifi > > dh_testroot > dh_clean > /usr/bin/make -C /usr/src/modules/madwifi clean \ > KERNELPATH=/lib/modules/2.6.18-1-powerpc/build > KERNELRELEASE=2.6.18-1-powerpc > KERNELCONF=/lib/modules/2.6.18-1-powerpc/build/.config > ATH_RATE=ath_rate/sample > make[2]: Entering directory `/usr/src/modules/madwifi' > Makefile.inc:199: *** TARGET powerpc-elf is invalid, valid > targets are: alpha-elf ap30 ap43 ap51 ap61 arm9-le-thumb-elf > armv4-be-elf armv4-le-elf i386-elf mips1-be-elf mips1-le-elf > mips-be-elf mipsisa32-be-elf mipsisa32-le-elf mips-le-elf > powerpc-be-eabi powerpc-be-elf powerpc-le-eabi sh4-le-elf > sparc64-be-elf sparc-be-elf x86_64-elf xscale-be-elf > xscale-le-elf. Stop. > > Looking at the differences between the 1704 (which built fine) and 1784 > builds I noted the following changes: The /scripts/get_arch_target.sh was > replaced with /scripts/get_arch.sh > > In here there was previously some logic to add the "endianness" to the > TARGET; i.e. change TARGET=powerpc-elf to TARGET=powerpc-be-elf. This logic > seems to have been purged, or possibly moved elsewhere. > > Note that the debian patch07 to get_arch_target.sh (which no longer > exists after the rename) was in the changelog. Not sure if that was > still being patched, but if so needs to be updated. > > The workaround for PPC32-be users familiar with the module building > process is to just to drop a > TARGET=powerpc-be-elf into the /usr/src/modules/madwifi/Makefile.inc and > rebuild madwifi.tar.bz2, and re-execute m-a a-i madwifi.
I forwarded this onto the upstream mailing list this morning[1] where Pavel Roskin stated[2] this is a problem he wants to fix very soon. Thanks, Kel. [1] http://article.gmane.org/gmane.linux.drivers.madwifi.devel/3449 [2] http://article.gmane.org/gmane.linux.drivers.madwifi.devel/3450 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]