Right, and a Debian armhf system has the following settings: DEB_HOST_ARCH=armhf DEB_HOST_ARCH_BITS=32 DEB_HOST_ARCH_CPU=arm DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH_OS=linux DEB_HOST_GNU_CPU=arm DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf
so if platform-is-supported wants to use the value of DEB_HOST_ARCH_CPU, it has to test for arm; if it wants to use DEB_HOST_ARCH, it has to test for armhf. I could have made either change (x86 and amd64 seem to have the same values for ARCH and ARCH_CPU), but I chose to stick with DEB_HOST_ARCH_CPU checking, and just change the value to the one that would actually be furnished. Jeff ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
