From: maximilian attems <max@stro.at>
To: Asbjoern Sloth Toennesen <asbjorn@asbjorn.biz>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
debian-kernel@lists.debian.org
Subject: Re: [PATCH] kbuild, deb-pkg: support overriding userland architecture
Date: Fri, 3 Dec 2010 18:48:00 +0100 [thread overview]
Message-ID: <20101203174800.GA952@stro.at> (raw)
In-Reply-To: <1289070320-20726-1-git-send-email-asbjorn@asbjorn.biz>
hello Asbjoern,
On Sat, 06 Nov 2010, Asbjoern Sloth Toennesen wrote:
> Usefull if building for sparc64 userland, because the
> sparc and sparc64 userlands use the same 64-bit kernel,
> making it impossible to always select the correct userland
> architecture for the resulting debian package.
>
> Might also be usefull, if you want a i386 userland with a amd64 kernel.
>
> Example usage:
> make DEBARCH=i386 deb-pkg
>
> This patch is based on my 'kbuild, deb-pkg: select
> userland architecture based on UTS_MACHINE' patch.
care to repost with KBUILD_ prefix, to keep namespace sane and mention
in Documentation/kbuild/kbuild.txt together with the relevant acks.
It be really cool to have that in next 2.6.38.
thanks
> LKML-reference: <alpine.DEB.2.02.1011051437500.13287@aurora.sdinet.de>
> Signed-off-by: Asbjoern Sloth Toennesen <asbjorn@asbjorn.biz>
Acked-by: maximilian attems <max@stro.at>
next prev parent reply other threads:[~2010-12-03 17:48 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
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 ` maximilian attems [this message]
2010-12-03 19:37 ` [PATCH] " 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=20101203174800.GA952@stro.at \
--to=max@stro.at \
--cc=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