Re: [patch 3/3] kconfig CROSS_COMPILE option

[Michal Marek <mmarek@suse.cz>]

On 17.11.2009 23:45, akpm@linux-foundation.org wrote:
> From: Roland McGrath <roland@redhat.com>
> 
> This adds CROSS_COMPILE as a kconfig string so you can store it in
> .config.  Then you can use plain "make" in the configured kernel build
> directory to do the right cross compilation without setting the
> command-line or environment variable every time.
> 
> With this, you can set up different build directories for different kernel
> configurations, whether native or cross-builds, and then use the simple:
> 
> 	make -C /build/dir M=module-source-dir
> 
> idiom to build modules for any given target kernel, indicating which one
> by nothing but the build directory chosen.
> 
> I tried a version that defaults the string with env="CROSS_COMPILE" so
> that in a "make oldconfig" with CROSS_COMPILE in the environment you can
> just hit return to store the way you're building it.  But the kconfig
> prompt for strings doesn't give you any way to say you want an empty
> string instead of the default, so I punted that.

This was posted in September, then superseded by the "save ARCH &
CROSS_COMPILE" patch (commit 5755433), which was then reverted because
it was causing too many issues (commit 2331d1a). In light of the revert,
I think I like Roland's patch: It's an optional feature, i.e if one does
not set the config option, nothing changes. So unless someone sees a
problem that I'm not seeing, I'll add this to for-next.

How to check for $ARCH consistency after the include/asm symlink removal
is another problem, separate from this.

Michal