Hi, On Wed, Jan 12, 2011 at 12:33 PM, Philippe Auphelle <pauphelle@xxxxxxxxx> wrote: > Hi, > > Running a 2.6.35 kernel, and gcc 4.4.5, I'm trying to build both an > x86 (32) and an x86_64 external (out of tree) module from my x86 > (32-bit) dev machine. > > I have tried various tricks, such as using ARCH=X86_64 when running > make, but to no avail so far: Whatever I do, V=1 shows kbuild invoking > gcc with -m32 and ld with elf_i386. > > I have googled around for a few hours without finding a solution to > the problem. > Since the x86 arch is unified and gcc is able to gen (and link) x86_64 > targets, it looks like this could be done, and I must be missing > something. > Could anyone point me to the right direction? > I suppose that you ensured that your kernel tree when you are building for x86-32 has been "prepared" for building for x86-32, and that you are using a dedicated x86-64 config and preparation when you try to build for x86-64 ? I'm just asking because I reproduced what I guess you are seeing using an ARCH=x86 config&prep tree on an x86-64 machine. When I try to build the module with ARCH=x86_64, -m32 is still specified. At least, there should be a test to assert that CONFIG_ARCH == ARCH when building a external module. While at this, I also think the build should die and report an error when trying to build an external modules when "CONFIG_MODULES is not set". Currently the build just fails miserably :/ [yes, that's a different issue.] Thanks, - Arnaud -- 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
