All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Levon <john.levon@sun.com>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Fix 64-bit foreign header check
Date: Wed, 15 Aug 2007 17:08:23 +0100	[thread overview]
Message-ID: <20070815160823.GA10743@barman.uk.sun.com> (raw)
In-Reply-To: <C2E8E29E.143F3%keir@xensource.com>

On Wed, Aug 15, 2007 at 05:04:30PM +0100, Keir Fraser wrote:

> > There is no such "32-bit" environment, we can always produce both.  What
> > you're
> > suggesting sounds like a cross-compile. This is absolutely not a cross
> > compile;
> > in particular we can and do want this header check to happen.
> > 
> > We set XEN_COMPILE_ARCH by hand to 64-bit since the Xen makefiles have the
> > notion
> > that uname has anything to do with 32 or 64 bitness (a Linux-ism; in fact an
> > x86_64-Linux-ism, since I believe other Linux arches do it the traditional
> > way).
> 
> Hmmm... Well varying COMPILE_ARCH when the compile arch is not actually
> changing seems dodgy to me.
>
> In any case, binaries that run on the compile host should build with
> HOSTCC/HOSTCFLAGS. That seems a pretty simple and obvious rule that I do not
> want to introduce exceptions to.

Can you please explain what you want us to do.

john

  reply	other threads:[~2007-08-15 16:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 14:20 [PATCH] Fix 64-bit foreign header check john.levon
2007-08-15 14:24 ` Keir Fraser
2007-08-15 14:37   ` John Levon
2007-08-15 14:59     ` Keir Fraser
2007-08-15 15:27       ` John Levon
2007-08-15 16:04         ` Keir Fraser
2007-08-15 16:08           ` John Levon [this message]
2007-08-16  7:15             ` Keir Fraser
2007-08-15 16:09           ` John Levon
  -- strict thread matches above, loose matches on Subject: below --
2007-08-16 13:23 john.levon

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=20070815160823.GA10743@barman.uk.sun.com \
    --to=john.levon@sun.com \
    --cc=keir@xensource.com \
    --cc=xen-devel@lists.xensource.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.