search for: xen_target_arch

...posix TARGET_CPPFLAGS += -isystem $(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf/include TARGET_CPPFLAGS += -isystem $(GCC_INSTALL)include -TARGET_CPPFLAGS += -isystem $(CURDIR)/lwip/src/include -TARGET_CPPFLAGS += -isystem $(CURDIR)/lwip/src/include/ipv4 +TARGET_CPPFLAGS += -isystem $(CURDIR)/lwip-$(XEN_TARGET_ARCH)/src/include +TARGET_CPPFLAGS += -isystem $(CURDIR)/lwip-$(XEN_TARGET_ARCH)/src/include/ipv4 TARGET_CPPFLAGS += -I$(CURDIR)/include TARGET_LDFLAGS += -nostdlib -L$(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf/lib @@ -164,7 +162,10 @@ lwip-$(XEN_TARGET_ARCH): lwip-$(LWIP_VER .PHONY: $(CROSS_ROOT)...

...e --- a/tools/Makefile +++ b/tools/Makefile @@ -45,6 +45,7 @@ SUBDIRS-y += remus SUBDIRS-$(CONFIG_X86) += xenpaging SUBDIRS-$(CONFIG_X86) += debugger/gdbsx SUBDIRS-$(CONFIG_X86) += debugger/kdd +SUBDIRS-$(CONFIG_TESTS) += tests # These don''t cross-compile ifeq ($(XEN_COMPILE_ARCH),$(XEN_TARGET_ARCH)) diff -r 2c6ff08e8b5b -r 7d62108a8936 tools/tests/Makefile --- /dev/null +++ b/tools/tests/Makefile @@ -0,0 +1,20 @@ +XEN_ROOT = $(CURDIR)/../.. +include $(XEN_ROOT)/tools/Rules.mk + +CFLAGS += $(CFLAGS_libxenctrl) +LDLIBS += $(LDLIBS_libxenctrl) + +SUBDIRS-y := +SUBDIRS-y += mce-test +SUBDIRS-y...

...fficiently done by making the path a parameter, calling the source file xendomains.in and then processing it to produce the official xendomains substituting the path with the provided one. LIBDIR: I guess we could do away with our patch if they accept to change their Config.mk from: ifeq ($(XEN_TARGET_ARCH),x86_64) LIBDIR = lib64 else LIBDIR = lib endif to: ifeq ($(XEN_TARGET_ARCH),x86_64) LIBDIR ?= lib64 else LIBDIR ?= lib endif Which shoudln't change anything for them and lets us pass the LIBDIR= parameter to make and remove our 20lib64.dpatch. Any other points we might...

...>Signed-off-by Zhang Xiantao <xiantao.zhang@intel.com> > >diff -r 0255f48b757f Makefile >--- a/Makefile Sun Dec 4 19:12:00 2005 >+++ b/Makefile Wed Dec 14 17:35:04 2005 >@@ -10,7 +10,7 @@ > # Export target architecture overrides to Xen and Linux sub-trees. > ifneq ($(XEN_TARGET_ARCH),) > SUBARCH := $(subst x86_32,i386,$(XEN_TARGET_ARCH)) >-export XEN_TARGET_ARCH SUBARCH >+export XEN_TARGET_ARCH SUBARCH XEN_SYSTYPE > endif > > # Default target must appear before any include lines >diff -r 0255f48b757f buildconfigs/mk.linux-2.6-xen >--- a/buildconfigs/mk....

Hello,   I can say that I have searched the entire ''world wide web'' and still haven''t found ''complete  and clear answers'' to the often asked question of: Given a Xen (release) build (say 3.2.0), which by default tries to get and build and assume Linux kernel-xen 2.6.18 from the mercurial repository, HOW TO override the build and make it work with a

This allows tools in the python directory to properly link to libxenstore.a on x86-64. --- tools/xenstore/Makefile.orig 2005-06-09 12:56:34.000000000 -0500 +++ tools/xenstore/Makefile 2005-06-09 13:48:06.000000000 -0500 @@ -20,6 +20,9 @@ BASECFLAGS+= -I. CFLAGS+=$(BASECFLAGS) +ifeq ($(XEN_TARGET_ARCH),x86_64) +CFLAGS += -fPIC +endif LDFLAGS=$(PROFILE) -L$(XEN_LIBXC) TESTDIR=`pwd`/testsuite/tmp TESTFLAGS=-DTESTING -- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157) _______________________________________________ Xen-devel mailing list Xen-devel@list...

I''ve removed all the LIBLEAF bits in this version, but kept passing the libfsimage plugin location via compiler command line. If there''s a better way to do this, I''m certainly open to it. But looking at it further today I think this isn''t too horrible. Matt

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

...quot;yes" diff -r 2d6fd3bba3c2 -r 2d289d7ab961 tools/ioemu/target-i386-dm/Makefile --- a/tools/ioemu/target-i386-dm/Makefile Thu Jun 30 05:24:52 2005 +++ b/tools/ioemu/target-i386-dm/Makefile Thu Jun 30 05:26:09 2005 @@ -305,9 +305,6 @@ ifdef CONFIG_STATIC VL_LDFLAGS+=-static endif -ifeq ($(XEN_TARGET_ARCH),x86_32) -VL_LDFLAGS+=-Wl,-T,$(SRC_PATH)/$(XEN_TARGET_ARCH).ld -endif ifndef CONFIG_DARWIN ifndef CONFIG_WIN32 VL_LIBS=-lutil _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...64/Makefile > > CFLAGS += -Werror > CFLAGS += -fno-strict-aliasing I''m not sure this is the best way. We''ll need to do the same thing for xc_ppc_linux_build.c, but it seems a little silly to unconditionally include powerpc/Makefile as well... perhaps -include $(XEN_TARGET_ARCH)/Makefile would suffice? -- Hollis Blanchard IBM Linux Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...uild fix for Solaris sed. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/xen/Rules.mk b/xen/Rules.mk --- a/xen/Rules.mk +++ b/xen/Rules.mk @@ -24,9 +24,11 @@ override COMPILE_SUBARCH := $(XEN_COMPIL override COMPILE_SUBARCH := $(XEN_COMPILE_ARCH) override TARGET_SUBARCH := $(XEN_TARGET_ARCH) override COMPILE_ARCH := $(shell echo $(XEN_COMPILE_ARCH) | \ - sed -e ''s/\(x86\|powerpc\).*/\1/'') + sed -e ''s/x86.*/x86/'' \ + -e ''s/powerpc.*/powerpc/'...

...gned-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 4024164e7572 stubdom/Makefile --- a/stubdom/Makefile Tue Jul 08 16:11:49 2008 +0100 +++ b/stubdom/Makefile Tue Jul 08 17:12:38 2008 +0100 @@ -190,7 +190,7 @@ [ -f ioemu/config-host.mak ] || \ ( cd ioemu ; \ XEN_TARGET_ARCH=$(XEN_TARGET_ARCH) CFLAGS="$(TARGET_CFLAGS)" sh configure --prefix=/usr --enable-stubdom $(IOEMU_OPTIONS)) - CPPFLAGS="$(TARGET_CPPFLAGS)" $(MAKE) -C ioemu LWIPDIR=$(CURDIR)/lwip-cvs + CPPFLAGS="$(TARGET_CPPFLAGS)" $(MAKE) -C ioemu LWIPDIR=$(CURDIR)/lwip-cvs TOOLS=...

...avante@jhuapl.edu> --- stubdom/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/stubdom/Makefile b/stubdom/Makefile index 7519683..3006ad6 100644 --- a/stubdom/Makefile +++ b/stubdom/Makefile @@ -173,7 +173,7 @@ cross-gmp: $(GMP_STAMPFILE) $(GMP_STAMPFILE): gmp-$(XEN_TARGET_ARCH) ( cd $< && \ $(MAKE) && \ - $(MAKE) install ) + $(MAKE) DESTDIR= install ) ############# # cross-polarssl -- 1.7.10.4

...e I need to get up to speed here before even looking at development. I do have some issues that need clarification: 1) How can I specify the target architecture for the build? (I''m working with two different systems , one Ubuntu 9.04 and the other Fedora Core 10. My Ubuntu machine needs XEN_TARGET_ARCH=x86_64, and my FC10 box needs XEN_TARGET_ARCH=x86_32. I would like to specify each build. 2) All attempts to build default to building linux-2.26.18. Why? I KNOW kernel.org is now up to 2.26.30. Is it even possible to specify specific kernel versions for domain0 and for domainU? 3) All attemp...

Hi all, this is the tenth version of the patch series to introduce upstream qemu and seabios in the xen-unstable build system. Changes to v9: - rename QEMU_UPSTREAM_TAG to QEMU_UPSTREAM_REVISION: we are going to use it with a branch name by default; - set QEMU_UPSTREAM_REVISION to "master" by default; - set SEABIOS_UPSTREAM_URL to git://xenbits.xen.org/seabios.git by default; - add

...is due to version difference. I am using Xen 4.3.3 version. My understanding is that due to this version difference I am not able to compile xen tools. I have produced the output below. Also I have attached my mkheader.py file for reference. ... make dist-tools CROSS_COMPILE=arm-linux-gnueabihf- XEN_TARGET_ARCH=arm32 make -C tools install make[1]: Entering directory `/Virt/xen1/xen-unstable.git-xen-arm-4.3-3-e2cb352/tools'' make[2]: Entering directory `/Virt/xen1/xen-unstable.git-xen-arm-4.3-3-e2cb352/tools'' make -C include install make[3]: Entering directory `/Virt/xen1/xen-unstable.git-...

...E) -C examples - $(MAKE) -C xentrace - $(MAKE) -C python - $(MAKE) -C xfrd - $(MAKE) -C xcs - $(MAKE) -C ioemu +SUBDIRS := +SUBDIRS += check +SUBDIRS += libxutil +SUBDIRS += libxc +SUBDIRS += misc +SUBDIRS += examples +SUBDIRS += xentrace +SUBDIRS += python +SUBDIRS += xfrd +SUBDIRS += xcs +ifeq ($(XEN_TARGET_ARCH),x86_32) +SUBDIRS += ioemu +endif -install: - $(MAKE) -C check - $(MAKE) -C libxutil install - $(MAKE) -C libxc install - $(MAKE) -C misc install - $(MAKE) -C examples install - $(MAKE) -C xentrace install - $(MAKE) -C python install - $(MAKE) -C xfrd install - $(MAKE) -C sv install - $(MAKE) -C...

Initially out there as #965245. I strongly prefer to build ARM64 packages on non-ARM systems. Something about my main build machine having twice the cores and twice the clock speed. As such after many builds I've managed to generate a set of patches which appear to mostly function to get functioning cross-builds of Xen. These are NOT a 100% solution. Some packaging hacks were needed. In

Goodmorning, I''m currently playing with XEN/arm on my Allwinner A20 (cubieboard2) I would like to get the XENFB driver working on domU. But currently in xen/arm there''s no support for VFB, atleast qemu is not supported. But this video http://www.youtube.com/watch?v=po1IeElg8tg and this one http://www.youtube.com/watch?v=Km6gBnIqaWo is showing a working framebuffer. So there are

...ce tree of my own, I would like to know the cause and possible fix for this. My guess: It seems like the target linux bulid directory build-linux-2.6.18-xen0_x86_32,  the sub-directory /arch/i386/boot/ is  not getting created for some reason.  Should the ''make dist'' also specify XEN_TARGET_ARCH=x86_32 ? Note: I am able to successfully build the linux kernel from the original kernel source directory without any such errors.  Only ''make dist'' fails. -regards, Jithendra B _______________________________________________ Xen-users mailing list Xen-users@lists.xensource....