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:
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|