Ok, I checked with mjg59. He says that the only difference between 386/586/686 flavors of RHEL is the kernel config, which leads to different compiler optimizations. The ARCH string has nothing to do with that.
So passing either "i386" or "x86" to force a 32-bit build is perfectly safe, even for RHEL. Alternatively, you could just read the top-level kernel Makefile and search for "uname -m". You'll see what we do with SUBARCH and ARCH; a little further down, you can see the x86-specific section for SRCARCH. I think the patch might break if we try to build a 64-bit module on a 32-bit host, I haven't tested that combo; but it should be extremely rare anyway. -- allow 32-bit module build on 64-bit host https://bugs.launchpad.net/bugs/655275 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
