bitkeeper revision 1.1159.234.1 (41f9203a3hESfmWBG29VVoqa-chOrA)

Build system cleanups.

Signed-off-by: c@pin.lu

Makefile

@@ -11,7 +11,7 @@ INSTALL_DIR	:= $(INSTALL) -d -m0755
 INSTALL_DATA	:= $(INSTALL) -m0644
 INSTALL_PROG	:= $(INSTALL) -m0755
 
-KERNELS ?= *2.6*
+KERNELS ?= linux-2.6-xen0 linux-2.6-xenU
 # linux-2.4-xen0 linux-2.4-xenU netbsd-2.0-xenU
 # You may use wildcards in the above e.g. KERNELS=*2.4*
 
@@ -30,20 +30,12 @@ endif
 include buildconfigs/Rules.mk
 
 .PHONY:	all dist install xen tools kernels docs world clean mkpatches mrproper
-.PHONY:	kbuild kdelete kclean install-tools install-xen install-docs
-.PHONY: install-kernels
+.PHONY:	kbuild kdelete kclean
 
 all: dist
 
-# install everything into the standard system directories
-# NB: install explicitly does not check that everything is up to date!
-install: DESTDIR=
-install: xen checked-tools kernels docs
-
-# Only check for install req'mts on 'make install', not on 'make dist'.
-checked-tools:
-	$(MAKE) -C tools/check install
-	$(MAKE) -C tools install
+# build and install everything into the standard system directories
+install: install-xen install-tools install-kernels install-docs
 
 # build and install everything into local dist directory
 dist: xen tools kernels docs
@@ -118,9 +110,17 @@ install-iptables:
 	tar -jxf iptables-1.2.11.tar.bz2
 	$(MAKE) -C iptables-1.2.11 PREFIX= KERNEL_DIR=../linux-$(LINUX_VER)-xen0 install
 
+install-%: DESTDIR=
+install-%: %
+	@: # do nothing
+
 help:
 	@echo 'Installation targets:'
 	@echo '  install          - build and install everything'
+	@echo '  install-xen      - build and install the Xen hypervisor'
+	@echo '  install-tools    - build and install the control tools'
+	@echo '  install-kernels  - build and install guest kernels'
+	@echo '  install-docs     - build and install documentation'
 	@echo ''
 	@echo 'Building targets:'
 	@echo '  dist             - build and install everything into local dist directory'
@@ -178,3 +178,4 @@ linux26:
 
 netbsd20:
 	$(MAKE) netbsd-2.0-xenU-build
+

linux-2.6.10-xen-sparse/arch/xen/Kconfig

@@ -26,7 +26,7 @@ menu "XEN"
 config XEN_PRIVILEGED_GUEST
 	bool "Privileged Guest (domain 0)"
 	default n
-        select XEN_PHYSDEV_ACCESS
+	select XEN_PHYSDEV_ACCESS
 	help
 	  Support for privileged operation (domain 0)
 
@@ -35,91 +35,91 @@ config XEN_PHYSDEV_ACCESS
 	default XEN_PRIVILEGED_GUEST
 	help
 	  Assume access is available to physical hardware devices
-          (e.g., hard drives, network cards). This allows you to configure
-          such devices and also includes some low-level support that is
-          otherwise not compiled into the kernel.
+	  (e.g., hard drives, network cards). This allows you to configure
+	  such devices and also includes some low-level support that is
+	  otherwise not compiled into the kernel.
 
 config XEN_BLKDEV_BACKEND
-        bool "Block-device backend driver"
-      depends on XEN_PHYSDEV_ACCESS
-        default y
-        help
-          The block-device backend driver allows the kernel to export its
-          block devices to other guests via a high-performance shared-memory
-          interface.
+	bool "Block-device backend driver"
+	depends on XEN_PHYSDEV_ACCESS
+	default y
+	help
+	  The block-device backend driver allows the kernel to export its
+	  block devices to other guests via a high-performance shared-memory
+	  interface.
 
 config XEN_NETDEV_BACKEND
-        bool "Network-device backend driver"
-      depends on XEN_PHYSDEV_ACCESS
-        default y
-        help
-          The network-device backend driver allows the kernel to export its
-          network devices to other guests via a high-performance shared-memory
-          interface.
+	bool "Network-device backend driver"
+	depends on XEN_PHYSDEV_ACCESS
+	default y
+	help
+	  The network-device backend driver allows the kernel to export its
+	  network devices to other guests via a high-performance shared-memory
+	  interface.
 
 config XEN_BLKDEV_FRONTEND
-        bool "Block-device frontend driver"
-        default y
-        help
-          The block-device frontend driver allows the kernel to access block
-          devices mounted within another guest OS. Unless you are building a
-          dedicated device-driver domain, or your master control domain
-          (domain 0), then you almost certainly want to say Y here.
+	bool "Block-device frontend driver"
+	default y
+	help
+	  The block-device frontend driver allows the kernel to access block
+	  devices mounted within another guest OS. Unless you are building a
+	  dedicated device-driver domain, or your master control domain
+	  (domain 0), then you almost certainly want to say Y here.
 
 config XEN_NETDEV_FRONTEND
-        bool "Network-device frontend driver"
-        default y
-        help
-          The network-device frontend driver allows the kernel to access
-          network interfaces within another guest OS. Unless you are building a
-          dedicated device-driver domain, or your master control domain
-          (domain 0), then you almost certainly want to say Y here.
+	bool "Network-device frontend driver"
+	default y
+	help
+	  The network-device frontend driver allows the kernel to access
+	  network interfaces within another guest OS. Unless you are building a
+	  dedicated device-driver domain, or your master control domain
+	  (domain 0), then you almost certainly want to say Y here.
 
 config XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER
-        bool "Pipelined transmitter (DANGEROUS)"
+	bool "Pipelined transmitter (DANGEROUS)"
 	depends on XEN_NETDEV_FRONTEND
-        default n
-        help
-          The driver will assume that the backend is pipelining packets for
-          transmission: whenever packets are pending in the remote backend,
-          the driver will not send asynchronous notifications when it queues
-          additional packets for transmission.
-          If the backend is a dumb domain, such as a transparent Ethernet
-          bridge with no local IP interface, it is safe to say Y here to get
-          slightly lower network overhead.
-          If the backend has a local IP interface; or may be doing smart things
-          like reassembling packets to perform firewall filtering; or if you
-          are unsure; or if you experience network hangs when this option is
-          enabled; then you must say N here.
+	default n
+	help
+	  The driver will assume that the backend is pipelining packets for
+	  transmission: whenever packets are pending in the remote backend,
+	  the driver will not send asynchronous notifications when it queues
+	  additional packets for transmission.
+	  If the backend is a dumb domain, such as a transparent Ethernet
+	  bridge with no local IP interface, it is safe to say Y here to get
+	  slightly lower network overhead.
+	  If the backend has a local IP interface; or may be doing smart things
+	  like reassembling packets to perform firewall filtering; or if you
+	  are unsure; or if you experience network hangs when this option is
+	  enabled; then you must say N here.
 
 config XEN_WRITABLE_PAGETABLES
 	bool
 	default y
 
 config XEN_SCRUB_PAGES
-        bool "Scrub memory before freeing it to Xen"
-        default y
-        help
-          Erase memory contents before freeing it back to Xen's global
-          pool. This ensures that any secrets contained within that
-          memory (e.g., private keys) cannot be found by other guests that
-          may be running on the machine. Most people will want to say Y here.
-          If security is not a concern then you may increase performance by
-          saying N.
+	bool "Scrub memory before freeing it to Xen"
+	default y
+	help
+	  Erase memory contents before freeing it back to Xen's global
+	  pool. This ensures that any secrets contained within that
+	  memory (e.g., private keys) cannot be found by other guests that
+	  may be running on the machine. Most people will want to say Y here.
+	  If security is not a concern then you may increase performance by
+	  saying N.
 
 choice
-        prompt "Processor Type"
-        default X86
+	prompt "Processor Type"
+	default X86
 
 config X86
-        bool "X86"
-        help
-          Choose this option if your computer is a X86 architecture.
+	bool "X86"
+	help
+	  Choose this option if your computer is a X86 architecture.
 
 config X86_64
-        bool "X86_64"
-        help
-          Choose this option if your computer is a X86 architecture.
+	bool "X86_64"
+	help
+	  Choose this option if your computer is a X86 architecture.
 
 endchoice
 

tools/examples/Makefile

@@ -25,20 +25,23 @@ all:
 install: all install-initd install-configs install-scripts
 
 install-initd:
-	$(INSTALL_DIR) $(DESTDIR)/etc/init.d
+	[ -d $(DESTDIR)/etc/init.d ] || $(INSTALL_DIR) $(DESTDIR)/etc/init.d
 	$(INSTALL_PROG) $(XEND_INITD) $(DESTDIR)/etc/init.d
 	$(INSTALL_PROG) $(XENDOMAINS_INITD) $(DESTDIR)/etc/init.d
 
 install-configs:
-	$(INSTALL_DIR) $(DESTDIR)$(XEN_CONFIG_DIR)
-	$(INSTALL_DIR) $(DESTDIR)$(XEN_CONFIG_DIR)/auto
+	[ -d $(DESTDIR)$(XEN_CONFIG_DIR) ] || \
+		$(INSTALL_DIR) $(DESTDIR)$(XEN_CONFIG_DIR)
+	[ -d $(DESTDIR)$(XEN_CONFIG_DIR)/auto ] || \
+		$(INSTALL_DIR) $(DESTDIR)$(XEN_CONFIG_DIR)/auto
 	for i in $(XEN_CONFIGS); \
 	    do [ -a $(DESTDIR)$(XEN_CONFIG_DIR)/$$i ] || \
 	    $(INSTALL_DATA) $$i $(DESTDIR)$(XEN_CONFIG_DIR); \
 	done
 
 install-scripts:
-	$(INSTALL_DIR) $(DESTDIR)$(XEN_SCRIPT_DIR)
+	[ -d $(DESTDIR)$(XEN_SCRIPT_DIR) ] || \
+		$(INSTALL_DIR) $(DESTDIR)$(XEN_SCRIPT_DIR)
 	for i in $(XEN_SCRIPTS); \
 	    do [ -a $(DESTDIR)$(XEN_SCRIPT_DIR)/$$i ] || \
 	    $(INSTALL_PROG) $$i $(DESTDIR)$(XEN_SCRIPT_DIR); \

tools/libxc/Makefile

@@ -66,8 +66,8 @@ mk-symlinks:
 	  ln -sf ../../$(LINUX_ROOT)/include/asm-xen/linux-public/*.h . )
 
 install: all
-	$(INSTALL_DIR) $(DESTDIR)/usr/lib
-	$(INSTALL_DIR) $(DESTDIR)/usr/include
+	[ -d $(DESTDIR)/usr/lib ] || $(INSTALL_DIR) $(DESTDIR)/usr/lib
+	[ -d $(DESTDIR)/usr/include ] || $(INSTALL_DIR) $(DESTDIR)/usr/include
 	$(INSTALL_PROG) $(LIB) $(DESTDIR)/usr/lib
 	ln -sf libxc.so.$(MAJOR).$(MINOR) $(DESTDIR)/usr/lib/libxc.so.$(MAJOR)
 	ln -sf libxc.so.$(MAJOR) $(DESTDIR)/usr/lib/libxc.so

tools/libxutil/Makefile

@@ -63,7 +63,7 @@ check-for-zlib:
 	fi
 
 install: all
-	$(INSTALL_DIR) -p $(DESTDIR)/usr/lib
+	[ -d $(DESTDIR)/usr/lib ] || $(INSTALL_DIR) -p $(DESTDIR)/usr/lib
 	$(INSTALL_PROG) $(LIB) $(DESTDIR)/usr/lib
 	ln -sf $(LIB_NAME).so.$(MAJOR).$(MINOR) $(DESTDIR)/usr/lib/$(LIB_NAME).so.$(MAJOR)
 	ln -sf $(LIB_NAME).so.$(MAJOR) $(DESTDIR)/usr/lib/$(LIB_NAME).so

tools/misc/Makefile

@@ -23,8 +23,8 @@ all: $(TARGETS)
 	$(MAKE) -C miniterm
 
 install: all
-	$(INSTALL_DIR) $(DESTDIR)/usr/bin
-	$(INSTALL_DIR) $(DESTDIR)/usr/sbin
+	[ -d $(DESTDIR)/usr/bin ] || $(INSTALL_DIR) $(DESTDIR)/usr/bin
+	[ -d $(DESTDIR)/usr/sbin ] || $(INSTALL_DIR) $(DESTDIR)/usr/sbin
 	$(INSTALL_PROG) $(INSTALL_BIN) $(DESTDIR)/usr/bin
 	$(INSTALL_PROG) $(INSTALL_SBIN) $(DESTDIR)/usr/sbin
 #       No sense in installing miniterm on the Xen box.

tools/misc/miniterm/Makefile

@@ -9,7 +9,7 @@ TARGET = miniterm
 all: $(TARGET)
 
 install: all
-	$(INSTALL_DIR) $(DESTDIR)/usr/bin
+	[ -d $(DESTDIR)/usr/bin ] || $(INSTALL_DIR) $(DESTDIR)/usr/bin
 	$(INSTALL_PROG) $(TARGET) $(DESTDIR)/usr/bin
 
 clean:

tools/sv/Makefile

@@ -17,15 +17,17 @@ IMAGES	+= next.png previous.png finish.png
 
 install:
 	# copy XenSV Main.rpy file
-	@$(INSTALL_DIR) $(DESTDIR)$(sv_insdir)
+	@[ -d $(DESTDIR)$(sv_insdir) ] || $(INSTALL_DIR) $(DESTDIR)$(sv_insdir)
 	@$(INSTALL_DATA) Main.rpy $(DESTDIR)$(sv_insdir)
 
 	# copy XenSV images
-	@$(INSTALL_DIR) $(DESTDIR)$(sv_insdir)/images
+	@[ -d $(DESTDIR)$(sv_insdir)/images ] || \
+		$(INSTALL_DIR) $(DESTDIR)$(sv_insdir)/images
 	@(cd images && $(INSTALL_DATA) $(IMAGES) $(DESTDIR)$(sv_insdir)/images)
 
 	# copy XenSV stylesheet
-	@$(INSTALL_DIR) $(DESTDIR)$(sv_insdir)/inc
+	@[ -d $(DESTDIR)$(sv_insdir)/inc ] || \
+		$(INSTALL_DIR) $(DESTDIR)$(sv_insdir)/inc
 	@$(INSTALL_DATA) inc/style.css inc/script.js $(DESTDIR)$(sv_insdir)/inc
 
 clean:

tools/xentrace/Makefile

@@ -24,9 +24,11 @@ MAN8     = $(wildcard *.8)
 all: $(BIN)
 
 install: all
-	$(INSTALL_DIR) $(DESTDIR)/usr/bin
-	$(INSTALL_DIR) $(DESTDIR)/usr/man/man1
-	$(INSTALL_DIR) $(DESTDIR)/usr/man/man8
+	[ -d $(DESTDIR)/usr/bin ] || $(INSTALL_DIR) $(DESTDIR)/usr/bin
+	[ -d $(DESTDIR)/usr/man/man1 ] || \
+		$(INSTALL_DIR) $(DESTDIR)/usr/man/man1
+	[ -d $(DESTDIR)/usr/man/man8 ] || \
+		$(INSTALL_DIR) $(DESTDIR)/usr/man/man8
 	$(INSTALL_PROG) $(BIN) $(SCRIPTS) $(DESTDIR)/usr/bin
 	$(INSTALL_DATA) $(MAN1) $(DESTDIR)/usr/man/man1
 	$(INSTALL_DATA) $(MAN8) $(DESTDIR)/usr/man/man8

tools/xfrd/Makefile

@@ -70,7 +70,8 @@ xfrd: $(XFRD_PROG_OBJ)
 
 .PHONY: install
 install: xfrd
-	$(INSTALL_DIR) $(DESTDIR)$(XFRD_INSTALL_DIR)
+	[ -d $(DESTDIR)$(XFRD_INSTALL_DIR) ] || \
+		$(INSTALL_DIR) $(DESTDIR)$(XFRD_INSTALL_DIR)
 	$(INSTALL_PROG) xfrd $(DESTDIR)$(XFRD_INSTALL_DIR)
 
 .PHONY: libutil

xen/Makefile

@@ -21,10 +21,11 @@ debug:
 	objdump -D -S $(TARGET)-syms > $(TARGET).s
 
 install: $(TARGET).gz
-	$(INSTALL_DIR) $(DESTDIR)/boot
+	[ -d $(DESTDIR)/boot ] || $(INSTALL_DIR) $(DESTDIR)/boot
 	$(INSTALL_DATA) $(TARGET).gz $(DESTDIR)/boot
 	$(INSTALL_DATA) $(TARGET)-syms $(DESTDIR)/boot
-	$(INSTALL_DIR) $(DESTDIR)/usr/include/xen/io
+	[ -d $(DESTDIR)/usr/include/xen/io ] || \
+		$(INSTALL_DIR) $(DESTDIR)/usr/include/xen/io
 	$(INSTALL_DATA) include/public/*.h $(DESTDIR)/usr/include/xen
 	$(INSTALL_DATA) include/public/io/*.h $(DESTDIR)/usr/include/xen/io
 	$(INSTALL_DATA) include/public/COPYING $(DESTDIR)/usr/include/xen