=> 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 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.5.5.tar.gz
=> Checksum RMD160 OK for xen-4.5.5.tar.gz
=> Checksum SHA512 OK for xen-4.5.5.tar.gz
===> Installing dependencies for xentools45-4.5.5nb10
==========================================================================
The following variables will affect the build process of this package,
xentools45-4.5.5nb10.  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.
==========================================================================
=> Tool dependency glib2-tools-[0-9]*: found glib2-tools-2.56.1
=> Tool dependency bash-[0-9]*: found bash-4.4.019
=> Tool dependency gmake>=3.81: found gmake-4.1nb4
=> Tool dependency perl>=5.0: found perl-5.26.2
=> Tool dependency pkgconf-[0-9]*: found pkgconf-1.4.1nb1
=> 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.5.6
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency py27-curses>=0: found py27-curses-2.7.15nb5
=> Full dependency python27>=2.7.1nb2: found python27-2.7.15nb1
=> Full dependency ocaml>=4.06.1: found ocaml-4.06.1
=> Full dependency ocaml-findlib>=1.8.0nb1: found ocaml-findlib-1.8.0nb1
=> Full dependency glib2>=2.34.0: found glib2-2.56.1nb1
=> Full dependency yajl>=1.0.9: found yajl-2.1.0
=> Full dependency pixman>=0.25.2: found pixman-0.34.0nb1
===> Overriding tools for xentools45-4.5.5nb10
===> Extracting for xentools45-4.5.5nb10
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 xentools45-4.5.5nb10
=> Applying pkgsrc patches for xentools45-4.5.5nb10
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-.._.._ipxe_src_core_settings.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/25 13:14:46 joerg 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/xentools45/patches/patch-.._.._ipxe_src_interface_efi_efi_snp.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/29 21:33:47 joerg 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/xentools45/patches/patch-.._.._ipxe_src_net_fcels.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/29 21:33:47 joerg 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/xentools45/patches/patch-.._.._ipxe_src_net_tls.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/29 21:33:47 joerg 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/xentools45/patches/patch-.._Config.mk
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-.._docs_man_xl.cfg.pod.5
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer Exp $
|
|--- ../docs/man/xl.cfg.pod.5.orig	2015-01-12 17:53:24.000000000 +0100
|+++ ../docs/man/xl.cfg.pod.5	2015-01-19 15:32:47.000000000 +0100
--------------------------
Patching file ../docs/man/xl.cfg.pod.5 using Plan A...
Hunk #1 succeeded at 4.
Hunk #2 succeeded at 1606 (offset 2 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-.._docs_man_xl.conf.pod.5
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-.._docs_man_xl.pod.1
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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 168.
Hunk #4 succeeded at 463.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-.._docs_man_xlcpupool.cfg.pod.5
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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 101.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-.._docs_misc_xl-disk-configuration.txt
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2016/04/04 14:35:13 bad 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/xentools45/patches/patch-Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-Makefile,v 1.2 2015/12/31 13:27:10 jnemeth Exp $
|
|--- Makefile.orig	2015-06-22 13:41:35.000000000 +0000
|+++ Makefile
--------------------------
Patching file Makefile using Plan A...
Hunk #1 succeeded at 18.
Hunk #2 succeeded at 33.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-Rules.mk
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/29 21:33:47 joerg Exp $
|
|--- Rules.mk.orig	2015-01-12 16:53:24.000000000 +0000
|+++ Rules.mk
--------------------------
Patching file Rules.mk using Plan A...
Hunk #1 succeeded at 36.
Hunk #2 succeeded at 68.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-184
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-184
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|patches for XSA-184 from upstream:
|
|From 17d8c4e47dfb41cb6778520ff2eab7a11fe12dfd Mon Sep 17 00:00:00 2001
|From: P J P <ppandit@redhat.com>
|Date: Tue, 26 Jul 2016 15:31:59 +0100
|Subject: [PATCH] virtio: error out if guest exceeds virtqueue size
|
|A broken or malicious guest can submit more requests than the virtqueue
|size permits.
|
|The guest can submit requests without bothering to wait for completion
|and is therefore not bound by virtqueue size.  This requires reusing
|vring descriptors in more than one request, which is incorrect but
|possible.  Processing a request allocates a VirtQueueElement and
|therefore causes unbounded memory allocation controlled by the guest.
|
|Exit with an error if the guest provides more requests than the
|virtqueue size permits.  This bounds memory allocation and makes the
|buggy guest visible to the user.
|
|Reported-by: Zhenhao Hong <zhenhaohong@gmail.com>
|Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
|---
| hw/virtio.c | 5 +++++
| 1 file changed, 5 insertions(+)
|
|diff --git a/hw/virtio.c b/hw/virtio.c
|index c26feff..42897bf 100644
|--- qemu-xen-traditional/hw/virtio.c.orig	2016-01-04 15:36:03.000000000 +0000
|+++ qemu-xen-traditional/hw/virtio.c	2016-09-11 11:01:37.000000000 +0000
--------------------------
Patching file qemu-xen-traditional/hw/virtio.c using Plan A...
Hunk #1 succeeded at 421.
Hmm...  Ignoring the trailing garbage.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-197-1
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-197-1
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA-197-1,v 1.1 2016/11/22 20:57:11 bouyer Exp $
|
|From: Jan Beulich <jbeulich@suse.com>
|Subject: xen: fix ioreq handling
|
|Avoid double fetches and bounds check size to avoid overflowing
|internal variables.
|
|This is XSA-197.
|
|Reported-by: yanghongke <yanghongke@huawei.com>
|Signed-off-by: Jan Beulich <jbeulich@suse.com>
|Reviewed-by: Ian Jackson <ian.jackson@eu.citrix.com>
|
|--- qemu-xen-traditional/i386-dm/helper2.c.orig
|+++ qemu-xen-traditional/i386-dm/helper2.c
--------------------------
Patching file qemu-xen-traditional/i386-dm/helper2.c using Plan A...
Hunk #1 succeeded at 374.
Hunk #2 succeeded at 408.
Hunk #3 succeeded at 516.
Hunk #4 succeeded at 555.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-197-2
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-197-2
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA-197-2,v 1.1 2016/11/22 20:57:11 bouyer Exp $
|
|From: Jan Beulich <jbeulich@suse.com>
|Subject: xen: fix ioreq handling
|
|Avoid double fetches and bounds check size to avoid overflowing
|internal variables.
|
|This is XSA-197.
|
|Reported-by: yanghongke <yanghongke@huawei.com>
|Signed-off-by: Jan Beulich <jbeulich@suse.com>
|Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
|
|--- qemu-xen/xen-hvm.c.orig
|+++ qemu-xen/xen-hvm.c
--------------------------
Patching file qemu-xen/xen-hvm.c using Plan A...
Hunk #1 succeeded at 722.
Hunk #2 succeeded at 755.
Hunk #3 succeeded at 834.
Hunk #4 succeeded at 872.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-198
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-198
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA-198,v 1.1 2016/11/22 20:57:11 bouyer Exp $
|
|From 71a389ae940bc52bf897a6e5becd73fd8ede94c5 Mon Sep 17 00:00:00 2001
|From: Ian Jackson <ian.jackson@eu.citrix.com>
|Date: Thu, 3 Nov 2016 16:37:40 +0000
|Subject: [PATCH] pygrub: Properly quote results, when returning them to the
| caller:
|
|* When the caller wants sexpr output, use `repr()'
|  This is what Xend expects.
|
|  The returned S-expressions are now escaped and quoted by Python,
|  generally using '...'.  Previously kernel and ramdisk were unquoted
|  and args was quoted with "..." but without proper escaping.  This
|  change may break toolstacks which do not properly dequote the
|  returned S-expressions.
|
|* When the caller wants "simple" output, crash if the delimiter is
|  contained in the returned value.
|
|  With --output-format=simple it does not seem like this could ever
|  happen, because the bootloader config parsers all take line-based
|  input from the various bootloader config files.
|
|  With --output-format=simple0, this can happen if the bootloader
|  config file contains nul bytes.
|
|This is XSA-198.
|
|Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
|Tested-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
|Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
|---
| tools/pygrub/src/pygrub | 9 ++++++---
| 1 file changed, 6 insertions(+), 3 deletions(-)
|
|diff --git a/tools/pygrub/src/pygrub b/tools/pygrub/src/pygrub
|index 40f9584..dd0c8f7 100755
|--- pygrub/src/pygrub.orig
|+++ pygrub/src/pygrub
--------------------------
Patching file pygrub/src/pygrub using Plan A...
Hunk #1 succeeded at 722 (offset 1 line).
Hmm...  Ignoring the trailing garbage.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-199
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-199
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA-199,v 1.1 2016/12/20 10:22:29 bouyer Exp $
|
|From b73bd1edc05d1bad5c018228146930d79315a5da Mon Sep 17 00:00:00 2001
|From: Ian Jackson <ian.jackson@eu.citrix.com>
|Date: Mon, 14 Nov 2016 17:19:46 +0000
|Subject: [PATCH] qemu: ioport_read, ioport_write: be defensive about 32-bit
| addresses
|
|On x86, ioport addresses are 16-bit.  That these functions take 32-bit
|arguments is a mistake.  Changing the argument type to 16-bit will
|discard the top bits of any erroneous values from elsewhere in qemu.
|
|Also, check just before use that the value is in range.  (This turns
|an ill-advised change to MAX_IOPORTS into a possible guest crash
|rather than a privilege escalation vulnerability.)
|
|And, in the Xen ioreq processor, clamp incoming ioport addresses to
|16-bit values.  Xen will never write >16-bit values but the guest may
|have access to the ioreq ring.  We want to defend the rest of the qemu
|code from wrong values.
|
|This is XSA-199.
|
|Reported-by: yanghongke <yanghongke@huawei.com>
|Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
|---
| i386-dm/helper2.c | 2 ++
| vl.c              | 9 +++++++--
| 2 files changed, 9 insertions(+), 2 deletions(-)
|
|diff --git a/i386-dm/helper2.c b/i386-dm/helper2.c
|index 2706f2e..5d276bb 100644
|--- qemu-xen-traditional/i386-dm/helper2.c.orig
|+++ qemu-xen-traditional/i386-dm/helper2.c
--------------------------
Patching file qemu-xen-traditional/i386-dm/helper2.c using Plan A...
Hunk #1 succeeded at 374 (offset -1 lines).
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/vl.c b/vl.c
|index f9c4d7e..c3c5d63 100644
|--- qemu-xen-traditional/vl.c.orig
|+++ qemu-xen-traditional/vl.c
--------------------------
Patching file qemu-xen-traditional/vl.c using Plan A...
Hunk #1 succeeded at 52.
Hunk #2 succeeded at 291.
Hmm...  Ignoring the trailing garbage.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-208-1
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-208-1
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA-208-1,v 1.1 2017/03/20 18:09:21 bouyer Exp $
|
|From 8f63265efeb6f92e63f7e749cb26131b68b20df7 Mon Sep 17 00:00:00 2001
|From: Li Qiang <liqiang6-s@360.cn>
|Date: Mon, 13 Feb 2017 15:22:15 +0000
|Subject: [PATCH] cirrus: fix oob access issue (CVE-2017-2615)
|
|When doing bitblt copy in backward mode, we should minus the
|blt width first just like the adding in the forward mode. This
|can avoid the oob access of the front of vga's vram.
|
|This is XSA-208.
|
|upstream-commit-id: 62d4c6bd5263bb8413a06c80144fc678df6dfb64
|
|Signed-off-by: Li Qiang <liqiang6-s@360.cn>
|
|{ kraxel: with backward blits (negative pitch) addr is the topmost
|          address, so check it as-is against vram size ]
|
|Cc: qemu-stable@nongnu.org
|Cc: P J P <ppandit@redhat.com>
|Cc: Laszlo Ersek <lersek@redhat.com>
|Cc: Paolo Bonzini <pbonzini@redhat.com>
|Cc: Wolfgang Bumiller <w.bumiller@proxmox.com>
|Fixes: d3532a0db02296e687711b8cdc7791924efccea0 (CVE-2014-8106)
|Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|Message-id: 1485938101-26602-1-git-send-email-kraxel@redhat.com
|Reviewed-by: Laszlo Ersek <lersek@redhat.com>
|Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
|---
| hw/display/cirrus_vga.c | 7 +++----
| 1 file changed, 3 insertions(+), 4 deletions(-)
|
|diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c
|index 5198037..7bf3707 100644
|--- qemu-xen/hw/display/cirrus_vga.c.orig
|+++ qemu-xen/hw/display/cirrus_vga.c
--------------------------
Patching file qemu-xen/hw/display/cirrus_vga.c using Plan A...
Hunk #1 succeeded at 269 (offset -3 lines).
Hmm...  Ignoring the trailing garbage.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-208-2
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-208-2
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA-208-2,v 1.1 2017/03/20 18:09:21 bouyer Exp $
|
|From 8f63265efeb6f92e63f7e749cb26131b68b20df7 Mon Sep 17 00:00:00 2001
|From: Li Qiang <liqiang6-s@360.cn>
|Date: Mon, 13 Feb 2017 15:22:15 +0000
|Subject: [PATCH] cirrus: fix oob access issue (CVE-2017-2615)
|
|When doing bitblt copy in backward mode, we should minus the
|blt width first just like the adding in the forward mode. This
|can avoid the oob access of the front of vga's vram.
|
|This is XSA-208.
|
|upstream-commit-id: 62d4c6bd5263bb8413a06c80144fc678df6dfb64
|
|Signed-off-by: Li Qiang <liqiang6-s@360.cn>
|
|{ kraxel: with backward blits (negative pitch) addr is the topmost
|          address, so check it as-is against vram size ]
|
|[ This is CVE-2017-2615 / XSA-208  - Ian Jackson ]
|
|Cc: qemu-stable@nongnu.org
|Cc: P J P <ppandit@redhat.com>
|Cc: Laszlo Ersek <lersek@redhat.com>
|Cc: Paolo Bonzini <pbonzini@redhat.com>
|Cc: Wolfgang Bumiller <w.bumiller@proxmox.com>
|Fixes: d3532a0db02296e687711b8cdc7791924efccea0 (CVE-2014-8106)
|Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|Message-id: 1485938101-26602-1-git-send-email-kraxel@redhat.com
|Reviewed-by: Laszlo Ersek <lersek@redhat.com>
|Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
|Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
|---
| hw/cirrus_vga.c | 7 +++----
| 1 file changed, 3 insertions(+), 4 deletions(-)
|
|diff --git a/hw/cirrus_vga.c b/hw/cirrus_vga.c
|index e6c3893..364e22d 100644
|--- qemu-xen-traditional/hw/cirrus_vga.c.orig
|+++ qemu-xen-traditional/hw/cirrus_vga.c
--------------------------
Patching file qemu-xen-traditional/hw/cirrus_vga.c using Plan A...
Hunk #1 succeeded at 308.
Hmm...  Ignoring the trailing garbage.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-209-1
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-209-1
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA-209-1,v 1.1 2017/03/20 18:09:21 bouyer Exp $
|
|From 8f63265efeb6f92e63f7e749cb26131b68b20df7 Mon Sep 17 00:00:00 2001
|From: Li Qiang <liqiang6-s@360.cn>
|Date: Mon, 13 Feb 2017 15:22:15 +0000
|Subject: [PATCH] cirrus: fix oob access issue (CVE-2017-2615)
|
|When doing bitblt copy in backward mode, we should minus the
|blt width first just like the adding in the forward mode. This
|can avoid the oob access of the front of vga's vram.
|
|This is XSA-208.
|
|upstream-commit-id: 62d4c6bd5263bb8413a06c80144fc678df6dfb64
|
|Signed-off-by: Li Qiang <liqiang6-s@360.cn>
|
|{ kraxel: with backward blits (negative pitch) addr is the topmost
|          address, so check it as-is against vram size ]
|
|Cc: qemu-stable@nongnu.org
|From 52b7f43c8fa185ab856bcaacda7abc9a6fc07f84 Mon Sep 17 00:00:00 2001
|From: Bruce Rogers <brogers@suse.com>
|Date: Tue, 21 Feb 2017 10:54:38 -0800
|Subject: [PATCH 1/2] display: cirrus: ignore source pitch value as needed in
| blit_is_unsafe
|
|Commit 4299b90 added a check which is too broad, given that the source
|pitch value is not required to be initialized for solid fill operations.
|This patch refines the blit_is_unsafe() check to ignore source pitch in
|that case. After applying the above commit as a security patch, we
|noticed the SLES 11 SP4 guest gui failed to initialize properly.
|
|Signed-off-by: Bruce Rogers <brogers@suse.com>
|Message-id: 20170109203520.5619-1-brogers@suse.com
|Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|---
| hw/display/cirrus_vga.c | 11 +++++++----
| 1 file changed, 7 insertions(+), 4 deletions(-)
|
|diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c
|index 7bf3707..34a6900 100644
|--- qemu-xen/hw/display/cirrus_vga.c.orig
|+++ qemu-xen/hw/display/cirrus_vga.c
--------------------------
Patching file qemu-xen/hw/display/cirrus_vga.c using Plan A...
Hunk #1 succeeded at 285 (offset -3 lines).
Hunk #2 succeeded at 299 (offset -3 lines).
Hunk #3 succeeded at 667 (offset -3 lines).
Hunk #4 succeeded at 685 (offset -3 lines).
Hunk #5 succeeded at 784 (offset -3 lines).
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|-- 
|2.1.4
|
|From 15268f91fbe75b38a851c458aef74e693d646ea5 Mon Sep 17 00:00:00 2001
|From: Gerd Hoffmann <kraxel@redhat.com>
|Date: Tue, 21 Feb 2017 10:54:59 -0800
|Subject: [PATCH 2/2] cirrus: add blit_is_unsafe call to
| cirrus_bitblt_cputovideo
|
|CIRRUS_BLTMODE_MEMSYSSRC blits do NOT check blit destination
|and blit width, at all.  Oops.  Fix it.
|
|Security impact: high.
|
|The missing blit destination check allows to write to host memory.
|Basically same as CVE-2014-8106 for the other blit variants.
|
|The missing blit width check allows to overflow cirrus_bltbuf,
|with the attractive target cirrus_srcptr (current cirrus_bltbuf write
|position) being located right after cirrus_bltbuf in CirrusVGAState.
|
|Due to cirrus emulation writing cirrus_bltbuf bytewise the attacker
|hasn't full control over cirrus_srcptr though, only one byte can be
|changed.  Once the first byte has been modified further writes land
|elsewhere.
|
|[ This is CVE-2017-2620 / XSA-209  - Ian Jackson ]
|
|Reported-by: Gerd Hoffmann <ghoffman@redhat.com>
|Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|---
| hw/display/cirrus_vga.c | 8 ++++++++
| 1 file changed, 8 insertions(+)
|
|diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c
|index 34a6900..5901250 100644
|--- qemu-xen/hw/display/cirrus_vga.c.orig
|+++ qemu-xen/hw/display/cirrus_vga.c
--------------------------
Patching file qemu-xen/hw/display/cirrus_vga.c using Plan A...
Hunk #1 succeeded at 862 (offset -3 lines).
Hunk #2 succeeded at 891 (offset -3 lines).
Hmm...  Ignoring the trailing garbage.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-209-2
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-209-2
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-XSA-209-2,v 1.1 2017/03/20 18:09:21 bouyer Exp $
|
|From: Gerd Hoffmann <kraxel@redhat.com>
|Subject: [PATCH 3/3] cirrus: add blit_is_unsafe call to cirrus_bitblt_cputovideo
|
|CIRRUS_BLTMODE_MEMSYSSRC blits do NOT check blit destination
|and blit width, at all.  Oops.  Fix it.
|
|Security impact: high.
|
|The missing blit destination check allows to write to host memory.
|Basically same as CVE-2014-8106 for the other blit variants.
|
|The missing blit width check allows to overflow cirrus_bltbuf,
|with the attractive target cirrus_srcptr (current cirrus_bltbuf write
|position) being located right after cirrus_bltbuf in CirrusVGAState.
|
|Due to cirrus emulation writing cirrus_bltbuf bytewise the attacker
|hasn't full control over cirrus_srcptr though, only one byte can be
|changed.  Once the first byte has been modified further writes land
|elsewhere.
|
|[ This is CVE-2017-2620 / XSA-209  - Ian Jackson ]
|
|Fixed compilation by removing extra parameter to blit_is_unsafe. -iwj
|
|Reported-by: Gerd Hoffmann <ghoffman@redhat.com>
|Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
|---
|diff --git a/hw/cirrus_vga.c b/hw/cirrus_vga.c
|index e6c3893..45facb6 100644
|--- qemu-xen-traditional/hw/cirrus_vga.c.orig
|+++ qemu-xen-traditional/hw/cirrus_vga.c
--------------------------
Patching file qemu-xen-traditional/hw/cirrus_vga.c using Plan A...
Hunk #1 succeeded at 899 (offset -1 lines).
Hunk #2 succeeded at 928 (offset -1 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-211-1
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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/20 18:09:21 bouyer Exp $
|
|From c85f4df08b17f5808eda2b8afea1e4db7016cdc8 Mon Sep 17 00:00:00 2001
|From: Gerd Hoffmann <kraxel@redhat.com>
|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 <kraxel@redhat.com>
|---
| hw/display/cirrus_vga.c | 12 ++-----
| include/ui/console.h    |  8 -----
| ui/console.c            | 28 ---------------
| ui/vnc.c                | 91 -------------------------------------------------
| 4 files changed, 3 insertions(+), 136 deletions(-)
|
|diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c
|index d643a0d..2e38c86 100644
|--- qemu-xen/hw/display/cirrus_vga.c.orig
|+++ qemu-xen/hw/display/cirrus_vga.c
--------------------------
Patching file qemu-xen/hw/display/cirrus_vga.c using Plan A...
Hunk #1 succeeded at 755 (offset -1 lines).
Hunk #2 succeeded at 763 (offset -1 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 22ef8ca..331c07a 100644
|--- qemu-xen/include/ui/console.h.orig
|+++ qemu-xen/include/ui/console.h
--------------------------
Patching file qemu-xen/include/ui/console.h using Plan A...
Hunk #1 succeeded at 158.
Hunk #2 succeeded at 213 (offset -6 lines).
Hunk #3 succeeded at 302 (offset -7 lines).
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 258af5d..cc1aa20 100644
|--- qemu-xen/ui/console.c.orig
|+++ qemu-xen/ui/console.c
--------------------------
Patching file qemu-xen/ui/console.c using Plan A...
Hunk #1 succeeded at 1418 (offset -32 lines).
Hunk #2 succeeded at 1868 (offset -79 lines).
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 76caa897..c3c2625 100644
|--- qemu-xen/ui/vnc.c.orig
|+++ qemu-xen/ui/vnc.c
--------------------------
Patching file qemu-xen/ui/vnc.c using Plan A...
Hunk #1 succeeded at 730 (offset -3 lines).
Hunk #2 succeeded at 2838 (offset -21 lines).
Hmm...  Ignoring the trailing garbage.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-XSA-211-2
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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/20 18:09:21 bouyer Exp $
|
|From dc4eee43ac608337ae96a174e0a5c1278168bd56 Mon Sep 17 00:00:00 2001
|From: Ian Jackson <ian.jackson@eu.citrix.com>
|Date: Thu, 9 Mar 2017 11:14:55 +0000
|Subject: [PATCH] cirrus/vnc: zap drop bitblit support from console code.
|
|From: Gerd Hoffmann <kraxel@redhat.com>
|
|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 <kraxel@redhat.com>
|
|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 <ian.jackson@eu.citrix.com>
|
|Conflicts:
|	hw/cirrus_vga.c
|---
| 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 9984d6f..33c8bac 100644
|--- qemu-xen-traditional/console.c.orig
|+++ qemu-xen-traditional/console.c
--------------------------
Patching file qemu-xen-traditional/console.c using Plan A...
Hunk #1 succeeded at 1398.
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
|--- qemu-xen-traditional/console.h.orig
|+++ qemu-xen-traditional/console.h
--------------------------
Patching file 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 d4bb462..3f941d1 100644
|--- qemu-xen-traditional/hw/cirrus_vga.c.orig
|+++ qemu-xen-traditional/hw/cirrus_vga.c
--------------------------
Patching file qemu-xen-traditional/hw/cirrus_vga.c using Plan A...
Hunk #1 succeeded at 793.
Hunk #2 succeeded at 801.
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
|--- qemu-xen-traditional/hw/vmware_vga.c.orig
|+++ qemu-xen-traditional/hw/vmware_vga.c
--------------------------
Patching file 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
|--- qemu-xen-traditional/vnc.c.orig
|+++ qemu-xen-traditional/vnc.c
--------------------------
Patching file 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/xentools45/patches/patch-blktap_drivers_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-blktap_drivers_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-blktap_drivers_Makefile,v 1.1 2015/01/20 16:42:13 bouyer Exp $
|
|--- blktap/drivers/Makefile.orig	2015-01-12 17:53:24.000000000 +0100
|+++ blktap/drivers/Makefile	2015-01-19 13:16:17.000000000 +0100
--------------------------
Patching file blktap/drivers/Makefile using Plan A...
Hunk #1 succeeded at 44.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-configure
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-configure
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-configure,v 1.3 2016/04/04 14:47:56 wiz Exp $
|
|--- configure.orig	2015-11-03 10:11:18.000000000 +0100
|+++ configure	2016-03-25 23:18:53.000000000 +0100
--------------------------
Patching file configure using Plan A...
Hunk #1 succeeded at 2276.
Hunk #2 succeeded at 3710.
Hunk #3 succeeded at 3776.
Hunk #4 succeeded at 3796.
Hunk #5 succeeded at 9878 (offset 306 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-console_daemon_utils.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/10/28 00:47:07 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 113.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-debugger_gdbsx_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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	2016-09-20 05:59:24.000000000 +0000
|+++ debugger/gdbsx/Makefile
--------------------------
Patching file debugger/gdbsx/Makefile using Plan A...
Hunk #1 succeeded at 18.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-examples_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-firmware_etherboot_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-firmware_etherboot_patches_series
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-firmware_hvmloader_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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.1 2015/01/20 16:42:13 bouyer Exp $
|
|--- firmware/hvmloader/Makefile.orig	2015-01-12 17:53:24.000000000 +0100
|+++ firmware/hvmloader/Makefile	2015-01-19 13:16:37.000000000 +0100
--------------------------
Patching file firmware/hvmloader/Makefile using Plan A...
Hunk #1 succeeded at 26.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-hotplug_NetBSD_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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.2 2016/04/04 14:45:12 bad Exp $
|
|--- hotplug/NetBSD/Makefile.orig	2015-11-03 10:11:18.000000000 +0100
|+++ hotplug/NetBSD/Makefile	2016-03-25 15:21:34.000000000 +0100
--------------------------
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/xentools45/patches/patch-hotplug_NetBSD_block
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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.3 2016/05/21 20:11:21 bad Exp $
|
|Lock the block script to avoid races during vnd configuration.
|
|Use "stat -L" to get device major/minor numbers through symlinks e.g. for
|lvm volumes.
|
|--- hotplug/NetBSD/block.orig	2016-03-23 14:57:27.000000000 +0100
|+++ hotplug/NetBSD/block	2016-05-21 17:08:01.000000000 +0200
--------------------------
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/xentools45/patches/patch-hotplug_NetBSD_vif-bridge
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-hotplug_NetBSD_vif-ip
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-hotplug_common_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-include_xen-sys_NetBSD_gntdev.h
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-libfsimage_common_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-libfsimage_common_Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libfsimage_common_Makefile,v 1.1 2015/01/20 16:42:13 bouyer Exp $
|
|--- libfsimage/common/Makefile.orig	2015-01-12 17:53:24.000000000 +0100
|+++ libfsimage/common/Makefile	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file libfsimage/common/Makefile using Plan A...
Hunk #1 succeeded at 4.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-libfsimage_ufs_ufs.h
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-libxc_xc__netbsd.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer Exp $
|
|--- libxc/xc_netbsd.c.orig	2015-01-12 17:53:24.000000000 +0100
|+++ libxc/xc_netbsd.c	2015-01-19 13:16:38.000000000 +0100
--------------------------
Patching file libxc/xc_netbsd.c using Plan A...
Hunk #1 succeeded at 18.
Hunk #2 succeeded at 396.
Hunk #3 succeeded at 608.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-libxl_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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.2 2015/06/23 17:45:33 bouyer Exp $
|
|--- libxl/Makefile.orig	2015-06-22 15:41:35.000000000 +0200
|+++ libxl/Makefile	2015-06-23 16:51:38.000000000 +0200
--------------------------
Patching file libxl/Makefile using Plan A...
Hunk #1 succeeded at 253.
Hunk #2 succeeded at 267.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-libxl_libxl__create.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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 432.
Hunk #2 succeeded at 469.
Hunk #3 succeeded at 1063 (offset 2 lines).
Hunk #4 succeeded at 1073 (offset 2 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-libxl_libxl__save__helper.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/29 21:33:47 joerg 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 49.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-libxl_libxl_uuid.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-libxl_xl__cmdtable.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2016/04/04 14:35:13 bad 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 507.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-ocaml_common.make
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 19:11:41 abs Exp $
|
|Handle ocaml-findlib 1.7.3 already appending DESTDIR
|Add -unsafe-string to fix build with ocaml-4.06.0 and later. ++PKGREVISION
|
|--- ocaml/common.make.orig	2016-09-20 05:59:24.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/xentools45/patches/patch-ocaml_libs_xb_xs__ring__stubs.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-ocaml_libs_xb_xs__ring__stubs.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ocaml_libs_xb_xs__ring__stubs.c,v 1.1 2016/05/12 21:13:47 abs Exp $
|
|--- ocaml/libs/xb/xs_ring_stubs.c.orig	2016-03-23 13:57:27.000000000 +0000
|+++ ocaml/libs/xb/xs_ring_stubs.c
--------------------------
Patching file ocaml/libs/xb/xs_ring_stubs.c using Plan A...
Hunk #1 succeeded at 55.
Hunk #2 succeeded at 114.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-ocaml_xenstored_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer Exp $
|
|--- ocaml/xenstored/Makefile.orig	2015-01-12 17:53:24.000000000 +0100
|+++ ocaml/xenstored/Makefile	2015-01-19 14:06:50.000000000 +0100
--------------------------
Patching file ocaml/xenstored/Makefile using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-ocaml_xenstored_define.ml
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-ocaml_xenstored_utils.ml
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-pygrub_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer Exp $
|
|--- pygrub/Makefile.orig	2015-01-12 17:53:24.000000000 +0100
|+++ pygrub/Makefile	2015-01-19 14:19:44.000000000 +0100
--------------------------
Patching file pygrub/Makefile using Plan A...
Hunk #1 succeeded at 15.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-qemu-xen-traditional_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_block-raw-posix.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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 1016.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-qemu-xen-traditional_configure
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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.2 2015/01/21 08:53:21 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_hw_e1000.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 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
|
|--- 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/xentools45/patches/patch-qemu-xen-traditional_hw_ide.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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.2 2015/06/11 17:43:58 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_hw_pass-through.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_hw_pass-through.h
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_hw_piix4acpi.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_hw_pt-graphics.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_hw_pt-msi.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_hw_pt-msi.h
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_i386-dm_hookstarget.mak
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen-traditional_xen-hooks.mak
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen_audio_audio.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen_qemu-doc.texi
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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/xentools45/patches/patch-qemu-xen_util_hbitmap.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/patches/patch-qemu-xen_util_hbitmap.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qemu-xen_util_hbitmap.c,v 1.1 2015/01/20 16:42:13 bouyer Exp $
|
|conflits with the popcountl from <strings.h>, no need to redefine one.
|
|--- qemu-xen/util/hbitmap.c.orig	2015-01-19 16:33:58.000000000 +0100
|+++ qemu-xen/util/hbitmap.c	2015-01-19 16:40:45.000000000 +0100
--------------------------
Patching file qemu-xen/util/hbitmap.c using Plan A...
Hunk #1 succeeded at 92.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-qemu-xen_xen-hvm.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/29 21:33:47 joerg Exp $
|
|--- qemu-xen/xen-hvm.c.orig	2015-01-25 20:59:13.000000000 +0000
|+++ qemu-xen/xen-hvm.c
--------------------------
Patching file qemu-xen/xen-hvm.c using Plan A...
Hunk #1 succeeded at 537 (offset 9 lines).
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-xenpaging_xenpaging.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2016/08/06 12:41:36 spz Exp $
|
|--- xenpaging/xenpaging.c.orig	2016-03-23 13:57:27.000000000 +0000
|+++ xenpaging/xenpaging.c
--------------------------
Patching file xenpaging/xenpaging.c using Plan A...
Hunk #1 succeeded at 184.
done
=> Verifying /data/pkgsrc/sysutils/xentools45/patches/patch-xenstore_xc.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xentools45/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 2015/01/20 16:42:13 bouyer 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 725.
done
===> Creating toolchain wrappers for xentools45-4.5.5nb10
===> Configuring for xentools45-4.5.5nb10
=> 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 "pathsvar" in Makefile  hotplug/Linux/init.d/sysconfig.xendomains
=> Substituting "conf" in ocaml/xenstored/define.ml libxl/xl_cmdtable.c ../docs/misc/xl-disk-configuration.txt
=> Substituting "procdev" in ocaml/xenstored/define.ml
=> Substituting "proc" 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/sbdf2devicepath misc/xen-bugtool misc/xen-ringwatch misc/xencons misc/xenpvnetboot misc/xensymoops 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 x86_64--netbsd-ocamlc... no
checking for ocamlc... ocamlc
OCaml version is 4.06.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/xentools45/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 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 wget... no
checking for ftp... /data/scratch/sysutils/xentools45/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 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/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/systemd/proc-xen.mount
config.status: creating hotplug/Linux/systemd/var-lib-xenstored.mount
config.status: creating hotplug/Linux/systemd/xen-init-dom0.service
config.status: creating hotplug/Linux/systemd/xen-qemu-dom0-disk-backend.service
config.status: creating hotplug/Linux/systemd/xen-watchdog.service
config.status: creating hotplug/Linux/systemd/xenconsoled.service
config.status: creating hotplug/Linux/systemd/xendomains.service
config.status: creating hotplug/Linux/systemd/xenstored.service
config.status: creating hotplug/Linux/systemd/xenstored.socket
config.status: creating hotplug/Linux/systemd/xenstored_ro.socket
config.status: creating hotplug/Linux/vif-setup
config.status: creating hotplug/Linux/xen-backend.rules
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 config.h