pkgsrc/sysutils/xentools413/patches/patch-tools_examples_Makefile

$NetBSD: patch-tools_examples_Makefile,v 1.1 2020/05/26 11:12:11 bouyer Exp $

--- tools/examples/Makefile.orig	2015-01-12 17:53:24.000000000 +0100
+++ tools/examples/Makefile	2015-01-19 13:37:18.000000000 +0100
@@ -1,6 +1,6 @@
 XEN_ROOT = $(CURDIR)/../..
 include $(XEN_ROOT)/tools/Rules.mk
-
+XEN_CONFIG_DIR=${XEN_EXAMPLES_DIR}
 # Xen configuration dir and configs to go there.
 XEN_READMES = README
 XEN_READMES += README.incompatibilities
Add xenkernel413 and xentools413 packages, version 4.13.1. At this time xentools413 will only build on a very recent -current (as of an hour ago or do - with /usr/include/xen/xenio.h 1.12 or newer) Xen is a hypervisor which supports running multiple guest operating systems on a single machine. Guest OSes (also called "domains") can be either paravirtualised (i.e. make hypercalls in order to access hardware), run in HVM (Hardware Virtualisation Mode) where they will be presented with virtual devices, or a combination where they use hypercalls to access hardware but manage memory themselves. At boot, the xen kernel is loaded along with the guest kernel for the first domain (called domain0). domain0 has privileges to access the physical hardware (PCI and ISA devices), administrate other domains and provide virtual devices (disks and network) to other domains. 2020-05-26 13:12:10 +02:00			$NetBSD: patch-tools_examples_Makefile,v 1.1 2020/05/26 11:12:11 bouyer Exp $

			`--- tools/examples/Makefile.orig 2015-01-12 17:53:24.000000000 +0100`
			`+++ tools/examples/Makefile 2015-01-19 13:37:18.000000000 +0100`
			`@@ -1,6 +1,6 @@`
			`XEN_ROOT = $(CURDIR)/../..`
			`include $(XEN_ROOT)/tools/Rules.mk`
			`-`
			`+XEN_CONFIG_DIR=${XEN_EXAMPLES_DIR}`
			`# Xen configuration dir and configs to go there.`
			`XEN_READMES = README`
			`XEN_READMES += README.incompatibilities`