On 1.10.2012 01:20, Jason Gunthorpe wrote:
> To make cross building a little simpler. The usage with mini-config would
> be something like:
>
> $ mkdir build
> $ make ARCH=arm CROSS_COMPILE=arm-v5te-linux-gnueabi- \
> KCONFIG_ALLCONFIG=mini.config O=build allnoconfig
> $ make -C build/
Are you sure this is not going to suffer from the same issues as
5755433? See
commit 2331d1a6cd3d6e580bc88b9a160066d9e1177fe1
Author: Sam Ravnborg <sam@xxxxxxxxxxxx>
Date: Sun Oct 11 23:22:58 2009 +0200
kbuild: revert "save ARCH & CROSS_COMPILE ..."
Revert commit 575543347b5baed0ca927cb90ba8807396fe9cc9
It caused following issues:
- On architectures where ARCH= setting is used to select between
32 and 64 bit this was no longer possible without "make mrproper"
- If ARCH was changed then kbuild refused to run "make mrproper"
because ARCH had changed
- When CROSS_COMPILE was changed people were asked to run "make
mrproper"
but kbuild refused to run "make mrproper" because CROSS_COMPILE
changed.
- Spaces in CROSS_COMPILE was not 'supported'
- If an non-existing ARCH= was used kbuild could get stuck
Lessons learned:
. Despite being simple and straghtforward people uses very different
approaches when building the kernel.
. CROSS_COMPILE is sometimes used for ccache despite cache being
only a CC frontend so one would have expected CC to be
used for this purpose.
. And obviously this was not tested widely enough.
Michal
--
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
