From: Aron Griffis <aron@hp.com>
To: Keir Fraser <keir.fraser@citrix.com>, Bastian Blank <waldi@debian.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-staging] [xen-unstable] ioemu: Use XEN_TARGET_ARCH instead of uname -m.
Date: Sun, 27 Jan 2008 16:38:05 -0500 [thread overview]
Message-ID: <20080127213805.GA14096@fc.hp.com> (raw)
In-Reply-To: <200801221436.m0MEaU7Q030779@latara.uk.xensource.com>
Keir, Bastian,
What is this changeset intended to fix? My cross-compilation seems to
work fine without it. With it, the cross-compile blows up because the
custom ld-script doesn't handle a sys-root (i.e. it overrides the
linker, gross!)
By my reading, this patch overrides the host CPU detection with
XEN_TARGET_ARCH, but that's incorrect because the host CPU should be
the machine on which ioemu is being built, right?
Thanks,
Aron
Xen staging patchbot-unstable wrote: [Tue Jan 22 2008, 09:36:29AM EST]
> # HG changeset patch
> # User Keir Fraser <keir.fraser@citrix.com>
> # Date 1201012477 0
> # Node ID 51a7e508bd01a1a7d083eada58062aa7b08b839b
> # Parent 5e03f0bc0aa2fbe8535bedca02d6ab6e4b530794
> ioemu: Use XEN_TARGET_ARCH instead of uname -m.
>
> Signed-off-by: Bastian Blank <waldi@debian.org>
> ---
> tools/Makefile | 2 +-
> tools/ioemu/configure | 36 ++++--------------------------------
> 2 files changed, 5 insertions(+), 33 deletions(-)
>
> diff -r 5e03f0bc0aa2 -r 51a7e508bd01 tools/Makefile
> --- a/tools/Makefile Tue Jan 22 14:31:10 2008 +0000
> +++ b/tools/Makefile Tue Jan 22 14:34:37 2008 +0000
> @@ -78,7 +78,7 @@ endif
> endif
> ioemu ioemuinstall:
> [ -f $(IOEMU_DIR)/config-host.mak ] || \
> - ( cd $(IOEMU_DIR) && sh configure --prefix=/usr \
> + ( cd $(IOEMU_DIR) && XEN_TARGET_ARCH=$(XEN_TARGET_ARCH) sh configure --prefix=/usr \
> $(IOEMU_CONFIGURE_CROSS) )
> $(MAKE) -C $(IOEMU_DIR) $(patsubst ioemu%,%,$@)
> ioemuclean:
> diff -r 5e03f0bc0aa2 -r 51a7e508bd01 tools/ioemu/configure
> --- a/tools/ioemu/configure Tue Jan 22 14:31:10 2008 +0000
> +++ b/tools/ioemu/configure Tue Jan 22 14:34:37 2008 +0000
> @@ -29,43 +29,15 @@ make="make"
> make="make"
> install="install"
> strip="strip"
> -cpu=`uname -m`
> target_list=""
> -case "$cpu" in
> - i386|i486|i586|i686|i86pc|BePC)
> +case "$XEN_TARGET_ARCH" in
> + x86_32)
> cpu="i386"
> ;;
> - armv*b)
> - cpu="armv4b"
> - ;;
> - armv*l)
> - cpu="armv4l"
> - ;;
> - alpha)
> - cpu="alpha"
> - ;;
> - "Power Macintosh"|ppc|ppc64)
> + powerpc)
> cpu="powerpc"
> ;;
> - mips)
> - cpu="mips"
> - ;;
> - s390)
> - cpu="s390"
> - ;;
> - sparc|sun4[muv])
> - cpu="sparc"
> - ;;
> - sparc64)
> - cpu="sparc64"
> - ;;
> - ia64)
> - cpu="ia64"
> - ;;
> - m68k)
> - cpu="m68k"
> - ;;
> - x86_64|amd64)
> + x86_64)
> cpu="x86_64"
> libdir="lib64"
> ;;
>
> _______________________________________________
> Xen-staging mailing list
> Xen-staging@lists.xensource.com
> http://lists.xensource.com/xen-staging
>
next parent reply other threads:[~2008-01-27 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200801221436.m0MEaU7Q030779@latara.uk.xensource.com>
2008-01-27 21:38 ` Aron Griffis [this message]
2008-01-27 22:21 ` Re: [Xen-staging] [xen-unstable] ioemu: Use XEN_TARGET_ARCH instead of uname -m Keir Fraser
2008-01-27 23:04 ` Aron Griffis
2008-01-28 8:10 ` Keir Fraser
2008-01-28 9:32 ` Keir Fraser
2008-01-28 1:01 ` 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=20080127213805.GA14096@fc.hp.com \
--to=aron@hp.com \
--cc=keir.fraser@citrix.com \
--cc=waldi@debian.org \
--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.