diff options
| author | kaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk> | 2006-04-10 16:31:53 +0100 |
|---|---|---|
| committer | kaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk> | 2006-04-10 16:31:53 +0100 |
| commit | 4886bb64c1ab8f5c0884a6ebc5c9c7591149684b (patch) | |
| tree | d70113b431f86cd5e6c1b73fa84830e3df6ed23d /Config.mk | |
| parent | 2a9a3c31160736e916dae53db6483fc6324fec0a (diff) | |
| download | xen-4886bb64c1ab8f5c0884a6ebc5c9c7591149684b.tar.gz xen-4886bb64c1ab8f5c0884a6ebc5c9c7591149684b.tar.bz2 xen-4886bb64c1ab8f5c0884a6ebc5c9c7591149684b.zip | |
build: Make sure that DESTDIR is set
In the case where XEN_PYTHON_NATIVE_INSTALL is in effect,
if DESTDIR is not set then the install will go into a relative
directory rather than under the default prefix (usually /usr).
An alternate solution would be to update the fragments
that do the python install to use $(DESTDIR)/ instead of
$(DESTDIR). This is not an incredible burden as there
are only two such fragments in the tree. However, it
seems prone to error as new makefiles are created
in the future.
Signed-Off-By: Horms <horms@verge.net.au>
Diffstat (limited to 'Config.mk')
| -rw-r--r-- | Config.mk | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -24,6 +24,7 @@ OBJCOPY = $(CROSS_COMPILE)objcopy OBJDUMP = $(CROSS_COMPILE)objdump DISTDIR ?= $(XEN_ROOT)/dist +DESTDIR ?= / INSTALL = install INSTALL_DIR = $(INSTALL) -d -m0755 |