Arnaud, First of all, when it started, I thought it was a kbuild (and friends) question. But after I found the solution, I thought of that, and after thinking twice, it looked to me that the problem would (or should?) have been the same on other archs that support multiple bitnesses in a single arch, like ARM, PPC, MIPS, even good'ole s390 or whatever. When I looked at the gcc (cross or not cross?) for instance, it appeared that the -m32 / -m64 option wasn't specific to x86 but existed in other archs. I suspect that menuconfig behaves more or less the same about the bitness in other archs too (OK, I admit, I didn't check that *at all* ;-) ) And here again, if it doesn't right now, I have a feeling that it eventually should. The reasons behind the unification of i386 and x86_64 back in 2007-2008 apply just the same to other architectures, and if there are still some that haven't been unified, I bet they will one day. The solution ended up being a better understanding / explaination about - what gcc is able to do natively, without a cross toolchain, in a given architecture with different bitnesses, - how to use kbuild with multiple "remote" target directories, - a peculiarity with menuconfig Admittedly, I didn't make any deep check on any of the other archs, though. But still, unless I'm missing something big, not much of this seems really soooo x86 specific after all. And all things considered, I'm still unsure whether I should really double-post this on the x86 list... /PhA. -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
