Comment 14 for bug 666267

Revision history for this message
Michiel Bacchiani (michiel-bacchiani) wrote :

Checking out bca641b96bb12e4d892ad10498c7877e14d24abc

Author: Paolo Pisati <email address hidden>
Date: Wed Dec 14 17:23:24 2011 +0100

    UBUNTU: Ubuntu-3.0.0-1206.14

and cross compiling on an x86_64 for omap4 as, for example,

CROSS_COMPILE=arm-linux-gnueabi- do_tools=false dpkg-buildpackage -B -aarmel -uc -us

I am still left with x86_64 scripts as opposed to ARM executables causing DKMS issues installing the header package.

I see that the KBUILD_SCRIPTROOT "fix" was reverted.

commit d3cefbb1062fc018a476190043e76f680bf5e2f0
Author: Tim Gardner <email address hidden>
Date: Mon Nov 7 17:50:52 2011 +0000

    Revert "LINARO: Use KBUILD_SCRIPTROOT to cross build scripts"

    This reverts commit d18a6e2590dcde348e7ece6f5e2d76085663413b.

    Breaks cross compile in Oneiric x86 chroots.

With some persuasion, doing something along the lines of

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- KERNELVERSION=3.0.0-1206-omap4 CONFIG_DEBUG_SECTION_MISMATCH=y KBUILD_BUILD_VERSION="14" LOCALVERSION= localver-extra= O=<header_package_path> HOSTCC=arm-linux-gnueabi-gcc KBUILD_SCRIPTROOT=<build_omap4 path> -j1 silentoldconfig prepare scripts

seems to successfully build the ARM scripts. But that required me to make some edits to the make files.

Is this indeed still broken? Or am I missing the correct incantation for executing the cross compile?