From: Frans Pop <elendil@planet.nl>
To: Wei Chong Tan <weichong78@gmail.com>
Cc: sam@ravnborg.org, max@stro.at, linux-kernel@vger.kernel.org
Subject: Re: PATCH: ARCH in builddeb
Date: Tue, 22 Sep 2009 02:38:16 +0200 [thread overview]
Message-ID: <200909220238.17579.elendil@planet.nl> (raw)
In-Reply-To: <200909201509.14794.elendil@planet.nl>
On Sunday 20 September 2009, Frans Pop wrote:
> So, somehow dpkg is able to do the right thing based on what is set for
> gcc (I expect from the CROSS_COMPILE option), but not if that gets
> overruled as both your patches seem to be doing.
Actually, I think the correct way to build a linux kernel for i386 on an
amd64 [1] system is to use 'linux32 make deb-pkg' [2]. With that no
changes to the kernel build system should be needed at all, and I think
with that you even should not need to set the ARCH variable.
It should also be possible to build a 64-bit kernel for i386 on amd64 that
way using 'linux32 make ARCH=x86_64 deb-pkg'.
Untested, but AFAIK that should work. Sorry for not mentioning it earlier,
but it's a command I've never really used myself and I keep forgetting
about it :-/
Cheers,
FJP
[1] amd64 as in the Debian architecture, which also covers Intel 64-bit
[2] linux32 is in until-linux package and thus guaranteed to be available
next prev parent reply other threads:[~2009-09-22 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 5:25 PATCH: ARCH in builddeb Wei Chong Tan
2009-09-14 21:01 ` Frans Pop
2009-09-16 14:19 ` Frans Pop
2009-09-17 0:12 ` Wei Chong Tan
2009-09-18 3:10 ` Wei Chong Tan
2009-09-20 13:09 ` Frans Pop
2009-09-22 0:38 ` Frans Pop [this message]
2009-09-22 14:38 ` Frans Pop
2009-09-22 14:43 ` Wei Chong Tan
2009-09-22 16:53 ` Frans Pop
2009-09-22 23:07 ` Wei Chong Tan
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=200909220238.17579.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
--cc=sam@ravnborg.org \
--cc=weichong78@gmail.com \
/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