Re: [Xen-ia64-devel] Re: [PATCH 2 of 2] cross-build fixes in ioemu-remote

Re: [Xen-ia64-devel] Re: [PATCH 2 of 2] cross-build fixes in ioemu-remote

[Samuel Thibault]

Ian Jackson, le Thu 31 Jul 2008 16:16:37 +0100, a écrit :
> Aron Griffis writes ("[Xen-devel] [PATCH 2 of 2] cross-build fixes in ioemu-remote"):
> > - Don't call install -s; it uses the host strip program which
> >   doesn't understand cross-built binaries.  This same change was
> >   in the legacy ioemu dir.
> 
> I think this should be fixed by the build environment, or possibly
> $(INSTALL), being arranged to not have this bug.  If $(INSTALL) -s
> doesn't work then this should be fixed.  Options include putting a
> symlink to /bin/true on the path somewhere under the name `strip', or
> overriding INSTALL somehow to a more clever program.

I have the same issue when cross-compiling some other projects.  I
wonder how install would be able to know which strip command it should
use.

Samuel

Re: [Xen-ia64-devel] Re: [PATCH 2 of 2] cross-build fixes in ioemu-remote

[Ian Jackson]

Samuel Thibault writes ("Re: [Xen-ia64-devel] Re: [Xen-devel] [PATCH 2 of 2] cross-build fixes in ioemu-remote"):
> I have the same issue when cross-compiling some other projects.  I
> wonder how install would be able to know which strip command it should
> use.

Perhaps it should call STRIP if it exists, or perhaps the
cross-building setup should provide a `strip' which will always DTRT
(perhaps by examining the file to decide which real strip to invoke).

Ian.

Re: [Xen-ia64-devel] Re: [PATCH 2 of 2] cross-build fixes in ioemu-remote

[Aron Griffis]

Ian Jackson wrote:  [Thu Jul 31 2008, 12:48:15PM EDT]
> Samuel Thibault writes ("Re: [Xen-ia64-devel] Re: [Xen-devel] [PATCH 2 of 2] cross-build fixes in ioemu-remote"):
> > I have the same issue when cross-compiling some other projects.  I
> > wonder how install would be able to know which strip command it should
> > use.
> 
> Perhaps it should call STRIP if it exists, or perhaps the
> cross-building setup should provide a `strip' which will always DTRT
> (perhaps by examining the file to decide which real strip to invoke).

I don't think it's necessary to provide one that will DTRT.  The
compiler and linker don't need that abstraction, and "install" is
only called for stuff that will be installed on the target
system.

qemu seems to have the ability to set the install command using
configure.  Seems something like the following should work,
except that (1) i386-dm/hookstarget.mak uses $(INSTALL_PROG)
which seems to be defined outside of the ioemu tree, and (2) I'm
having enough trouble cross-building qemu that it's hard to test.

Thanks,
Aron

diff -r 40daf3257cad tools/Makefile
--- a/tools/Makefile	Thu Jul 31 10:51:30 2008 -0400
+++ b/tools/Makefile	Thu Jul 31 15:18:24 2008 -0400
@@ -36,9 +36,11 @@ SUBDIRS-$(PYTHON_TOOLS) += pygrub
 SUBDIRS-$(PYTHON_TOOLS) += pygrub
 endif
 
-# For the sake of linking, set the sys-root
+# For the sake of linking, set the path to "strip" and the sys-root
 ifneq ($(CROSS_COMPILE),)
+CROSS_BIN_PATH ?= /usr/$(CROSS_COMPILE:-=)/bin
 CROSS_SYS_ROOT ?= /usr/$(CROSS_COMPILE:-=)/sys-root
+# export sys-root to environment for check/funcs.sh
 export CROSS_SYS_ROOT
 endif
 
@@ -57,7 +59,8 @@ ifneq ($(XEN_COMPILE_ARCH),$(XEN_TARGET_
 ifneq ($(XEN_COMPILE_ARCH),$(XEN_TARGET_ARCH))
 IOEMU_CONFIGURE_CROSS ?= --cpu=$(XEN_TARGET_ARCH) \
 			 --cross-prefix=$(CROSS_COMPILE) \
-			 --interp-prefix=$(CROSS_SYS_ROOT)
+			 --interp-prefix=$(CROSS_SYS_ROOT) \
+			 --install='env PATH="$(CROSS_BIN_PATH):$$$$PATH" install'
 endif
 
 ioemu/config-host.mak:

Re: [Xen-ia64-devel] Re: [PATCH 2 of 2] cross-build fixes in ioemu-remote

[Ian Jackson]

Aron Griffis writes ("Re: [Xen-ia64-devel] Re: [Xen-devel] [PATCH 2 of 2] cross-build fixes in ioemu-remote"):
> -			 --interp-prefix=$(CROSS_SYS_ROOT)
> +			 --interp-prefix=$(CROSS_SYS_ROOT) \
> +			 --install='env PATH="$(CROSS_BIN_PATH):$$$$PATH" install'

This is a bit bizarre (not to mention the fact that the number of $'s
will depend on undocumented properties of the way qemu's configure
inteprets that option).

Why not just set PATH directly and export it ?

But in general I think this is a reasonable approach.

Ian.

Re: [Xen-ia64-devel] Re: [PATCH 2 of 2] cross-build fixes in ioemu-remote

[Aron Griffis]

Any responses to my last email and patch in this thread?

It would be nice to get cross-install (or something like it) in
the tree, along with fixing the build on ia64.

The build problem is that translate-all.c doesn't build on ia64,
because there's no support for instruction translation on ia64.
But it shouldn't need to build translate-all.c at all for ioemu.
It didn't on the legacy ioemu, and it's only working right now on
ia32 and x86_64 because those arches can build translate-all.c,
however unnecessary it is.

I took a quick look but I'm not quickly seeing how to change the
build to omit translate-all.c.  It would be great if somebody
more familiar with ioemu could take a glance.

Thanks,
Aron

Re: [Xen-ia64-devel] Re: [PATCH 2 of 2] cross-build fixes in ioemu-remote

[Keir Fraser]

Unfortunately Ian is away this week, so these changes aren't likely to get
picked up or commented on until Monday.

 -- Keir

On 4/8/08 23:31, "Aron Griffis" <aron@hp.com> wrote:

> Any responses to my last email and patch in this thread?
> 
> It would be nice to get cross-install (or something like it) in
> the tree, along with fixing the build on ia64.
> 
> The build problem is that translate-all.c doesn't build on ia64,
> because there's no support for instruction translation on ia64.
> But it shouldn't need to build translate-all.c at all for ioemu.
> It didn't on the legacy ioemu, and it's only working right now on
> ia32 and x86_64 because those arches can build translate-all.c,
> however unnecessary it is.
> 
> I took a quick look but I'm not quickly seeing how to change the
> build to omit translate-all.c.  It would be great if somebody
> more familiar with ioemu could take a glance.
> 
> Thanks,
> Aron
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: [Xen-ia64-devel] Re: [PATCH 2 of 2] cross-build fixes in ioemu-remote

[Aron Griffis]

(cc'd to lists)

Isaku Yamahata wrote:  [Tue Aug 05 2008, 10:02:49PM EDT]
> On Tue, Aug 05, 2008 at 10:50:32AM -0400, Aron Griffis wrote:
> > Keir Fraser wrote:  [Tue Aug 05 2008, 08:47:40AM EDT]
> > > I suggest we turn off ioemu-remote for ia64, at least by
> > > default. Even if we get it building next week, it still needs
> > > testing. And we plan to release next Friday (15th August).
> > 
> > I'd defer to Isaku (cc'd) on that question.  I'm not quite
> > connected enough to Xen/ia64 development to know the best answer.
> 
> Given that no one hasn't seemed to test ioemu-remote,
> I think default off is a reasonable choice.

Okay, here's the patch.

Thanks,
Aron

# HG changeset patch
# User Aron Griffis <aron@hp.com>
# Date 1218028500 14400
# Node ID 7071b1990a15ee14e2ccb9d199764237962c7e57
# Parent  c329dcc9df04ade9c183bfb696bca37296d80a1f
Use legacy ioemu on ia64 for Xen 4.0

Signed-off-by: Aron Griffis <aron@hp.com>

diff -r c329dcc9df04 -r 7071b1990a15 Config.mk
--- a/Config.mk	Wed Aug 06 11:38:42 2008 +0100
+++ b/Config.mk	Wed Aug 06 09:15:00 2008 -0400
@@ -86,7 +86,11 @@
 # Mercurial in-tree version, or a local directory, or a git URL.
 # CONFIG_QEMU   ?= ioemu
 # CONFIG_QEMU   ?= ../qemu-xen.git
+ifeq ($(XEN_TARGET_ARCH),ia64)
+CONFIG_QEMU   ?= ioemu
+else
 CONFIG_QEMU   ?= $(QEMU_REMOTE)
+endif
 
 # Optional components
 XENSTAT_XENTOP     ?= y