=> Bootstrap dependency digest>=20010302: found digest-20160304 ===> 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 xen48/gmp-4.3.2.tar.bz2 => Checksum RMD160 OK for xen48/gmp-4.3.2.tar.bz2 => Checksum SHA512 OK for xen48/gmp-4.3.2.tar.bz2 => Checksum SHA1 OK for xen48/grub-0.97.tar.gz => Checksum RMD160 OK for xen48/grub-0.97.tar.gz => Checksum SHA512 OK for xen48/grub-0.97.tar.gz => Checksum SHA1 OK for xen48/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz => Checksum RMD160 OK for xen48/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz => Checksum SHA512 OK for xen48/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz => Checksum SHA1 OK for xen48/lwip-1.3.0.tar.gz => Checksum RMD160 OK for xen48/lwip-1.3.0.tar.gz => Checksum SHA512 OK for xen48/lwip-1.3.0.tar.gz => Checksum SHA1 OK for xen48/newlib-1.16.0.tar.gz => Checksum RMD160 OK for xen48/newlib-1.16.0.tar.gz => Checksum SHA512 OK for xen48/newlib-1.16.0.tar.gz => Checksum SHA1 OK for xen48/ocaml-3.11.0.tar.gz => Checksum RMD160 OK for xen48/ocaml-3.11.0.tar.gz => Checksum SHA512 OK for xen48/ocaml-3.11.0.tar.gz => Checksum SHA1 OK for xen48/pciutils-2.2.9.tar.bz2 => Checksum RMD160 OK for xen48/pciutils-2.2.9.tar.bz2 => Checksum SHA512 OK for xen48/pciutils-2.2.9.tar.bz2 => Checksum SHA1 OK for xen48/polarssl-1.1.4-gpl.tgz => Checksum RMD160 OK for xen48/polarssl-1.1.4-gpl.tgz => Checksum SHA512 OK for xen48/polarssl-1.1.4-gpl.tgz => Checksum SHA1 OK for xen48/tpm_emulator-0.7.4.tar.gz => Checksum RMD160 OK for xen48/tpm_emulator-0.7.4.tar.gz => Checksum SHA512 OK for xen48/tpm_emulator-0.7.4.tar.gz => Checksum SHA1 OK for xen48/xen-4.8.0.tar.gz => Checksum RMD160 OK for xen48/xen-4.8.0.tar.gz => Checksum SHA512 OK for xen48/xen-4.8.0.tar.gz => Checksum SHA1 OK for xen48/zlib-1.2.3.tar.gz => Checksum RMD160 OK for xen48/zlib-1.2.3.tar.gz => Checksum SHA512 OK for xen48/zlib-1.2.3.tar.gz ===> Installing dependencies for xentools48-4.8.0nb3 ========================================================================== The following variables will affect the build process of this package, xentools48-4.8.0nb3. Their current value is shown below: * CURSES_DEFAULT = curses * PYTHON_VERSION_DEFAULT = 27 * 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. ========================================================================== bash / [0-9]* pkgconf / [0-9]* dev86 / [0-9]* => Tool dependency bash-[0-9]*: found bash-4.4.012 => Tool dependency cmake>=2.8.1nb1: found cmake-3.9.3 => Tool dependency gmake>=3.81: found gmake-4.1nb3 => Tool dependency perl>=5.0: found perl-5.26.1 => Tool dependency pkgconf-[0-9]*: found pkgconf-1.3.5 => Tool dependency checkperms>=1.1: found checkperms-1.11nb1 => Build dependency dev86-[0-9]*: found dev86-0.16.21 => Build dependency pciutils>=3.0.2: found pciutils-3.5.5 => Build dependency gcc48>=4.8: found gcc48-4.8.5nb4 => Build dependency cwrappers>=20150314: found cwrappers-20170611 => Full dependency py27-curses>=0: found py27-curses-2.7.14nb4 => Full dependency python27>=2.7.1nb2: found python27-2.7.14 => Full dependency ocaml>=4.05.0: found ocaml-4.05.0 => Full dependency ocaml-findlib>=1.7.3: found ocaml-findlib-1.7.3nb1 => Full dependency glib2>=2.34.0: found glib2-2.52.3nb1 => Full dependency yajl>=1.0.9: found yajl-2.1.0 => Full dependency argp>=1.3: found argp-1.3nb1 => Full dependency libgcrypt>=1.6.0: found libgcrypt-1.8.1 => Full dependency pixman>=0.25.2: found pixman-0.34.0nb1 ===> Overriding tools for xentools48-4.8.0nb3 ===> Extracting for xentools48-4.8.0nb3 tar: Global extended headers posix ustar archive. Extracting as plain files. Following files might be in the wrong directory or have wrong attributes. ===> Patching for xentools48-4.8.0nb3 => Applying pkgsrc patches for xentools48-4.8.0nb3 => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-.._ipxe_src_core_settings.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/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 2017/03/30 09:15:10 bouyer Exp $ | |--- ../ipxe/src/core/settings.c.orig 2016-08-31 18:23:42.000000000 +0200 |+++ ../ipxe/src/core/settings.c 2017-03-24 19:44:07.000000000 +0100 -------------------------- Patching file ../ipxe/src/core/settings.c using Plan A... Hunk #1 succeeded at 304. Hunk #2 succeeded at 320. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-.._ipxe_src_net_fcels.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/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 2017/03/30 09:15:10 bouyer 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 951 (offset 5 lines). Hunk #2 succeeded at 968 (offset 5 lines). Hunk #3 succeeded at 1011 (offset 5 lines). Hunk #4 succeeded at 1027 (offset 5 lines). Hunk #5 succeeded at 1048 (offset 5 lines). Hunk #6 succeeded at 1098 (offset 5 lines). Hunk #7 succeeded at 1262 (offset 5 lines). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-.._newlib-1.16.0_newlib_libc_include_sys__types.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-.._newlib-1.16.0_newlib_libc_include_sys__types.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-.._newlib-1.16.0_newlib_libc_include_sys__types.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- ../newlib-1.16.0/newlib/libc/include/sys/_types.h.orig 2017-03-28 15:10:39.000000000 +0200 |+++ ../newlib-1.16.0/newlib/libc/include/sys/_types.h 2017-03-28 15:10:56.000000000 +0200 -------------------------- Patching file ../newlib-1.16.0/newlib/libc/include/sys/_types.h using Plan A... Hunk #1 succeeded at 52. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-._stubdom_vtpmmgr_tpm2_marshal.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-._stubdom_vtpmmgr_tpm2_marshal.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-._stubdom_vtpmmgr_tpm2_marshal.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- ./stubdom/vtpmmgr/tpm2_marshal.h.orig 2017-03-28 16:08:46.000000000 +0200 |+++ ./stubdom/vtpmmgr/tpm2_marshal.h 2017-03-28 16:08:56.000000000 +0200 -------------------------- Patching file ./stubdom/vtpmmgr/tpm2_marshal.h using Plan A... Hunk #1 succeeded at 52. Hunk #2 succeeded at 60. Hunk #3 succeeded at 125. Hunk #4 succeeded at 147. Hunk #5 succeeded at 155. Hunk #6 succeeded at 229. Hunk #7 succeeded at 240. Hunk #8 succeeded at 265. Hunk #9 succeeded at 276. Hunk #10 succeeded at 288. Hunk #11 succeeded at 318. Hunk #12 succeeded at 336. Hunk #13 succeeded at 355. Hunk #14 succeeded at 376. Hunk #15 succeeded at 397. Hunk #16 succeeded at 405. Hunk #17 succeeded at 416. Hunk #18 succeeded at 438. Hunk #19 succeeded at 462. Hunk #20 succeeded at 492. Hunk #21 succeeded at 501. Hunk #22 succeeded at 518. Hunk #23 succeeded at 535. Hunk #24 succeeded at 564. Hunk #25 succeeded at 580. Hunk #26 succeeded at 591. Hunk #27 succeeded at 602. Hunk #28 succeeded at 611. Hunk #29 succeeded at 626. Hunk #30 succeeded at 635. Hunk #31 succeeded at 647. Hunk #32 succeeded at 657. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-Config.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/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 2017/03/30 09:15:10 bouyer Exp $ | |--- Config.mk.orig 2016-12-05 13:03:27.000000000 +0100 |+++ Config.mk 2017-03-24 17:33:17.000000000 +0100 -------------------------- Patching file Config.mk using Plan A... Hunk #1 succeeded at 35. Hunk #2 succeeded at 221. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- Makefile.orig 2017-03-29 10:48:50.000000000 +0200 |+++ Makefile 2017-03-29 10:49:33.000000000 +0200 -------------------------- Patching file Makefile using Plan A... Hunk #1 succeeded at 56. Hunk #2 succeeded at 103. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-XSA-211-1 => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-XSA-211-1 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-XSA-211-1,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |From 7563ddb0bd67e7e54568e017cb7d4f7f556587fc Mon Sep 17 00:00:00 2001 |From: Gerd Hoffmann |Date: Tue, 14 Feb 2017 19:09:59 +0100 |Subject: [PATCH] cirrus/vnc: zap bitblit support from console code. | |There is a special code path (dpy_gfx_copy) to allow graphic emulation |notify user interface code about bitblit operations carryed out by |guests. It is supported by cirrus and vnc server. The intended purpose |is to optimize display scrolls and just send over the scroll op instead |of a full display update. | |This is rarely used these days though because modern guests simply don't |use the cirrus blitter any more. Any linux guest using the cirrus drm |driver doesn't. Any windows guest newer than winxp doesn't ship with a |cirrus driver any more and thus uses the cirrus as simple framebuffer. | |So this code tends to bitrot and bugs can go unnoticed for a long time. |See for example commit "3e10c3e vnc: fix qemu crash because of SIGSEGV" |which fixes a bug lingering in the code for almost a year, added by |commit "c7628bf vnc: only alloc server surface with clients connected". | |Also the vnc server will throttle the frame rate in case it figures the |network can't keep up (send buffers are full). This doesn't work with |dpy_gfx_copy, for any copy operation sent to the vnc client we have to |send all outstanding updates beforehand, otherwise the vnc client might |run the client side blit on outdated data and thereby corrupt the |display. So this dpy_gfx_copy "optimization" might even make things |worse on slow network links. | |Lets kill it once for all. | |Signed-off-by: Gerd Hoffmann |--- | hw/display/cirrus_vga.c | 12 ++----- | include/ui/console.h | 7 ---- | ui/console.c | 28 --------------- | ui/vnc.c | 96 ------------------------------------------------- | 4 files changed, 3 insertions(+), 140 deletions(-) | |diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c |index 9a4e90a..2966125 100644 |--- tools/qemu-xen/hw/display/cirrus_vga.c.orig |+++ tools/qemu-xen/hw/display/cirrus_vga.c -------------------------- Patching file tools/qemu-xen/hw/display/cirrus_vga.c using Plan A... Hunk #1 succeeded at 758 (offset -2 lines). Hunk #2 succeeded at 766 (offset -2 lines). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/include/ui/console.h b/include/ui/console.h |index 2703a3a..67927ed 100644 |--- tools/qemu-xen/include/ui/console.h.orig |+++ tools/qemu-xen/include/ui/console.h -------------------------- Patching file tools/qemu-xen/include/ui/console.h using Plan A... Hunk #1 succeeded at 189. Hunk #2 succeeded at 270. Hunk #3 succeeded at 393. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/ui/console.c b/ui/console.c |index c24bfe4..ece0c04 100644 |--- tools/qemu-xen/ui/console.c.orig |+++ tools/qemu-xen/ui/console.c -------------------------- Patching file tools/qemu-xen/ui/console.c using Plan A... Hunk #1 succeeded at 1558. Hunk #2 succeeded at 2083. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/ui/vnc.c b/ui/vnc.c |index d1087c9..b45bb2c 100644 |--- tools/qemu-xen/ui/vnc.c.orig |+++ tools/qemu-xen/ui/vnc.c -------------------------- Patching file tools/qemu-xen/ui/vnc.c using Plan A... Hunk #1 succeeded at 872. Hunk #2 succeeded at 3024. Hmm... Ignoring the trailing garbage. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-XSA-211-2 => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-XSA-211-2 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-XSA-211-2,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |From 29e67cfd46b4d06ca1bb75558e227ec34a6af35f Mon Sep 17 00:00:00 2001 |From: Ian Jackson |Date: Thu, 9 Mar 2017 11:14:55 +0000 |Subject: [PATCH] cirrus/vnc: zap drop bitblit support from console code. | |From: Gerd Hoffmann | |There is a special code path (dpy_gfx_copy) to allow graphic emulation |notify user interface code about bitblit operations carryed out by |guests. It is supported by cirrus and vnc server. The intended purpose |is to optimize display scrolls and just send over the scroll op instead |of a full display update. | |This is rarely used these days though because modern guests simply don't |use the cirrus blitter any more. Any linux guest using the cirrus drm |driver doesn't. Any windows guest newer than winxp doesn't ship with a |cirrus driver any more and thus uses the cirrus as simple framebuffer. | |So this code tends to bitrot and bugs can go unnoticed for a long time. |See for example commit "3e10c3e vnc: fix qemu crash because of SIGSEGV" |which fixes a bug lingering in the code for almost a year, added by |commit "c7628bf vnc: only alloc server surface with clients connected". | |Also the vnc server will throttle the frame rate in case it figures the |network can't keep up (send buffers are full). This doesn't work with |dpy_gfx_copy, for any copy operation sent to the vnc client we have to |send all outstanding updates beforehand, otherwise the vnc client might |run the client side blit on outdated data and thereby corrupt the |display. So this dpy_gfx_copy "optimization" might even make things |worse on slow network links. | |Lets kill it once for all. | |Signed-off-by: Gerd Hoffmann | |These changes (dropping dpy_copy and all its references and |implementations) reimplemented for qemu-xen-traditional. | |This is XSA-211. | |Signed-off-by: Ian Jackson |--- | console.c | 8 -------- | console.h | 16 ---------------- | hw/cirrus_vga.c | 15 +++++---------- | hw/vmware_vga.c | 1 + | vnc.c | 35 ----------------------------------- | 5 files changed, 6 insertions(+), 69 deletions(-) | |diff --git a/console.c b/console.c |index d4f1ad0..e61b53b 100644 |--- tools/qemu-xen-traditional/console.c.orig |+++ tools/qemu-xen-traditional/console.c -------------------------- Patching file tools/qemu-xen-traditional/console.c using Plan A... Hunk #1 succeeded at 1399. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/console.h b/console.h |index 14b42f3..8306cc4 100644 |--- tools/qemu-xen-traditional/console.h.orig |+++ tools/qemu-xen-traditional/console.h -------------------------- Patching file tools/qemu-xen-traditional/console.h using Plan A... Hunk #1 succeeded at 98. Hunk #2 succeeded at 209. Hunk #3 succeeded at 283. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/hw/cirrus_vga.c b/hw/cirrus_vga.c |index 06b4a3b..4e85b90 100644 |--- tools/qemu-xen-traditional/hw/cirrus_vga.c.orig |+++ tools/qemu-xen-traditional/hw/cirrus_vga.c -------------------------- Patching file tools/qemu-xen-traditional/hw/cirrus_vga.c using Plan A... Hunk #1 succeeded at 794 (offset 1 line). Hunk #2 succeeded at 802 (offset 1 line). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/hw/vmware_vga.c b/hw/vmware_vga.c |index d1cba28..c38e43c 100644 |--- tools/qemu-xen-traditional/hw/vmware_vga.c.orig |+++ tools/qemu-xen-traditional/hw/vmware_vga.c -------------------------- Patching file tools/qemu-xen-traditional/hw/vmware_vga.c using Plan A... Hunk #1 succeeded at 383. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/vnc.c b/vnc.c |index 61d1555..0e61197 100644 |--- tools/qemu-xen-traditional/vnc.c.orig |+++ tools/qemu-xen-traditional/vnc.c -------------------------- Patching file tools/qemu-xen-traditional/vnc.c using Plan A... Hunk #1 succeeded at 572. Hunk #2 succeeded at 1513. Hunk #3 succeeded at 2425. Hmm... Ignoring the trailing garbage. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-docs_man_xl.cfg.pod.5.in => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-docs_man_xl.cfg.pod.5.in Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-docs_man_xl.cfg.pod.5.in,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- docs/man/xl.cfg.pod.5.in.orig 2017-03-24 17:42:46.000000000 +0100 |+++ docs/man/xl.cfg.pod.5.in 2017-03-24 17:43:19.000000000 +0100 -------------------------- Patching file docs/man/xl.cfg.pod.5.in using Plan A... Hunk #1 succeeded at 4. Hunk #2 succeeded at 2040. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-docs_man_xl.conf.pod.5 => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/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 2017/03/30 09:15:10 bouyer Exp $ | |--- docs/man/xl.conf.pod.5.orig 2016-12-05 13:03:27.000000000 +0100 |+++ docs/man/xl.conf.pod.5 2017-03-24 17:37:53.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/xentools48/patches/patch-docs_man_xl.pod.1.in => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-docs_man_xl.pod.1.in Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-docs_man_xl.pod.1.in,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- docs/man/xl.pod.1.in.orig 2017-03-24 17:39:08.000000000 +0100 |+++ docs/man/xl.pod.1.in 2017-03-24 17:40:12.000000000 +0100 -------------------------- Patching file docs/man/xl.pod.1.in using Plan A... Hunk #1 succeeded at 33. Hunk #2 succeeded at 50. Hunk #3 succeeded at 175. Hunk #4 succeeded at 528. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-docs_man_xlcpupool.cfg.pod.5 => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/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 2017/03/30 09:15:10 bouyer Exp $ | |--- docs/man/xlcpupool.cfg.pod.5.orig 2017-03-24 17:41:23.000000000 +0100 |+++ docs/man/xlcpupool.cfg.pod.5 2017-03-24 17:41:50.000000000 +0100 -------------------------- Patching file docs/man/xlcpupool.cfg.pod.5 using Plan A... Hunk #1 succeeded at 4. Hunk #2 succeeded at 117. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-docs_misc_xl-disk-configuration.txt => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/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 2017/03/30 09:15:10 bouyer 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/xentools48/patches/patch-extras_mini-os_Config.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_Config.mk Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- extras/mini-os/Config.mk.orig 2017-03-27 19:37:46.000000000 +0200 |+++ extras/mini-os/Config.mk 2017-03-27 19:38:46.000000000 +0200 -------------------------- Patching file extras/mini-os/Config.mk using Plan A... Hunk #1 succeeded at 106. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_arch_x86_arch.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_arch_x86_arch.mk Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-extras_mini-os_arch_x86_arch.mk,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- extras/mini-os/arch/x86/arch.mk.orig 2017-03-27 16:41:50.000000000 +0200 |+++ extras/mini-os/arch/x86/arch.mk 2017-03-27 16:43:37.000000000 +0200 -------------------------- Patching file extras/mini-os/arch/x86/arch.mk using Plan A... Hunk #1 succeeded at 7. Hunk #2 succeeded at 17. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_include_fcntl.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_include_fcntl.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-extras_mini-os_include_fcntl.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- extras/mini-os/include/fcntl.h.orig 2017-03-28 19:38:01.000000000 +0200 |+++ extras/mini-os/include/fcntl.h 2017-03-28 19:38:12.000000000 +0200 -------------------------- Patching file extras/mini-os/include/fcntl.h using Plan A... Hunk #1 succeeded at 93. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_include_time.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_include_time.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-extras_mini-os_include_time.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- extras/mini-os/include/time.h.orig 2016-09-28 13:09:38.000000000 +0200 |+++ extras/mini-os/include/time.h 2017-03-28 20:00:33.000000000 +0200 -------------------------- Patching file extras/mini-os/include/time.h using Plan A... Hunk #1 succeeded at 48. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_lib_sys.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_lib_sys.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- extras/mini-os/lib//sys.c.orig 2017-03-28 13:14:26.000000000 +0200 |+++ extras/mini-os/lib//sys.c 2017-03-28 13:14:39.000000000 +0200 -------------------------- Patching file extras/mini-os/lib//sys.c using Plan A... Hunk #1 succeeded at 18. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_lock.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-extras_mini-os_lock.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- extras/mini-os/lock.c.orig 2017-03-28 12:14:33.000000000 +0200 |+++ extras/mini-os/lock.c 2017-03-28 12:14:43.000000000 +0200 -------------------------- Patching file extras/mini-os/lock.c using Plan A... Hunk #1 succeeded at 4. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-stubdom_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- stubdom/Makefile.orig 2016-12-05 13:03:27.000000000 +0100 |+++ stubdom/Makefile 2017-03-29 09:58:39.000000000 +0200 -------------------------- Patching file stubdom/Makefile using Plan A... Hunk #1 succeeded at 6. Hunk #2 succeeded at 22. Hunk #3 succeeded at 72. Hunk #4 succeeded at 87. Hunk #5 succeeded at 95. Hunk #6 succeeded at 111. Hunk #7 succeeded at 125. Hunk #8 succeeded at 135. Hunk #9 succeeded at 144. Hunk #10 succeeded at 165. Hunk #11 succeeded at 174. Hunk #12 succeeded at 183. Hunk #13 succeeded at 195. Hunk #14 succeeded at 214. Hunk #15 succeeded at 228. Hunk #16 succeeded at 342. Hunk #17 succeeded at 404. Hunk #18 succeeded at 442. Hunk #19 succeeded at 453. Hunk #20 succeeded at 503. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_newlib.patch => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_newlib.patch Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-stubdom_newlib.patch,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- stubdom/newlib.patch.orig 2016-12-05 13:03:27.000000000 +0100 |+++ stubdom/newlib.patch 2017-03-28 13:34:23.000000000 +0200 -------------------------- Patching file stubdom/newlib.patch using Plan A... Hunk #1 succeeded at 663. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_marshal.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_marshal.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-stubdom_vtpmmgr_marshal.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- stubdom/vtpmmgr/marshal.h.orig 2017-03-28 16:07:11.000000000 +0200 |+++ stubdom/vtpmmgr/marshal.h 2017-03-28 16:08:28.000000000 +0200 -------------------------- Patching file stubdom/vtpmmgr/marshal.h using Plan A... Hunk #1 succeeded at 47. Hunk #2 succeeded at 72. Hunk #3 succeeded at 93. Hunk #4 succeeded at 236. Hunk #5 succeeded at 256. Hunk #6 succeeded at 271. Hunk #7 succeeded at 279. Hunk #8 succeeded at 292. Hunk #9 succeeded at 325. Hunk #10 succeeded at 333. Hunk #11 succeeded at 341. Hunk #12 succeeded at 355. Hunk #13 succeeded at 366. Hunk #14 succeeded at 377. Hunk #15 succeeded at 409. Hunk #16 succeeded at 493. Hunk #17 succeeded at 511. Hunk #18 succeeded at 532. Hunk #19 succeeded at 599. Hunk #20 succeeded at 610. Hunk #21 succeeded at 622. Hunk #22 succeeded at 637. Hunk #23 succeeded at 665. Hunk #24 succeeded at 682. Hunk #25 succeeded at 699. Hunk #26 succeeded at 722. Hunk #27 succeeded at 732. Hunk #28 succeeded at 746. Hunk #29 succeeded at 758. Hunk #30 succeeded at 770. Hunk #31 succeeded at 786. Hunk #32 succeeded at 794. Hunk #33 succeeded at 817. Hunk #34 succeeded at 826. Hunk #35 succeeded at 836. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_tcg.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_tcg.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-stubdom_vtpmmgr_tcg.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- stubdom/vtpmmgr/tcg.h.orig 2017-03-28 16:00:31.000000000 +0200 |+++ stubdom/vtpmmgr/tcg.h 2017-03-28 16:01:01.000000000 +0200 -------------------------- Patching file stubdom/vtpmmgr/tcg.h using Plan A... Hunk #1 succeeded at 461. Hunk #2 succeeded at 494. Hunk #3 succeeded at 510. Hunk #4 succeeded at 528. Hunk #5 succeeded at 550. Hunk #6 succeeded at 562. Hunk #7 succeeded at 574. Hunk #8 succeeded at 594. Hunk #9 succeeded at 607. Hunk #10 succeeded at 619. Hunk #11 succeeded at 643. Hunk #12 succeeded at 660. Hunk #13 succeeded at 676. Hunk #14 succeeded at 696. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_tpmrsa.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_tpmrsa.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-stubdom_vtpmmgr_tpmrsa.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- stubdom/vtpmmgr/tpmrsa.h.orig 2017-03-28 16:12:14.000000000 +0200 |+++ stubdom/vtpmmgr/tpmrsa.h 2017-03-28 16:12:26.000000000 +0200 -------------------------- Patching file stubdom/vtpmmgr/tpmrsa.h using Plan A... Hunk #1 succeeded at 62. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_vtpm_manager.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_vtpm_manager.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-stubdom_vtpmmgr_vtpm_manager.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- stubdom/vtpmmgr/vtpm_manager.h.orig 2017-03-28 15:33:35.000000000 +0200 |+++ stubdom/vtpmmgr/vtpm_manager.h 2017-03-28 15:33:55.000000000 +0200 -------------------------- Patching file stubdom/vtpmmgr/vtpm_manager.h using Plan A... Hunk #1 succeeded at 54. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_vtpmmgr.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-stubdom_vtpmmgr_vtpmmgr.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-stubdom_vtpmmgr_vtpmmgr.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- stubdom/vtpmmgr/vtpmmgr.h.orig 2017-03-28 16:13:43.000000000 +0200 |+++ stubdom/vtpmmgr/vtpmmgr.h 2017-03-28 16:13:51.000000000 +0200 -------------------------- Patching file stubdom/vtpmmgr/vtpmmgr.h using Plan A... Hunk #1 succeeded at 101. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/Makefile.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/Makefile 2017-03-24 20:07:16.000000000 +0100 -------------------------- Patching file tools/Makefile using Plan A... Hunk #1 succeeded at 18. Hunk #2 succeeded at 34. Hunk #3 succeeded at 275. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_Rules.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_Rules.mk Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_Rules.mk,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/Rules.mk.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/Rules.mk 2017-03-24 17:48:17.000000000 +0100 -------------------------- Patching file tools/Rules.mk using Plan A... Hunk #1 succeeded at 84. Hunk #2 succeeded at 151. Hunk #3 succeeded at 162. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_configure => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_configure Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_configure,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/configure.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/configure 2017-03-24 18:13:41.000000000 +0100 -------------------------- Patching file tools/configure using Plan A... Hunk #1 succeeded at 2408. Hunk #2 succeeded at 3844. Hunk #3 succeeded at 3962. Hunk #4 succeeded at 10386. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_console_daemon_utils.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_console_daemon_utils.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_console_daemon_utils.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/console/daemon/utils.c.orig 2015-06-22 13:41:35.000000000 +0000 |+++ tools/console/daemon/utils.c -------------------------- Patching file tools/console/daemon/utils.c using Plan A... Hunk #1 succeeded at 107 (offset -6 lines). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_examples_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_examples_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_examples_Makefile,v 1.1 2017/03/30 09:15:10 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 -------------------------- Patching file tools/examples/Makefile using Plan A... Hunk #1 succeeded at 1. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_firmware_etherboot_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_firmware_etherboot_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_firmware_etherboot_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/firmware/etherboot/Makefile.orig 2015-01-12 17:53:24.000000000 +0100 |+++ tools/firmware/etherboot/Makefile 2015-01-19 13:42:54.000000000 +0100 -------------------------- Patching file tools/firmware/etherboot/Makefile using Plan A... Hunk #1 succeeded at 27. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_firmware_hvmloader_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_firmware_hvmloader_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_firmware_hvmloader_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/firmware/hvmloader/Makefile.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/firmware/hvmloader/Makefile 2017-03-24 18:14:34.000000000 +0100 -------------------------- Patching file tools/firmware/hvmloader/Makefile using Plan A... Hunk #1 succeeded at 26. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_hotplug_NetBSD_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_hotplug_NetBSD_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_hotplug_NetBSD_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/hotplug/NetBSD/Makefile.orig 2016-02-09 14:44:19.000000000 +0000 |+++ tools/hotplug/NetBSD/Makefile -------------------------- Patching file tools/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/xentools48/patches/patch-tools_hotplug_NetBSD_block => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_hotplug_NetBSD_block Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_hotplug_NetBSD_block,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/hotplug/NetBSD/block.orig 2016-02-09 14:44:19.000000000 +0000 |+++ tools/hotplug/NetBSD/block -------------------------- Patching file tools/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/xentools48/patches/patch-tools_hotplug_NetBSD_vif-bridge => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_hotplug_NetBSD_vif-bridge Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_hotplug_NetBSD_vif-bridge,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/hotplug/NetBSD/vif-bridge.orig 2015-01-12 17:53:24.000000000 +0100 |+++ tools/hotplug/NetBSD/vif-bridge 2015-01-19 13:16:37.000000000 +0100 -------------------------- Patching file tools/hotplug/NetBSD/vif-bridge using Plan A... Hunk #1 succeeded at 23. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_hotplug_NetBSD_vif-ip => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_hotplug_NetBSD_vif-ip Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_hotplug_NetBSD_vif-ip,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/hotplug/NetBSD/vif-ip.orig 2015-01-12 17:53:24.000000000 +0100 |+++ tools/hotplug/NetBSD/vif-ip 2015-01-19 13:16:37.000000000 +0100 -------------------------- Patching file tools/hotplug/NetBSD/vif-ip using Plan A... Hunk #1 succeeded at 24. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_hotplug_common_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_hotplug_common_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_hotplug_common_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/hotplug/common/Makefile.orig 2015-01-12 17:53:24.000000000 +0100 |+++ tools/hotplug/common/Makefile 2015-01-19 13:16:37.000000000 +0100 -------------------------- Patching file tools/hotplug/common/Makefile using Plan A... Hunk #1 succeeded at 23. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_include_xen-sys_NetBSD_gntdev.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_include_xen-sys_NetBSD_gntdev.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_include_xen-sys_NetBSD_gntdev.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/include/xen-sys/NetBSD/gntdev.h.orig 2015-01-19 13:16:37.000000000 +0100 |+++ tools/include/xen-sys/NetBSD/gntdev.h 2015-01-19 13:16:37.000000000 +0100 -------------------------- (Creating file tools/include/xen-sys/NetBSD/gntdev.h...) Patching file tools/include/xen-sys/NetBSD/gntdev.h using Plan A... Empty context always matches. Hunk #1 succeeded at 1. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_call_netbsd.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_call_netbsd.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_call_netbsd.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libs/call/netbsd.c.orig 2017-03-24 18:29:45.000000000 +0100 |+++ tools/libs/call/netbsd.c 2017-03-24 18:34:05.000000000 +0100 -------------------------- Patching file tools/libs/call/netbsd.c using Plan A... Hunk #1 succeeded at 19. Hunk #2 succeeded at 71. Hunk #3 succeeded at 89. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_call_private.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_call_private.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_call_private.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libs/call/private.h.orig 2017-03-28 10:42:37.000000000 +0200 |+++ tools/libs/call/private.h 2017-03-28 10:43:04.000000000 +0200 -------------------------- Patching file tools/libs/call/private.h using Plan A... Hunk #1 succeeded at 11. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_evtchn_netbsd.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_evtchn_netbsd.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_evtchn_netbsd.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libs/evtchn/netbsd.c.orig 2017-03-24 18:23:27.000000000 +0100 |+++ tools/libs/evtchn/netbsd.c 2017-03-24 18:23:40.000000000 +0100 -------------------------- Patching file tools/libs/evtchn/netbsd.c using Plan A... Hunk #1 succeeded at 124. Hunk #2 succeeded at 133. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_foreignmemory_compat.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_foreignmemory_compat.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_foreignmemory_compat.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libs/foreignmemory/compat.c.orig 2017-03-24 18:42:26.000000000 +0100 |+++ tools/libs/foreignmemory/compat.c 2017-03-24 18:41:44.000000000 +0100 -------------------------- Patching file tools/libs/foreignmemory/compat.c using Plan A... Hunk #1 succeeded at 20. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_foreignmemory_netbsd.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_foreignmemory_netbsd.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_foreignmemory_netbsd.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libs/foreignmemory/netbsd.c.orig 2017-03-24 18:51:51.000000000 +0100 |+++ tools/libs/foreignmemory/netbsd.c 2017-03-24 18:55:36.000000000 +0100 -------------------------- Patching file tools/libs/foreignmemory/netbsd.c using Plan A... Hunk #1 succeeded at 19. Hunk #2 succeeded at 68. Hunk #3 succeeded at 88. Hunk #4 succeeded at 99. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_foreignmemory_private.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libs_foreignmemory_private.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_foreignmemory_private.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libs/foreignmemory/private.h.orig 2017-03-24 18:38:28.000000000 +0100 |+++ tools/libs/foreignmemory/private.h 2017-03-24 18:52:19.000000000 +0100 -------------------------- Patching file tools/libs/foreignmemory/private.h using Plan A... Hunk #1 succeeded at 34. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libxl/Makefile.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/libxl/Makefile 2017-03-24 18:00:08.000000000 +0100 -------------------------- Patching file tools/libxl/Makefile using Plan A... Hunk #1 succeeded at 306. Hunk #2 succeeded at 320. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_libxl__create.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_libxl__create.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_libxl__create.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libxl/libxl_create.c.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/libxl/libxl_create.c 2017-03-24 18:03:19.000000000 +0100 -------------------------- Patching file tools/libxl/libxl_create.c using Plan A... Hunk #1 succeeded at 451. Hunk #2 succeeded at 488. Hunk #3 succeeded at 1161. Hunk #4 succeeded at 1171. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_libxl_event.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_libxl_event.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_libxl_event.c,v 1.1 2017/03/30 09:15:10 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 | |--- tools/libxl/libxl_event.c.orig 2016-12-20 16:01:30.000000000 +0100 |+++ tools/libxl/libxl_event.c 2016-12-20 17:28:52.000000000 +0100 -------------------------- Patching file tools/libxl/libxl_event.c using Plan A... Hunk #1 succeeded at 1255 (offset -6 lines). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_libxl_internal.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_libxl_internal.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_libxl_internal.h,v 1.1 2017/03/30 09:15:10 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. | |--- tools/libxl/libxl_internal.h.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/libxl/libxl_internal.h 2017-03-24 18:07:05.000000000 +0100 -------------------------- Patching file tools/libxl/libxl_internal.h using Plan A... Hunk #1 succeeded at 88. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_libxl_uuid.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_libxl_uuid.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_libxl_uuid.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libxl/libxl_uuid.c.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/libxl/libxl_uuid.c 2017-03-24 18:15:58.000000000 +0100 -------------------------- Patching file tools/libxl/libxl_uuid.c using Plan A... Hunk #1 succeeded at 82. Hunk #2 succeeded at 120. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_xl__cmdtable.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_xl__cmdtable.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_xl__cmdtable.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/libxl/xl_cmdtable.c.orig 2015-11-03 09:11:18.000000000 +0000 |+++ tools/libxl/xl_cmdtable.c -------------------------- Patching file tools/libxl/xl_cmdtable.c using Plan A... Hunk #1 succeeded at 498 (offset -9 lines). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_xl_cmdimpl.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_libxl_xl_cmdimpl.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_xl_cmdimpl.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |avoid shadowing a global on netbsd-6. | |--- tools/libxl/xl_cmdimpl.c.orig 2017-03-21 23:27:46.000000000 +0100 |+++ tools/libxl/xl_cmdimpl.c 2017-03-21 23:28:17.000000000 +0100 -------------------------- Patching file tools/libxl/xl_cmdimpl.c using Plan A... Hunk #1 succeeded at 480 (offset 7 lines). Hunk #2 succeeded at 510 (offset 5 lines). Hunk #3 succeeded at 9027 (offset 951 lines). Hunk #4 succeeded at 8093 (offset 5 lines). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_ocaml_common.make => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_ocaml_common.make Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_common.make,v 1.3 2017/08/23 03:02:14 maya Exp $ | |Handle ocaml-findlib 1.7.3 already appending destdir | |--- tools/ocaml/common.make.orig 2016-12-05 12:03:27.000000000 +0000 |+++ tools/ocaml/common.make 2017-08-18 16:00:39.195689939 +0100 -------------------------- Patching file tools/ocaml/common.make using Plan A... Hunk #1 succeeded at 3. Hunk #2 succeeded at 17. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_ocaml_xenstored_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_ocaml_xenstored_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_xenstored_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/ocaml/xenstored/Makefile.orig 2016-02-09 14:44:19.000000000 +0000 |+++ tools/ocaml/xenstored/Makefile -------------------------- Patching file tools/ocaml/xenstored/Makefile using Plan A... Hunk #1 succeeded at 1. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_ocaml_xenstored_define.ml => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_ocaml_xenstored_define.ml Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_xenstored_define.ml,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/ocaml/xenstored/define.ml.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/ocaml/xenstored/define.ml 2017-03-24 17:29:24.000000000 +0100 -------------------------- Patching file tools/ocaml/xenstored/define.ml using Plan A... Hunk #1 succeeded at 17. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_ocaml_xenstored_utils.ml => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_ocaml_xenstored_utils.ml Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_xenstored_utils.ml,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/ocaml/xenstored/utils.ml.orig 2016-12-05 13:03:27.000000000 +0100 |+++ tools/ocaml/xenstored/utils.ml 2017-03-24 17:31:22.000000000 +0100 -------------------------- Patching file tools/ocaml/xenstored/utils.ml using Plan A... Hunk #1 succeeded at 87. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_pygrub_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_pygrub_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_pygrub_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/pygrub/Makefile.orig 2016-02-09 14:44:19.000000000 +0000 |+++ tools/pygrub/Makefile -------------------------- Patching file tools/pygrub/Makefile using Plan A... Hunk #1 succeeded at 18 (offset 1 line). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_Makefile,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/Makefile.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/Makefile 2015-01-19 14:16:12.000000000 +0100 -------------------------- Patching file tools/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/xentools48/patches/patch-tools_qemu-xen-traditional_block-raw-posix.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_block-raw-posix.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_block-raw-posix.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |- if given a block device, use the character device instead. | |--- tools/qemu-xen-traditional/block-raw-posix.c.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/block-raw-posix.c 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/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/xentools48/patches/patch-tools_qemu-xen-traditional_configure => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_configure Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_configure,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/configure.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/configure 2015-01-20 22:58:07.000000000 +0100 -------------------------- Patching file tools/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/xentools48/patches/patch-tools_qemu-xen-traditional_hw_e1000.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_e1000.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_e1000.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |From sysutils/xentools33/patches/patch-ak. | |qemu-0.13.x will include this fix: |http://git.qemu.org/qemu.git/commit/?id=9651ac55e5de0e1534d898316cc851af6ffc4334 | |--- tools/qemu-xen-traditional/hw/e1000.c.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/e1000.c 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/e1000.c using Plan A... Hunk #1 succeeded at 265. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_ide.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_ide.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_ide.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/ide.c.orig 2014-01-09 13:44:42.000000000 +0100 |+++ tools/qemu-xen-traditional/hw/ide.c 2015-06-11 16:15:49.000000000 +0200 -------------------------- Patching file tools/qemu-xen-traditional/hw/ide.c using Plan A... Hunk #1 succeeded at 757. Hunk #2 succeeded at 817. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pass-through.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pass-through.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_pass-through.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/pass-through.c.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/pass-through.c 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/pass-through.c using Plan A... Hunk #1 succeeded at 84. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pass-through.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pass-through.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_pass-through.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/pass-through.h.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/pass-through.h 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/pass-through.h using Plan A... Hunk #1 succeeded at 20. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_piix4acpi.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_piix4acpi.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_piix4acpi.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/piix4acpi.c.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/piix4acpi.c 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/piix4acpi.c using Plan A... Hunk #1 succeeded at 41. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pt-graphics.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pt-graphics.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_pt-graphics.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/pt-graphics.c.orig 2015-01-19 16:14:46.000000000 +0100 |+++ tools/qemu-xen-traditional/hw/pt-graphics.c 2015-01-19 16:14:51.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/pt-graphics.c using Plan A... Hunk #1 succeeded at 4. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pt-msi.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pt-msi.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_pt-msi.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/pt-msi.c.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/pt-msi.c 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/pt-msi.c using Plan A... Hunk #1 succeeded at 22. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pt-msi.h => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_hw_pt-msi.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_pt-msi.h,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/pt-msi.h.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/pt-msi.h 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/pt-msi.h using Plan A... Hunk #1 succeeded at 1. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_i386-dm_hookstarget.mak => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_i386-dm_hookstarget.mak Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_i386-dm_hookstarget.mak,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen-traditional/i386-dm/hookstarget.mak.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/i386-dm/hookstarget.mak 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/i386-dm/hookstarget.mak using Plan A... Hunk #1 succeeded at 2. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_net.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_net.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_net.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ |--- tools/qemu-xen-traditional/net.c.orig 2016-11-29 17:36:38.000000000 +0100 |+++ tools/qemu-xen-traditional/net.c 2017-03-29 18:16:54.000000000 +0200 -------------------------- Patching file tools/qemu-xen-traditional/net.c using Plan A... Hunk #1 succeeded at 990. Hunk #2 succeeded at 1029. Hunk #3 succeeded at 1050. Hunk #4 succeeded at 1969. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_xen-hooks.mak => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen-traditional_xen-hooks.mak Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_xen-hooks.mak,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |enable PCI passthrough when pciutils is present | |--- tools/qemu-xen-traditional/xen-hooks.mak.orig 2016-11-29 17:36:38.000000000 +0100 |+++ tools/qemu-xen-traditional/xen-hooks.mak 2017-03-24 20:09:07.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/xen-hooks.mak using Plan A... Hunk #1 succeeded at 25. Hunk #2 succeeded at 68. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen_audio_audio.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen_audio_audio.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen_audio_audio.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen/audio/audio.c.orig 2016-11-24 13:24:26.000000000 +0100 |+++ tools/qemu-xen/audio/audio.c 2017-03-24 18:11:17.000000000 +0100 -------------------------- Patching file tools/qemu-xen/audio/audio.c using Plan A... Hunk #1 succeeded at 1156. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen_configure => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen_configure Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen_configure,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |-lrt is needed for shm_open() | |--- tools/qemu-xen/configure.orig 2017-03-26 22:27:41.000000000 +0200 |+++ tools/qemu-xen/configure 2017-03-26 22:27:46.000000000 +0200 -------------------------- Patching file tools/qemu-xen/configure using Plan A... Hunk #1 succeeded at 594. done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen_qemu-doc.texi => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen_qemu-doc.texi Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen_qemu-doc.texi,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |Avoid encoding issues in pod2man. | |--- tools/qemu-xen/qemu-doc.texi.orig 2014-12-02 11:41:02.000000000 +0100 |+++ tools/qemu-xen/qemu-doc.texi 2015-01-19 14:24:23.000000000 +0100 -------------------------- Patching file tools/qemu-xen/qemu-doc.texi using Plan A... Hunk #1 succeeded at 223 (offset 3 lines). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen_xen-hvm.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_qemu-xen_xen-hvm.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen_xen-hvm.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/qemu-xen/xen-hvm.c.orig 2016-01-06 16:42:43.000000000 +0000 |+++ tools/qemu-xen/xen-hvm.c -------------------------- Patching file tools/qemu-xen/xen-hvm.c using Plan A... Hunk #1 succeeded at 605 (offset -7 lines). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_xenpaging_xenpaging.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_xenpaging_xenpaging.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_xenpaging_xenpaging.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/xenpaging/xenpaging.c.orig 2016-06-20 12:08:22.000000000 +0000 |+++ tools/xenpaging/xenpaging.c -------------------------- Patching file tools/xenpaging/xenpaging.c using Plan A... Hunk #1 succeeded at 181 (offset -1 lines). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_xenstore_xc.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_xenstore_xc.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_xenstore_xc.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/xenstore/xs.c.orig 2015-01-19 15:40:00.000000000 +0100 |+++ tools/xenstore/xs.c 2015-01-19 15:46:56.000000000 +0100 -------------------------- Patching file tools/xenstore/xs.c using Plan A... Hunk #1 succeeded at 724 (offset -1 lines). done => Verifying /data/pkgsrc/sysutils/xentools48/patches/patch-tools_xentrace_xentrace.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xentools48/patches/patch-tools_xentrace_xentrace.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_xentrace_xentrace.c,v 1.1 2017/03/30 09:15:10 bouyer Exp $ | |--- tools/xentrace/xentrace.c.orig 2016-02-09 14:44:19.000000000 +0000 |+++ tools/xentrace/xentrace.c -------------------------- Patching file tools/xentrace/xentrace.c using Plan A... Hunk #1 succeeded at 947 (offset 2 lines). done ===> Creating toolchain wrappers for xentools48-4.8.0nb3 ===> Configuring for xentools48-4.8.0nb3 => 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 INFO: [subst.mk:perlpath] Nothing changed in ./../ipxe/src/util/parserom.pl. => Substituting "pathsvar" in tools/Makefile tools/hotplug/Linux/init.d/sysconfig.xendomains INFO: [subst.mk:pathsvar] Nothing changed in ./tools/Makefile. WARNING: [subst.mk:pathsvar] Ignoring non-existent file "./tools/hotplug/Linux/init.d/sysconfig.xendomains". => Substituting "conf" in tools/ocaml/xenstored/define.ml tools/libxl/xl_cmdtable.c docs/misc/xl-disk-configuration.txt INFO: [subst.mk:conf] Nothing changed in ./tools/ocaml/xenstored/define.ml. => Substituting "procdev" in tools/ocaml/xenstored/define.ml => Substituting "proc" in tools/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 tools/misc/xen-bugtool tools/misc/xen-ringwatch tools/misc/xencons tools/misc/xenpvnetboot tools/misc/xensymoops tools/python/scripts/convert-legacy-stream tools/python/scripts/verify-stream-v2 tools/xenmon/xenmon.py. => Replacing bash interpreter in stubdom/stubdom-dm. => Checking for portability problems in extracted files checking build system type... x86_64--netbsd checking host system type... x86_64--netbsd Will build the following subsystems: xen tools stubdom docs configure: creating ./config.status config.status: creating config/Toplevel.mk config.status: creating config/Paths.mk === configuring in tools (/data/scratch/sysutils/xentools48/work/xen-4.8.0/tools) configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr/pkg' '--disable-seabios' '--sysconfdir=/usr/pkg/etc' '--build=x86_64--netbsd' '--host=x86_64--netbsd' '--mandir=/usr/pkg/man' 'build_alias=x86_64--netbsd' 'host_alias=x86_64--netbsd' --cache-file=/dev/null --srcdir=. 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 as86... /usr/pkg/bin/as86 checking for ld86... /usr/pkg/bin/ld86 checking for bcc... /usr/pkg/bin/bcc checking for lzma_version_number in -llzma... yes 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.05.0 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/xentools48/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 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/xentools48/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 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... yes 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 and COLO. Please install libnl3 libraries (including libnl3-route), 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/sysconfig.xendomains 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/launch-xenstore 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 ocaml/xenstored/oxenstored.conf config.status: creating config.h === configuring in stubdom (/data/scratch/sysutils/xentools48/work/xen-4.8.0/stubdom) configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr/pkg' '--disable-seabios' '--sysconfdir=/usr/pkg/etc' '--build=x86_64--netbsd' '--host=x86_64--netbsd' '--mandir=/usr/pkg/man' 'build_alias=x86_64--netbsd' 'host_alias=x86_64--netbsd' --cache-file=/dev/null --srcdir=. checking build system type... x86_64--netbsd checking host system type... x86_64--netbsd xyy checking for wget... no checking for ftp... /data/scratch/sysutils/xentools48/work/.tools/bin/ftp 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 whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c -o pbulkXXX -g users checking for cmake... /data/scratch/sysutils/xentools48/work/.tools/bin/cmake Will build the following stub domains: pv-grub xenstore-stubdom vtpm-stubdom vtpmmgr-stubdom ioemu-stubdom configure: creating ./config.status config.status: creating ../config/Stubdom.mk === configuring in docs (/data/scratch/sysutils/xentools48/work/xen-4.8.0/docs) configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr/pkg' '--disable-seabios' '--sysconfdir=/usr/pkg/etc' '--build=x86_64--netbsd' '--host=x86_64--netbsd' '--mandir=/usr/pkg/man' 'build_alias=x86_64--netbsd' 'host_alias=x86_64--netbsd' --cache-file=/dev/null --srcdir=. checking for fig2dev... no configure: WARNING: fig2dev is not available so some documentation won't be built checking for pod2man... /data/scratch/sysutils/xentools48/work/.tools/bin/pod2man checking for pod2html... /usr/pkg/bin/pod2html checking for pod2text... /usr/pkg/bin/pod2text checking for pandoc... no configure: WARNING: pandoc is not available so some documentation won't be built checking for markdown... no checking for markdown_py... no configure: WARNING: markdown is not available so some documentation won't be built checking for perl... /usr/pkg/bin/perl configure: creating ./config.status config.status: creating ../config/Docs.mk config.status: creating man/xl.cfg.pod.5 config.status: creating man/xl.pod.1