All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Gordon <robert@greenroomsoftware.com>
To: Nuno Subtil <subtil@gmail.com>
Cc: maximilian attems <max@stro.at>, Michal Marek <mmarek@suse.cz>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] deb-pkg: fix cross-compile build
Date: Thu, 12 May 2011 19:50:07 -0700	[thread overview]
Message-ID: <4DCC9C5F.2000301@greenroomsoftware.com> (raw)
In-Reply-To: <BANLkTi=e62Whz+jyW-MtCN-nYGwUUBR6sg@mail.gmail.com>

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*

  reply	other threads:[~2011-05-13  2:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04  5:59 [PATCH 1/1] deb-pkg: fix cross-compile build Nuno Subtil
2011-05-04 20:48 ` Michal Marek
2011-05-05  9:07   ` maximilian attems
2011-05-05 15:42     ` Robert Gordon
2011-05-05 17:10       ` Nuno Subtil
     [not found]         ` <4DC2EB2B.1050203@greenroomsoftware.com>
2011-05-05 18:34           ` Robert Gordon
2011-05-10  5:29           ` Nuno Subtil
2011-05-10 12:41             ` maximilian attems
2011-05-12 14:01               ` Robert Gordon
2011-05-12 19:45                 ` Nuno Subtil
2011-05-13  2:50                   ` Robert Gordon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-10  5:25 Nuno Subtil

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=4DCC9C5F.2000301@greenroomsoftware.com \
    --to=robert@greenroomsoftware.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@stro.at \
    --cc=mmarek@suse.cz \
    --cc=subtil@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.