From: "Asbjørn Sloth Tønnesen" <asbjorn@asbjorn.biz>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
debian-kernel@lists.debian.org
Subject: Re: [PATCH] kbuild, deb-pkg: fix Architecture field when cross compiling
Date: Thu, 04 Nov 2010 01:42:29 +0000 [thread overview]
Message-ID: <4CD20F85.7040005@asbjorn.biz> (raw)
In-Reply-To: <4CD1E8C4.2020405@suse.cz>
On 11/03/2010 10:57 PM, Michal Marek wrote:
> I know very little about debian packaging, but shouldn't this be done in
> all cases, regardless of CROSS_COMPILE being set or not? You even show
> in the above example that in some cases you don't need CROSS_COMPILE to
> build a kernel for a different architecture.
I had a problem earlier with Kbuild ignoring ARCH if CROSS_COMPILE
wasn't set, but can't reproduce with the current kernel, but I also
started out with upgrading it from .26, since squeezes .32 doesn't work
on Soekris net4501. So this is no longer an issue.
The other reason for make it dependent on CROSS_COMPILE at least to
begin with is that the ARCH -> debarch translation table doesn't have to
be as complete since it doesn't break anything in the currently working
non-cross compile senario. If this doesn't matter then I will send a new
patch, that doesn't depend on CROSS_COMPILE being set.
I have CC'ed the debian-kernel list, for people not on LKML:
https://patchwork.kernel.org/patch/296182/
next prev parent reply other threads:[~2010-11-04 1:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 23:31 [PATCH] kbuild, deb-pkg: fix Architecture field when cross compiling Asbjoern Sloth Toennesen
2010-11-03 22:57 ` Michal Marek
2010-11-03 23:25 ` Michal Marek
2010-11-04 1:42 ` Asbjørn Sloth Tønnesen [this message]
2010-11-04 2:42 ` Asbjoern Sloth Toennesen
2010-11-04 3:38 ` Asbjørn Sloth Tønnesen
2010-11-04 3:44 ` Asbjoern Sloth Toennesen
2010-11-04 5:58 ` Sam Ravnborg
2010-11-04 12:29 ` Asbjørn Sloth Tønnesen
2010-11-04 12:36 ` Michal Marek
2010-11-04 13:33 ` Asbjørn Sloth Tønnesen
2010-11-05 12:32 ` [PATCH] kbuild, deb-pkg: select userland architectire based on UTS_MACHINE Asbjoern Sloth Toennesen
2010-11-05 12:41 ` maximilian attems
2010-11-05 13:29 ` Asbjørn Sloth Tønnesen
2010-11-05 13:30 ` [PATCH] kbuild, deb-pkg: select userland architecture " Asbjoern Sloth Toennesen
2010-11-05 13:36 ` maximilian attems
2010-11-05 13:42 ` Sven-Haegar Koch
2010-11-06 19:04 ` Asbjørn Sloth Tønnesen
2010-11-06 19:05 ` [PATCH] kbuild, deb-pkg: support overriding userland architecture Asbjoern Sloth Toennesen
2010-11-07 8:24 ` Américo Wang
2010-11-25 14:37 ` Michal Marek
2010-11-25 19:10 ` Sam Ravnborg
2010-12-08 21:35 ` [PATCH v2] " Asbjoern Sloth Toennesen
2010-12-09 14:24 ` maximilian attems
2010-12-09 15:23 ` Asbjørn Sloth Tønnesen
2010-12-09 15:24 ` [PATCH v3] " Asbjoern Sloth Toennesen
2010-12-09 15:34 ` Michal Marek
2010-12-09 15:42 ` Asbjørn Sloth Tønnesen
2010-12-12 17:39 ` [PATCH v4] " Asbjoern Sloth Toennesen
2010-12-20 15:53 ` Michal Marek
2010-12-03 17:48 ` [PATCH] " maximilian attems
2010-12-03 19:37 ` Asbjørn Sloth Tønnesen
2010-11-25 14:35 ` [PATCH] kbuild, deb-pkg: select userland architecture based on UTS_MACHINE Michal Marek
2010-11-05 12:44 ` [PATCH] kbuild, deb-pkg: select userland architectire " Asbjørn Sloth Tønnesen
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=4CD20F85.7040005@asbjorn.biz \
--to=asbjorn@asbjorn.biz \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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