linux-kernel - Re: PATCH: ARCH in builddeb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 Sep 2009 02:38:16 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Wei Chong Tan <weichong78@...il.com>
Cc:	sam@...nborg.org, max@...o.at, linux-kernel@...r.kernel.org
Subject: Re: PATCH: ARCH in builddeb

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/