On 9.8.2013 17:27, Mark Brown wrote: > On Fri, Aug 09, 2013 at 05:13:46PM +0200, Sam Ravnborg wrote: >> On Fri, Aug 09, 2013 at 04:00:31PM +0100, Mark Brown wrote: > >>> OK... I'd have thought that cross compliation was enough of a rationale >>> to be honest. > >> The way I understand cross compilation is that for example you >> build for arm - on your x86 box. >> This is supported today. > >> So you need to explain your interpretation of cross compilation >> and why this patch is needed. >> Because I do not get it. > > I thought that was covered by: > > Cross compiling the binaries in scripts/* is not possible > because various makefiles assume that $(obj)/whatever is > executable on the build host. > > ie, we can cross build the kernel but not fixdep, conf or mk_elfconfig > since those are assumed to be runnable for the kernel build, meaning > they can't be deployed onto a target system without hoop jumping. OK, but what what do you need cross compile them and deploy on the target? Their job is to build the kernel. So if you are going to build the kernel on the target, you can also build the tools there, can't you? Or are you using the tools from something else than building the kernel? I think that we are missing some detail of your use case and it does not make sense without that detail. 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
