=> Bootstrap dependency digest>=20010302: found digest-20190127
===> Skipping vulnerability checks.
WARNING: No /var/db/pkg/pkg-vulnerabilities file found.
WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'.
=> Checksum SHA1 OK for ipxe-git-9a93db3f0947484e30e753bbd61a10b17336e20e.tar.gz
=> Checksum RMD160 OK for ipxe-git-9a93db3f0947484e30e753bbd61a10b17336e20e.tar.gz
=> Checksum SHA512 OK for ipxe-git-9a93db3f0947484e30e753bbd61a10b17336e20e.tar.gz
=> Checksum SHA1 OK for xen-4.6.6.tar.gz
=> Checksum RMD160 OK for xen-4.6.6.tar.gz
=> Checksum SHA512 OK for xen-4.6.6.tar.gz
===> Installing dependencies for xentools46-4.6.6nb11
==========================================================================
The following variables will affect the build process of this package,
xentools46-4.6.6nb11.  Their current value is shown below:

        * CURSES_DEFAULT = curses
        * PYTHON_VERSION_DEFAULT = 37
        * VARBASE = /var

Based on these variables, the following variables have been set:

        * CURSES_TYPE = curses
        * PYPACKAGE = python27
        * TERMCAP_TYPE = termcap

You may want to abort the process now with CTRL-C and change their value
before continuing.  Be sure to run `/usr/bin/make clean' after
the changes.
==========================================================================
=> Tool dependency glib2-tools-[0-9]*: found glib2-tools-2.64.2
=> Tool dependency bash-[0-9]*: found bash-5.0.17
=> Tool dependency gmake>=3.81: found gmake-4.2.1nb1
=> Tool dependency perl>=5.0: found perl-5.30.3
=> Tool dependency pkgconf-[0-9]*: found pkgconf-1.6.0
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency dev86-[0-9]*: found dev86-0.16.21
=> Build dependency pciutils>=3.0.2: found pciutils-3.7.0
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency py27-curses>=0: found py27-curses-2.7.18nb5
=> Full dependency python27>=2.7.1nb2: found python27-2.7.18
=> Full dependency ocaml>=4.09.0: found ocaml-4.09.1
=> Full dependency ocaml-findlib>=1.8.1: found ocaml-findlib-1.8.1
=> Full dependency glib2>=2.64.0nb1: found glib2-2.64.2nb1
=> Full dependency yajl>=1.0.9: found yajl-2.1.0
=> Full dependency argp>=1.3: found argp-1.3nb1
=> Full dependency pixman>=0.25.2: found pixman-0.40.0
===> Skipping vulnerability checks.
WARNING: No /var/db/pkg/pkg-vulnerabilities file found.
WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'.
===> Overriding tools for xentools46-4.6.6nb11
===> Extracting for xentools46-4.6.6nb11
===> Patching for xentools46-4.6.6nb11
=> Applying pkgsrc patches for xentools46-4.6.6nb11
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._.._ipxe_src_core_settings.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._.._ipxe_src_core_settings.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._.._ipxe_src_core_settings.c,v 1.1.1.1 2016/07/04 07:30:49 jnemeth Exp $
|
|--- ../../ipxe/src/core/settings.c.orig	2013-03-25 18:48:57.000000000 +0000
|+++ ../../ipxe/src/core/settings.c
--------------------------
Patching file ../../ipxe/src/core/settings.c using Plan A...
Hunk #1 succeeded at 284.
Hunk #2 succeeded at 297.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._.._ipxe_src_interface_efi_efi_snp.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._.._ipxe_src_interface_efi_efi_snp.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._.._ipxe_src_interface_efi_efi_snp.c,v 1.1.1.1 2016/07/04 07:30:49 jnemeth Exp $
|
|--- ../../ipxe/src/interface/efi/efi_snp.c.orig	2015-01-25 20:37:13.000000000 +0000
|+++ ../../ipxe/src/interface/efi/efi_snp.c
--------------------------
Patching file ../../ipxe/src/interface/efi/efi_snp.c using Plan A...
Hunk #1 succeeded at 984.
Hunk #2 succeeded at 1002.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._.._ipxe_src_net_fcels.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._.._ipxe_src_net_fcels.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._.._ipxe_src_net_fcels.c,v 1.1.1.1 2016/07/04 07:30:50 jnemeth Exp $
|
|--- ../../ipxe/src/net/fcels.c.orig	2015-01-25 20:27:57.000000000 +0000
|+++ ../../ipxe/src/net/fcels.c
--------------------------
Patching file ../../ipxe/src/net/fcels.c using Plan A...
Hunk #1 succeeded at 946.
Hunk #2 succeeded at 963.
Hunk #3 succeeded at 1006.
Hunk #4 succeeded at 1022.
Hunk #5 succeeded at 1043.
Hunk #6 succeeded at 1093.
Hunk #7 succeeded at 1257.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._.._ipxe_src_net_tls.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._.._ipxe_src_net_tls.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._.._ipxe_src_net_tls.c,v 1.1.1.1 2016/07/04 07:30:50 jnemeth Exp $
|
|--- ../../ipxe/src/net/tls.c.orig	2010-02-02 17:12:44.000000000 +0100
|+++ ../../ipxe/src/net/tls.c	2013-05-26 20:05:24.000000000 +0200
--------------------------
Patching file ../../ipxe/src/net/tls.c using Plan A...
Hunk #1 succeeded at 704.
Hunk #2 succeeded at 730.
Hunk #3 succeeded at 860.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._Config.mk
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._Config.mk
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._Config.mk,v 1.1.1.1 2016/07/04 07:30:50 jnemeth Exp $
|
|--- ../Config.mk.orig	2015-01-12 17:53:24.000000000 +0100
|+++ ../Config.mk	2015-01-19 13:16:16.000000000 +0100
--------------------------
Patching file ../Config.mk using Plan A...
Hunk #1 succeeded at 38.
Hunk #2 succeeded at 194.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_man_xl.cfg.pod.5
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_man_xl.cfg.pod.5
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._docs_man_xl.cfg.pod.5,v 1.1.1.1 2016/07/04 07:30:50 jnemeth Exp $
|
|--- ../docs/man/xl.cfg.pod.5.orig	2016-02-09 14:44:19.000000000 +0000
|+++ ../docs/man/xl.cfg.pod.5
--------------------------
Patching file ../docs/man/xl.cfg.pod.5 using Plan A...
Hunk #1 succeeded at 4.
Hunk #2 succeeded at 1854.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_man_xl.conf.pod.5
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_man_xl.conf.pod.5
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._docs_man_xl.conf.pod.5,v 1.1.1.1 2016/07/04 07:30:50 jnemeth Exp $
|
|--- ../docs/man/xl.conf.pod.5.orig	2015-01-12 17:53:24.000000000 +0100
|+++ ../docs/man/xl.conf.pod.5	2015-01-19 13:18:33.000000000 +0100
--------------------------
Patching file ../docs/man/xl.conf.pod.5 using Plan A...
Hunk #1 succeeded at 1.
Hunk #2 succeeded at 83.
Hunk #3 succeeded at 109.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_man_xl.pod.1
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_man_xl.pod.1
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._docs_man_xl.pod.1,v 1.1.1.1 2016/07/04 07:30:50 jnemeth Exp $
|
|--- ../docs/man/xl.pod.1.orig	2015-01-12 17:53:24.000000000 +0100
|+++ ../docs/man/xl.pod.1	2015-01-19 13:19:15.000000000 +0100
--------------------------
Patching file ../docs/man/xl.pod.1 using Plan A...
Hunk #1 succeeded at 33.
Hunk #2 succeeded at 50.
Hunk #3 succeeded at 175 (offset 7 lines).
Hunk #4 succeeded at 471 (offset 8 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_man_xlcpupool.cfg.pod.5
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_man_xlcpupool.cfg.pod.5
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._docs_man_xlcpupool.cfg.pod.5,v 1.1.1.1 2016/07/04 07:30:50 jnemeth Exp $
|
|--- ../docs/man/xlcpupool.cfg.pod.5.orig	2015-01-12 17:53:24.000000000 +0100
|+++ ../docs/man/xlcpupool.cfg.pod.5	2015-01-19 13:16:17.000000000 +0100
--------------------------
Patching file ../docs/man/xlcpupool.cfg.pod.5 using Plan A...
Hunk #1 succeeded at 4.
Hunk #2 succeeded at 117 (offset 16 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_misc_xl-disk-configuration.txt
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-.._docs_misc_xl-disk-configuration.txt
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-.._docs_misc_xl-disk-configuration.txt,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- ../docs/misc/xl-disk-configuration.txt.orig	2015-11-03 10:11:18.000000000 +0100
|+++ ../docs/misc/xl-disk-configuration.txt	2016-03-29 22:48:24.000000000 +0200
--------------------------
Patching file ../docs/misc/xl-disk-configuration.txt using Plan A...
Hunk #1 succeeded at 173.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-Makefile,v 1.1.1.1 2016/07/04 07:30:50 jnemeth Exp $
|
|--- Makefile.orig	2016-02-09 14:44:19.000000000 +0000
|+++ Makefile
--------------------------
Patching file Makefile using Plan A...
Hunk #1 succeeded at 17.
Hunk #2 succeeded at 32.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-Rules.mk
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-Rules.mk
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-Rules.mk,v 1.1.1.1 2016/07/04 07:30:50 jnemeth Exp $
|
|--- Rules.mk.orig	2016-02-09 14:44:19.000000000 +0000
|+++ Rules.mk
--------------------------
Patching file Rules.mk using Plan A...
Hunk #1 succeeded at 36.
Hunk #2 succeeded at 66.
Hunk #3 succeeded at 75.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-XSA228
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-XSA228
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA228,v 1.1 2017/10/17 10:57:34 bouyer Exp $
|
|From cb91f4c43bd4158daa6561c73921a6455176f278 Mon Sep 17 00:00:00 2001
|From: Jan Beulich <jbeulich@suse.com>
|Date: Mon, 31 Jul 2017 15:17:56 +0100
|Subject: [PATCH] gnttab: split maptrack lock to make it fulfill its purpose
| again
|
|The way the lock is currently being used in get_maptrack_handle(), it
|protects only the maptrack limit: The function acts on current's list
|only, so races on list accesses are impossible even without the lock.
|
|Otoh list access races are possible between __get_maptrack_handle() and
|put_maptrack_handle(), due to the invocation of the former for other
|than current from steal_maptrack_handle(). Introduce a per-vCPU lock
|for list accesses to become race free again. This lock will be
|uncontended except when it becomes necessary to take the steal path,
|i.e. in the common case there should be no meaningful performance
|impact.
|
|When in get_maptrack_handle adds a stolen entry to a fresh, empty,
|freelist, we think that there is probably no concurrency.  However,
|this is not a fast path and adding the locking there makes the code
|clearly correct.
|
|Also, while we are here: the stolen maptrack_entry's tail pointer was
|not properly set.  Set it.
|
|This is XSA-228.
|
|Reported-by: Ian Jackson <ian.jackson@eu.citrix.com>
|Signed-off-by: Jan Beulich <jbeulich@suse.com>
|Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
|---
| docs/misc/grant-tables.txt    |  7 ++++++-
| xen/common/grant_table.c      | 30 ++++++++++++++++++++++++------
| xen/include/xen/grant_table.h |  2 +-
| xen/include/xen/sched.h       |  1 +
| 4 files changed, 32 insertions(+), 8 deletions(-)
|
|diff --git a/docs/misc/grant-tables.txt b/docs/misc/grant-tables.txt
|index 417ce2d..64da5cf 100644
|--- ../docs/misc/grant-tables.txt.orig
|+++ ../docs/misc/grant-tables.txt
--------------------------
Patching file ../docs/misc/grant-tables.txt using Plan A...
Hunk #1 succeeded at 87.
Hunk #2 succeeded at 103.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-XSA233
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-XSA233
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA233,v 1.1 2017/10/17 10:57:34 bouyer Exp $
|
|From: Juergen Gross <jgross@suse.com>
|Subject: tools/xenstore: dont unlink connection object twice
|
|A connection object of a domain with associated stubdom has two
|parents: the domain and the stubdom. When cleaning up the list of
|active domains in domain_cleanup() make sure not to unlink the
|connection twice from the same domain. This could happen when the
|domain and its stubdom are being destroyed at the same time leading
|to the domain loop being entered twice.
|
|Additionally don't use talloc_free() in this case as it will remove
|a random parent link, leading eventually to a memory leak. Use
|talloc_unlink() instead specifying the context from which the
|connection object should be removed.
|
|This is XSA-233.
|
|Reported-by: Eric Chanudet <chanudete@ainfosec.com>
|Signed-off-by: Juergen Gross <jgross@suse.com>
|Reviewed-by: Ian Jackson <ian.jackson@eu.citrix.com>
|
|--- xenstore/xenstored_domain.c.orig
|+++ xenstore/xenstored_domain.c
--------------------------
Patching file xenstore/xenstored_domain.c using Plan A...
Hunk #1 succeeded at 220 (offset -1 lines).
Hunk #2 succeeded at 236 (offset -1 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-XSA240
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-XSA240
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA240,v 1.1 2017/10/17 10:57:34 bouyer Exp $
|
|From eeea00c427376c269ffa34587f16fa1182d8c29d Mon Sep 17 00:00:00 2001
|From: George Dunlap <george.dunlap@citrix.com>
|Date: Fri, 22 Sep 2017 11:46:55 +0100
|Subject: [PATCH 2/2] x86/mm: Disable PV linear pagetables by default
|
|Allowing pagetables to point to other pagetables of the same level
|(often called 'linear pagetables') has been included in Xen since its
|inception.  But it is not used by the most common PV guests (Linux,
|NetBSD, minios), and has been the source of a number of subtle
|reference-counting bugs.
|
|Add a command-line option to control whether PV linear pagetables are
|allowed (disabled by default).
|
|Reported-by: Jann Horn <jannh@google.com>
|Signed-off-by: George Dunlap <george.dunlap@citrix.com>
|Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
|---
|Changes since v2:
|- s/_/-/; in command-line option
|- Added __read_mostly
|---
| docs/misc/xen-command-line.markdown | 15 +++++++++++++++
| xen/arch/x86/mm.c                   |  9 +++++++++
| 2 files changed, 24 insertions(+)
|
|diff --git a/docs/misc/xen-command-line.markdown b/docs/misc/xen-command-line.markdown
|index d99a20a44b..c91acaa464 100644
|--- ../docs/misc/xen-command-line.markdown.orig
|+++ ../docs/misc/xen-command-line.markdown
--------------------------
Patching file ../docs/misc/xen-command-line.markdown using Plan A...
Hunk #1 succeeded at 1231.
Hmm...  Ignoring the trailing garbage.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-configure
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-configure
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-configure,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- configure.orig	2016-02-09 14:44:19.000000000 +0000
|+++ configure
--------------------------
Patching file configure using Plan A...
Hunk #1 succeeded at 2402.
Hunk #2 succeeded at 3838.
Hunk #3 succeeded at 3916.
Hunk #4 succeeded at 3936.
Hunk #5 succeeded at 10339 (offset 306 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-console_daemon_utils.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-console_daemon_utils.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-console_daemon_utils.c,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- console/daemon/utils.c.orig	2015-06-22 13:41:35.000000000 +0000
|+++ console/daemon/utils.c
--------------------------
Patching file console/daemon/utils.c using Plan A...
Hunk #1 succeeded at 112 (offset -1 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-debugger_gdbsx_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-debugger_gdbsx_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-debugger_gdbsx_Makefile,v 1.1 2017/10/28 03:14:17 khorben Exp $
|
|Add support for LDFLAGS when building gdbsx
|
|--- debugger/gdbsx/Makefile.orig	2017-07-06 07:04:28.000000000 +0000
|+++ debugger/gdbsx/Makefile
--------------------------
Patching file debugger/gdbsx/Makefile using Plan A...
Hunk #1 succeeded at 22.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-examples_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-examples_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-examples_Makefile,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- examples/Makefile.orig	2015-01-12 17:53:24.000000000 +0100
|+++ examples/Makefile	2015-01-19 13:37:18.000000000 +0100
--------------------------
Patching file examples/Makefile using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-firmware_etherboot_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-firmware_etherboot_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-firmware_etherboot_Makefile,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- firmware/etherboot/Makefile.orig	2015-01-12 17:53:24.000000000 +0100
|+++ firmware/etherboot/Makefile	2015-01-19 13:42:54.000000000 +0100
--------------------------
Patching file firmware/etherboot/Makefile using Plan A...
Hunk #1 succeeded at 27.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-firmware_etherboot_patches_series
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-firmware_etherboot_patches_series
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-firmware_etherboot_patches_series,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- firmware/etherboot/patches/series.orig	2015-01-12 17:53:24.000000000 +0100
|+++ firmware/etherboot/patches/series	2015-01-19 13:16:37.000000000 +0100
--------------------------
Patching file firmware/etherboot/patches/series using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-firmware_hvmloader_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-firmware_hvmloader_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-firmware_hvmloader_Makefile,v 1.2 2018/07/03 13:57:20 maya Exp $
|
|Fix for newer iasl. From royger upstream.
|https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=858dbaaeda33b05c1ac80aea0ba9a03924e09005
|
|--- firmware/hvmloader/acpi/Makefile.orig	2017-07-06 07:04:28.000000000 +0000
|+++ firmware/hvmloader/acpi/Makefile
--------------------------
Patching file firmware/hvmloader/acpi/Makefile using Plan A...
Hunk #1 succeeded at 27.
Hunk #2 succeeded at 44.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_NetBSD_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_NetBSD_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-hotplug_NetBSD_Makefile,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- hotplug/NetBSD/Makefile.orig	2016-02-09 14:44:19.000000000 +0000
|+++ hotplug/NetBSD/Makefile
--------------------------
Patching file hotplug/NetBSD/Makefile using Plan A...
Hunk #1 succeeded at 3.
Hunk #2 succeeded at 22.
Hunk #3 succeeded at 35.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_NetBSD_block
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_NetBSD_block
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-hotplug_NetBSD_block,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- hotplug/NetBSD/block.orig	2016-02-09 14:44:19.000000000 +0000
|+++ hotplug/NetBSD/block
--------------------------
Patching file hotplug/NetBSD/block using Plan A...
Hunk #1 succeeded at 6.
Hunk #2 succeeded at 63.
Hunk #3 succeeded at 79.
Hunk #4 succeeded at 89.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_NetBSD_vif-bridge
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_NetBSD_vif-bridge
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-hotplug_NetBSD_vif-bridge,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- hotplug/NetBSD/vif-bridge.orig	2015-01-12 17:53:24.000000000 +0100
|+++ hotplug/NetBSD/vif-bridge	2015-01-19 13:16:37.000000000 +0100
--------------------------
Patching file hotplug/NetBSD/vif-bridge using Plan A...
Hunk #1 succeeded at 23.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_NetBSD_vif-ip
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_NetBSD_vif-ip
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-hotplug_NetBSD_vif-ip,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- hotplug/NetBSD/vif-ip.orig	2015-01-12 17:53:24.000000000 +0100
|+++ hotplug/NetBSD/vif-ip	2015-01-19 13:16:37.000000000 +0100
--------------------------
Patching file hotplug/NetBSD/vif-ip using Plan A...
Hunk #1 succeeded at 24.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_common_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-hotplug_common_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-hotplug_common_Makefile,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- hotplug/common/Makefile.orig	2015-01-12 17:53:24.000000000 +0100
|+++ hotplug/common/Makefile	2015-01-19 13:16:37.000000000 +0100
--------------------------
Patching file hotplug/common/Makefile using Plan A...
Hunk #1 succeeded at 23.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-include_xen-sys_NetBSD_gntdev.h
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-include_xen-sys_NetBSD_gntdev.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-include_xen-sys_NetBSD_gntdev.h,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- include/xen-sys/NetBSD/gntdev.h.orig	2015-01-19 13:16:37.000000000 +0100
|+++ include/xen-sys/NetBSD/gntdev.h	2015-01-19 13:16:37.000000000 +0100
--------------------------
(Creating file include/xen-sys/NetBSD/gntdev.h...)
Patching file include/xen-sys/NetBSD/gntdev.h using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libfsimage_ufs_ufs.h
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libfsimage_ufs_ufs.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libfsimage_ufs_ufs.h,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- libfsimage/ufs/ufs.h.orig	2015-01-12 17:53:24.000000000 +0100
|+++ libfsimage/ufs/ufs.h	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file libfsimage/ufs/ufs.h using Plan A...
Hunk #1 succeeded at 4.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxc_xc__netbsd.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxc_xc__netbsd.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxc_xc__netbsd.c,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- libxc/xc_netbsd.c.orig	2016-02-09 14:44:19.000000000 +0000
|+++ libxc/xc_netbsd.c
--------------------------
Patching file libxc/xc_netbsd.c using Plan A...
Hunk #1 succeeded at 17.
Hunk #2 succeeded at 395.
Hunk #3 succeeded at 607.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxl_Makefile,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- libxl/Makefile.orig	2016-02-09 14:44:19.000000000 +0000
|+++ libxl/Makefile
--------------------------
Patching file libxl/Makefile using Plan A...
Hunk #1 succeeded at 276.
Hunk #2 succeeded at 291.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl__create.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl__create.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxl_libxl__create.c,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- libxl/libxl_create.c.orig	2015-01-12 17:53:24.000000000 +0100
|+++ libxl/libxl_create.c	2015-01-19 14:08:19.000000000 +0100
--------------------------
Patching file libxl/libxl_create.c using Plan A...
Hunk #1 succeeded at 422 (offset -10 lines).
Hunk #2 succeeded at 459 (offset -10 lines).
Hunk #3 succeeded at 1094 (offset 33 lines).
Hunk #4 succeeded at 1061 (offset -10 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl__netbsd.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl__netbsd.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxl_libxl__netbsd.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- libxl/libxl_netbsd.c.orig	2016-06-20 12:08:22.000000000 +0000
|+++ libxl/libxl_netbsd.c
--------------------------
Patching file libxl/libxl_netbsd.c using Plan A...
Hunk #1 succeeded at 68.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl__save__helper.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl__save__helper.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxl_libxl__save__helper.c,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- libxl/libxl_save_helper.c.orig	2015-01-25 21:04:31.000000000 +0000
|+++ libxl/libxl_save_helper.c
--------------------------
Patching file libxl/libxl_save_helper.c using Plan A...
Hunk #1 succeeded at 52 (offset 3 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl_event.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl_event.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxl_libxl_event.c,v 1.1 2016/12/20 17:24:58 bouyer Exp $
|
|The SIGCHLD handler just writes to a pipe where the reader is the
|same process. The idea is that this will cause poll(2) in the main
|thread to exit with the reaper pipe readable, and do child cleanup here.
|
|Unfortunably, is the child also has a write pipe back to the
|parent (as e.g. with pygrub), the loop in afterpoll_internal() may see the
|POLLHUP event on this pipe before the POLLIN even on the reaper pipe, and
|this will be considered as an error (from e.g. pygrub).
|
|work around by filtering POLLHUP events here
|
|--- libxl/libxl_event.c.orig	2016-12-20 16:01:30.000000000 +0100
|+++ libxl/libxl_event.c	2016-12-20 17:28:52.000000000 +0100
--------------------------
Patching file libxl/libxl_event.c using Plan A...
Hunk #1 succeeded at 1261.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl_internal.h
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl_internal.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxl_libxl_internal.h,v 1.1 2017/03/21 22:52:52 bouyer Exp $
|
|bump some timeouts to more reasonable values. 40s is not enough
|if there is lots of them (e.g lots of network interfaces) and they
|need to be serialized.
|
|--- libxl/libxl_internal.h.orig	2017-03-21 23:13:59.000000000 +0100
|+++ libxl/libxl_internal.h	2017-03-21 23:14:47.000000000 +0100
--------------------------
Patching file libxl/libxl_internal.h using Plan A...
Hunk #1 succeeded at 85.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl_uuid.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_libxl_uuid.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxl_libxl_uuid.c,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- libxl/libxl_uuid.c.orig	2015-01-19 17:05:02.000000000 +0100
|+++ libxl/libxl_uuid.c	2015-01-19 17:18:47.000000000 +0100
--------------------------
Patching file libxl/libxl_uuid.c using Plan A...
Hunk #1 succeeded at 77.
Hunk #2 succeeded at 112.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_xl__cmdtable.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_xl__cmdtable.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxl_xl__cmdtable.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- libxl/xl_cmdtable.c.orig	2015-11-03 09:11:18.000000000 +0000
|+++ libxl/xl_cmdtable.c
--------------------------
Patching file libxl/xl_cmdtable.c using Plan A...
Hunk #1 succeeded at 493 (offset -14 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_xl_cmdimpl.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-libxl_xl_cmdimpl.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libxl_xl_cmdimpl.c,v 1.1 2017/03/21 22:52:52 bouyer Exp $
|avoid shadowing a global on netbsd-6.
|
|--- libxl/xl_cmdimpl.c.orig	2017-03-21 23:27:46.000000000 +0100
|+++ libxl/xl_cmdimpl.c	2017-03-21 23:28:17.000000000 +0100
--------------------------
Patching file libxl/xl_cmdimpl.c using Plan A...
Hunk #1 succeeded at 473.
Hunk #2 succeeded at 505.
Hunk #3 succeeded at 8076.
Hunk #4 succeeded at 8088.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-ocaml_common.make
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-ocaml_common.make
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ocaml_common.make,v 1.3 2018/01/27 18:24:16 abs Exp $
|
|Add -unsafe-string to fix build with ocaml-4.06.0 and later
|
|--- ocaml/common.make.orig	2017-07-06 07:04:28.000000000 +0000
|+++ ocaml/common.make
--------------------------
Patching file ocaml/common.make using Plan A...
Hunk #1 succeeded at 3.
Hunk #2 succeeded at 12.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-ocaml_xenstored_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-ocaml_xenstored_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ocaml_xenstored_Makefile,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- ocaml/xenstored/Makefile.orig	2016-02-09 14:44:19.000000000 +0000
|+++ ocaml/xenstored/Makefile
--------------------------
Patching file ocaml/xenstored/Makefile using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-ocaml_xenstored_define.ml
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-ocaml_xenstored_define.ml
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ocaml_xenstored_define.ml,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- ocaml/xenstored/define.ml.orig	2015-01-12 17:53:24.000000000 +0100
|+++ ocaml/xenstored/define.ml	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file ocaml/xenstored/define.ml using Plan A...
Hunk #1 succeeded at 17.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-ocaml_xenstored_utils.ml
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-ocaml_xenstored_utils.ml
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ocaml_xenstored_utils.ml,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- ocaml/xenstored/utils.ml.orig	2015-01-12 17:53:24.000000000 +0100
|+++ ocaml/xenstored/utils.ml	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file ocaml/xenstored/utils.ml using Plan A...
Hunk #1 succeeded at 94.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-pygrub_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-pygrub_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-pygrub_Makefile,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- pygrub/Makefile.orig	2016-02-09 14:44:19.000000000 +0000
|+++ pygrub/Makefile
--------------------------
Patching file pygrub/Makefile using Plan A...
Hunk #1 succeeded at 17.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_Makefile,v 1.1.1.1 2016/07/04 07:30:52 jnemeth Exp $
|
|--- qemu-xen-traditional/Makefile.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/Makefile	2015-01-19 14:16:12.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/Makefile using Plan A...
Hunk #1 succeeded at 1.
Hunk #2 succeeded at 231.
Hunk #3 succeeded at 275.
Hunk #4 succeeded at 284.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_block-raw-posix.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_block-raw-posix.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_block-raw-posix.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|- if given a block device, use the character device instead.
|
|--- qemu-xen-traditional/block-raw-posix.c.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/block-raw-posix.c	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/block-raw-posix.c using Plan A...
Hunk #1 succeeded at 65.
Hunk #2 succeeded at 73.
Hunk #3 succeeded at 1017 (offset 1 line).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_configure
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_configure
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_configure,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen-traditional/configure.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/configure	2015-01-20 22:58:07.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/configure using Plan A...
Hunk #1 succeeded at 1089.
Hunk #2 succeeded at 1124.
Hunk #3 succeeded at 1216.
Hunk #4 succeeded at 1495.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_e1000.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_e1000.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_hw_e1000.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|From sysutils/xentools33/patches/patch-ak.
|
|qemu-0.13.x will include this fix:
|http://git.qemu.org/qemu.git/commit/?id=9651ac55e5de0e1534d898316cc851af6ffc4334
|
|--- qemu-xen-traditional/hw/e1000.c.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/hw/e1000.c	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/hw/e1000.c using Plan A...
Hunk #1 succeeded at 265.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_ide.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_ide.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_hw_ide.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen-traditional/hw/ide.c.orig	2014-01-09 13:44:42.000000000 +0100
|+++ qemu-xen-traditional/hw/ide.c	2015-06-11 16:15:49.000000000 +0200
--------------------------
Patching file qemu-xen-traditional/hw/ide.c using Plan A...
Hunk #1 succeeded at 757.
Hunk #2 succeeded at 817.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pass-through.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pass-through.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_hw_pass-through.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen-traditional/hw/pass-through.c.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/hw/pass-through.c	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/hw/pass-through.c using Plan A...
Hunk #1 succeeded at 84.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pass-through.h
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pass-through.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_hw_pass-through.h,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen-traditional/hw/pass-through.h.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/hw/pass-through.h	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/hw/pass-through.h using Plan A...
Hunk #1 succeeded at 20.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_piix4acpi.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_piix4acpi.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_hw_piix4acpi.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen-traditional/hw/piix4acpi.c.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/hw/piix4acpi.c	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/hw/piix4acpi.c using Plan A...
Hunk #1 succeeded at 41.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pt-graphics.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pt-graphics.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_hw_pt-graphics.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen-traditional/hw/pt-graphics.c.orig	2015-01-19 16:14:46.000000000 +0100
|+++ qemu-xen-traditional/hw/pt-graphics.c	2015-01-19 16:14:51.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/hw/pt-graphics.c using Plan A...
Hunk #1 succeeded at 4.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pt-msi.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pt-msi.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_hw_pt-msi.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen-traditional/hw/pt-msi.c.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/hw/pt-msi.c	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/hw/pt-msi.c using Plan A...
Hunk #1 succeeded at 22.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pt-msi.h
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_hw_pt-msi.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_hw_pt-msi.h,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen-traditional/hw/pt-msi.h.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/hw/pt-msi.h	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/hw/pt-msi.h using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_i386-dm_hookstarget.mak
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_i386-dm_hookstarget.mak
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_i386-dm_hookstarget.mak,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen-traditional/i386-dm/hookstarget.mak.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/i386-dm/hookstarget.mak	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/i386-dm/hookstarget.mak using Plan A...
Hunk #1 succeeded at 2.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_xen-hooks.mak
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen-traditional_xen-hooks.mak
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen-traditional_xen-hooks.mak,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|enable PCI passthrough when pciutils is present
|
|--- qemu-xen-traditional/xen-hooks.mak.orig	2014-10-06 17:50:24.000000000 +0200
|+++ qemu-xen-traditional/xen-hooks.mak	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen-traditional/xen-hooks.mak using Plan A...
Hunk #1 succeeded at 59.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_audio_audio.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_audio_audio.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen_audio_audio.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen/audio/audio.c.orig	2014-12-02 11:41:02.000000000 +0100
|+++ qemu-xen/audio/audio.c	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file qemu-xen/audio/audio.c using Plan A...
Hunk #1 succeeded at 1173.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_hw_i386_ssdt-misc.dsl
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_hw_i386_ssdt-misc.dsl
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen_hw_i386_ssdt-misc.dsl,v 1.1 2018/07/03 13:57:20 maya Exp $
|
|Fix for newer iasl.
|Length was previously truncated to 8 characters.
|
|--- qemu-xen/hw/i386/ssdt-misc.dsl.orig	2017-06-21 15:43:09.000000000 +0000
|+++ qemu-xen/hw/i386/ssdt-misc.dsl
--------------------------
Patching file qemu-xen/hw/i386/ssdt-misc.dsl using Plan A...
Hunk #1 succeeded at 16.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_hw_i386_ssdt-pcihp.dsl
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_hw_i386_ssdt-pcihp.dsl
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen_hw_i386_ssdt-pcihp.dsl,v 1.1 2018/07/03 13:57:20 maya Exp $
|
|Fix for newer iasl.
|Length was previously truncated to 8 characters.
|
|--- qemu-xen/hw/i386/ssdt-pcihp.dsl.orig	2017-06-21 15:43:09.000000000 +0000
|+++ qemu-xen/hw/i386/ssdt-pcihp.dsl
--------------------------
Patching file qemu-xen/hw/i386/ssdt-pcihp.dsl using Plan A...
Hunk #1 succeeded at 15.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_qemu-doc.texi
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_qemu-doc.texi
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen_qemu-doc.texi,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|Avoid encoding issues in pod2man.
|
|--- qemu-xen/qemu-doc.texi.orig	2014-12-02 11:41:02.000000000 +0100
|+++ qemu-xen/qemu-doc.texi	2015-01-19 14:24:23.000000000 +0100
--------------------------
Patching file qemu-xen/qemu-doc.texi using Plan A...
Hunk #1 succeeded at 220.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_xen-hvm.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-qemu-xen_xen-hvm.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen_xen-hvm.c,v 1.1.1.1 2016/07/04 07:30:53 jnemeth Exp $
|
|--- qemu-xen/xen-hvm.c.orig	2016-01-06 16:42:43.000000000 +0000
|+++ qemu-xen/xen-hvm.c
--------------------------
Patching file qemu-xen/xen-hvm.c using Plan A...
Hunk #1 succeeded at 621 (offset 9 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-xenpaging_xenpaging.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-xenpaging_xenpaging.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xenpaging_xenpaging.c,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- xenpaging/xenpaging.c.orig	2016-06-20 12:08:22.000000000 +0000
|+++ xenpaging/xenpaging.c
--------------------------
Patching file xenpaging/xenpaging.c using Plan A...
Hunk #1 succeeded at 182.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-xenstore_xc.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-xenstore_xc.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xenstore_xc.c,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- xenstore/xs.c.orig	2015-01-19 15:40:00.000000000 +0100
|+++ xenstore/xs.c	2015-01-19 15:46:56.000000000 +0100
--------------------------
Patching file xenstore/xs.c using Plan A...
Hunk #1 succeeded at 724 (offset -1 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-xentrace_xenalyze.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-xentrace_xenalyze.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xentrace_xenalyze.c,v 1.2 2018/07/03 14:05:04 maya Exp $
|
|Remove unused function, guard misleading indentation (from upstream)
|
|--- xentrace/xenalyze.c.orig	2017-07-06 07:04:28.000000000 +0000
|+++ xentrace/xenalyze.c
--------------------------
Patching file xentrace/xenalyze.c using Plan A...
Hunk #1 succeeded at 2132.
Hunk #2 succeeded at 2213.
Hunk #3 succeeded at 4125.
Hunk #4 succeeded at 4142.
done
=> Verifying /data/pkgsrc/sysutils/xentools46/patches/patch-xentrace_xentrace.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools46/patches/patch-xentrace_xentrace.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xentrace_xentrace.c,v 1.1.1.1 2016/07/04 07:30:51 jnemeth Exp $
|
|--- xentrace/xentrace.c.orig	2016-02-09 14:44:19.000000000 +0000
|+++ xentrace/xentrace.c
--------------------------
Patching file xentrace/xentrace.c using Plan A...
Hunk #1 succeeded at 945.
done
===> Creating toolchain wrappers for xentools46-4.6.6nb11
===> Configuring for xentools46-4.6.6nb11
=> Substituting "conf" in ocaml/xenstored/define.ml libxl/xl_cmdtable.c ../docs/misc/xl-disk-configuration.txt
=> Substituting "pathsvar" in Makefile  hotplug/Linux/init.d/sysconfig.xendomains
=> Substituting "perlpath" in ../tools/misc/xencov_split ../tools/firmware/rombios/makesym.perl ../tools/qemu-xen-traditional/texi2pod.pl ../tools/examples/xeninfo.pl ../tools/include/xen-external/bsd-sys-queue-h-seddery ../tools/qemu-xen/scripts/texi2pod.pl ../tools/qemu-xen/scripts/get_maintainer.pl ../tools/qemu-xen/scripts/checkpatch.pl ../tools/libxl/libxl_save_msgs_gen.pl ../tools/libxl/check-libxl-api-rules ../../ipxe/src/drivers/infiniband/qib_genbits.pl ../../ipxe/src/util/catrom.pl ../../ipxe/src/util/diffsize.pl ../../ipxe/src/util/disrom.pl ../../ipxe/src/util/get-pci-ids ../../ipxe/src/util/licence.pl ../../ipxe/src/util/mergerom.pl ../../ipxe/src/util/modrom.pl ../../ipxe/src/util/padimg.pl ../../ipxe/src/util/parserom.pl ../../ipxe/src/util/sortobjdump.pl ../../ipxe/src/util/swapdevids.pl ../../ipxe/src/util/symcheck.pl
=> Substituting "proc" in ocaml/xenstored/define.ml
=> Substituting "procdev" in ocaml/xenstored/define.ml
=> Modifying GNU configure scripts to avoid --recheck
=> Replacing config-guess with pkgsrc versions
=> Replacing config-sub with pkgsrc versions
=> Replacing install-sh with pkgsrc version
=> Replacing python interpreter in misc/xen-bugtool misc/xen-ringwatch misc/xencons misc/xenpvnetboot misc/xensymoops python/scripts/convert-legacy-stream python/scripts/verify-stream-v2 xenmon/xenmon.py.
=> Checking for portability problems in extracted files
configure: WARNING: Setting CC, CFLAGS, LDFLAGS, LIBS, CPPFLAGS or CPP is not recommended, use PREPEND_INCLUDES, PREPEND_LIB, APPEND_INCLUDES and APPEND_LIB instead when possible.
checking build system type... x86_64--netbsd
checking host system type... x86_64--netbsd
checking for x86_64--netbsd-gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether clang accepts -g... yes
checking for clang option to accept ISO C89... none needed
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for x86_64--netbsd-gcc... (cached) clang
checking whether we are using the GNU C compiler... (cached) yes
checking whether clang accepts -g... (cached) yes
checking for clang option to accept ISO C89... (cached) none needed
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c -o pbulkXXX -g users
checking for bison... no
checking for flex... /usr/bin/flex
checking for perl... /usr/pkg/bin/perl
checking for awk... /usr/bin/awk
checking for x86_64--netbsd-ocamlc... no
checking for ocamlc... ocamlc
OCaml version is 4.09.1
OCaml library path is /usr/pkg/lib/ocaml
checking for x86_64--netbsd-ocamlopt... no
checking for ocamlopt... ocamlopt
checking for x86_64--netbsd-ocamlc.opt... no
checking for ocamlc.opt... ocamlc.opt
checking for x86_64--netbsd-ocamlopt.opt... no
checking for ocamlopt.opt... ocamlopt.opt
checking for x86_64--netbsd-ocaml... no
checking for ocaml... ocaml
checking for x86_64--netbsd-ocamldep... no
checking for ocamldep... ocamldep
checking for x86_64--netbsd-ocamlmktop... no
checking for ocamlmktop... ocamlmktop
checking for x86_64--netbsd-ocamlmklib... no
checking for ocamlmklib... ocamlmklib
checking for x86_64--netbsd-ocamldoc... no
checking for ocamldoc... ocamldoc
checking for x86_64--netbsd-ocamlbuild... no
checking for ocamlbuild... no
checking for x86_64--netbsd-ocamlfind... no
checking for ocamlfind... ocamlfind
checking for gawk... /usr/bin/awk
checking for x86_64--netbsd-checkpolicy... no
checking for checkpolicy... no
checking for bash... /data/scratch/sysutils/xentools46/work/.tools/bin/bash
checking for python2.7... /usr/pkg/bin/python2.7
checking for python version >= 2.3 ... yes
checking how to run the C preprocessor... clang -E
checking for grep that handles long lines and -e... (cached) /usr/bin/grep
checking for egrep... (cached) /usr/bin/egrep
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for python2.7-config... /usr/pkg/bin/python2.7-config
checking Python.h usability... yes
checking Python.h presence... yes
checking for Python.h... yes
checking for PyArg_ParseTuple in -lpython2.7... yes
checking whether Python setup.py brokenly enables -D_FORTIFY_SOURCE... no
checking for xgettext... /usr/bin/xgettext
checking for as86... /usr/pkg/bin/as86
checking for ld86... /usr/pkg/bin/ld86
checking for bcc... /usr/pkg/bin/bcc
checking for iasl... /usr/bin/iasl
checking uuid/uuid.h usability... no
checking uuid/uuid.h presence... no
checking for uuid/uuid.h... no
checking uuid.h usability... yes
checking uuid.h presence... yes
checking for uuid.h... yes
checking curses.h usability... yes
checking curses.h presence... yes
checking for curses.h... yes
checking for clear in -lcurses... yes
checking ncurses.h usability... no
checking ncurses.h presence... no
checking for ncurses.h... no
checking pkg-config is at least version 0.9.0... yes
checking for glib... yes
checking for pixman... yes
checking for wget... no
checking for ftp... /data/scratch/sysutils/xentools46/work/.tools/bin/ftp
checking bzlib.h usability... yes
checking bzlib.h presence... yes
checking for bzlib.h... yes
checking for BZ2_bzDecompressInit in -lbz2... yes
checking lzma.h usability... yes
checking lzma.h presence... yes
checking for lzma.h... yes
checking for lzma_stream_decoder in -llzma... yes
checking lzo/lzo1x.h usability... no
checking lzo/lzo1x.h presence... no
checking for lzo/lzo1x.h... no
checking for MD5 in -lcrypto... yes
checking ext2fs/ext2fs.h usability... no
checking ext2fs/ext2fs.h presence... no
checking for ext2fs/ext2fs.h... no
checking ext4fs/ext2fs.h usability... no
checking ext4fs/ext2fs.h presence... no
checking for ext4fs/ext2fs.h... no
checking for gcry_md_hash_buffer in -lgcrypt... no
checking for pthread flag... -pthread
checking libutil.h usability... no
checking libutil.h presence... no
checking for libutil.h... no
checking for openpty et al... -lutil
checking for yajl_alloc in -lyajl... yes
checking for deflateCopy in -lz... yes
checking for libiconv_open in -liconv... no
checking argp.h usability... yes
checking argp.h presence... yes
checking for argp.h... yes
checking for argp_usage in -largp... yes
checking yajl/yajl_version.h usability... yes
checking yajl/yajl_version.h presence... yes
checking for yajl/yajl_version.h... yes
checking sys/eventfd.h usability... no
checking sys/eventfd.h presence... no
checking for sys/eventfd.h... no
checking valgrind/memcheck.h usability... no
checking valgrind/memcheck.h presence... no
checking for valgrind/memcheck.h... no
checking utmp.h usability... yes
checking utmp.h presence... yes
checking for utmp.h... yes
checking for LIBNL3... no
configure: WARNING: Disabling support for Remus network buffering.
    Please install libnl3 libraries, command line tools and devel
    headers - version 3.2.8 or higher
checking for SYSTEMD... no
checking for SYSTEMD... no
configure: creating ./config.status
config.status: creating ../config/Tools.mk
config.status: creating ../config/Paths.mk
config.status: creating hotplug/FreeBSD/rc.d/xencommons
config.status: creating hotplug/FreeBSD/rc.d/xendriverdomain
config.status: creating hotplug/Linux/init.d/sysconfig.xencommons
config.status: creating hotplug/Linux/init.d/xen-watchdog
config.status: creating hotplug/Linux/init.d/xencommons
config.status: creating hotplug/Linux/init.d/xendomains
config.status: creating hotplug/Linux/init.d/xendriverdomain
config.status: creating hotplug/Linux/vif-setup
config.status: creating hotplug/Linux/xen-hotplug-common.sh
config.status: creating hotplug/Linux/xendomains
config.status: creating hotplug/NetBSD/rc.d/xencommons
config.status: creating hotplug/NetBSD/rc.d/xendriverdomain
config.status: creating libxl/xenlight.pc.in
config.status: creating libxl/xlutil.pc.in
config.status: creating config.h