From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from 75.98.165.80.static.a2webhosting.com ([75.98.165.80]:46800 "EHLO greenroomsoftware.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752216Ab1EMCuS (ORCPT ); Thu, 12 May 2011 22:50:18 -0400 Message-ID: <4DCC9C5F.2000301@greenroomsoftware.com> Date: Thu, 12 May 2011 19:50:07 -0700 From: Robert Gordon MIME-Version: 1.0 Subject: Re: [PATCH 1/1] deb-pkg: fix cross-compile build References: <1304488750-13606-1-git-send-email-subtil@gmail.com> <20110504204807.GB13293@sepie.suse.cz> <20110505090728.GC30678@vostochny.stro.at> <4DC2C568.9090803@greenroomsoftware.com> <4DC2EB2B.1050203@greenroomsoftware.com> <20110510124123.GE13278@vostochny.stro.at> <4DCBE83C.2080403@greenroomsoftware.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Nuno Subtil Cc: maximilian attems , Michal Marek , linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org On 5/12/11 12:45 PM, Nuno Subtil wrote: >> The debian/control file for an unpatched scripts/package/builddeb would >> assign 'i386' instead of 'amd64'. > > That seems wrong to me. Were the resulting packages actually usable on amd64? I modeled my patch after behavior I saw in the unpatched script. I had also originally set x86_64 to amd64 with the exact results I get with your patch. So, I looked at what the unpatched kernel was doing, which is putting i386 in those fields when building for x86_64 on an i386 machine. I don't know the results would actually run because I don't have an x86_64 myself. It may not run, but it does build. cheers! -- *www.greenroomsoftware.com*