[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-ia64-devel] RE: Refering Xen files within XenLinux
Dan, You do want to pull in this patch into XenLinux for build. This patch was missed previousely and causing XenLinux build fail. -Fred Tian, Kevin wrote: > Another symbolic link change for asm-xsi-offsets.h, to allow user > directly "make" after pull, without any extra manual copy: > > diff -r 3dcc6214c790 arch/ia64/Makefile > --- a/arch/ia64/Makefile Tue Aug 9 17:07:51 2005 > +++ b/arch/ia64/Makefile Wed Aug 10 16:00:48 2005 > @@ -110,6 +110,9 @@ > [ -e include/asm-xen/xen-public ] \ > || ln -s $(XEN_PATH)/xen/include/public \ > include/asm-xen/xen-public > + [ -e include/asm-ia64/xen/asm-xsi-offsets.h ] \ > + || ln -s $(XEN_PATH)/xen/include/asm-ia64/asm-xsi-offsets.h \ > + include/asm-ia64/xen/asm-xsi-offsets.h > > boot: lib/lib.a vmlinux > $(Q)$(MAKE) $(build)=$(boot) $@ > > Thanks, > Kevin > >> -----Original Message----- >> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx >> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of >> Tian, Kevin Sent: Tuesday, August 09, 2005 6:25 PM >> To: Magenheimer, Dan (HP Labs Fort Collins); Yang, Fred >> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx >> Subject: RE: [Xen-ia64-devel] RE: Refering Xen files within XenLinux >> >> Attached is the xenolinux patch to convert xen-public symlinked to >> xen source. To reducing size of patch, I skipped bunch of lines of >> removed files in xen-public . So after applying this patch, you have >> to remove the whole xen-public directory locally before pushing to >> hg tree. ;-) >> >> There's also related change for arch-ia64.h for naming issue. So a >> necessary pull is also required for Xen: >> >> changeset: 5978:c56a9805216a23c014d91d213a7a0962566b76fc >> tag: tip >> user: fred@xxxxxxxxxxxxxxxxxxxxx >> date: Tue Aug 9 03:32:52 2005 >> summary: Accommodate ia64-xenolinux change where xen-public is >> symlinked to >> >> Signed-off-by Kevin Tian <Kevin.tian@xxxxxxxxx> >> Signed-off-by Arun Sharma <arun.sharma@xxxxxxxxx> >> >> diff -r e02a6763767b arch/ia64/Makefile >> --- a/arch/ia64/Makefile Thu Aug 4 22:02:00 2005 >> +++ b/arch/ia64/Makefile Tue Aug 9 10:51:40 2005 >> @@ -99,11 +99,17 @@ >> >> arch/ia64/kernel/asm-offsets.s: include/asm-ia64/.offsets.h.stamp >> >> +XEN_PATH := $(srctree)/../xen-ia64-unstable.hg/ >> include/asm-ia64/.offsets.h.stamp: >> mkdir -p include/asm-ia64 >> [ -s include/asm-ia64/offsets.h ] \ >> || echo "#define IA64_TASK_SIZE 0" > include/asm-ia64/offsets.h >> touch $@ + [ -e include/asm-xen/asm ] \ >> + || ln -s asm-ia64 include/asm-xen/asm >> + [ -e include/asm-xen/xen-public ] \ >> + || ln -s $(XEN_PATH)/xen/include/public \ >> + include/asm-xen/xen-public >> >> boot: lib/lib.a vmlinux >> $(Q)$(MAKE) $(build)=$(boot) $@ >> >>> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx >>> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of >>> Magenheimer, Dan (HP Labs Fort Collins) >>> Sent: Friday, August 05, 2005 7:31 AM >>> >>>> How about use XEN=/path/to/xen within xenlinux Makefile and some >>>> glue to symlink files. We can come out patch for xenlinux build >>>> early next week if it is agreed approach. >>> >>> This sounds reasonable, though it may create some confusion >>> if someone has multiple xen development trees and only one xenlinux >>> treee. >>> >> >> _______________________________________________ >> Xen-ia64-devel mailing list >> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx >> http://lists.xensource.com/xen-ia64-devel _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ia64-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |