public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Mark Brown <broonie@kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	linaro-kernel@lists.linaro.org, linux-kbuild@vger.kernel.org,
	John Rigby <john.rigby@linaro.org>
Subject: Re: [PATCH] kbuild: Allow scripts/* to be cross compiled
Date: Fri, 09 Aug 2013 17:35:39 +0200	[thread overview]
Message-ID: <52050C4B.2060606@suse.cz> (raw)
In-Reply-To: <20130809152748.GF6427@sirena.org.uk>

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

  reply	other threads:[~2013-08-09 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 11:07 [PATCH] kbuild: Allow scripts/* to be cross compiled Mark Brown
2013-08-09 12:32 ` Sam Ravnborg
2013-08-09 15:00   ` Mark Brown
2013-08-09 15:13     ` Sam Ravnborg
2013-08-09 15:27       ` Mark Brown
2013-08-09 15:35         ` Michal Marek [this message]
2013-08-09 16:08           ` Mark Brown
2013-08-09 12:36 ` Michal Marek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52050C4B.2060606@suse.cz \
    --to=mmarek@suse.cz \
    --cc=broonie@kernel.org \
    --cc=john.rigby@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox