=> 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/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 ===> Installing dependencies for xenkernel48-4.8.0nb1 ========================================================================== The following variables will affect the build process of this package, xenkernel48-4.8.0nb1. Their current value is shown below: * PYTHON_VERSION_DEFAULT = 27 Based on these variables, the following variables have been set: * PYPACKAGE = python27 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 gmake>=3.81: found gmake-4.1nb3 => Tool dependency checkperms>=1.1: found checkperms-1.11nb1 => Build dependency python27>=2.7.1nb2: found python27-2.7.13nb1 => Build dependency cwrappers>=20150314: found cwrappers-20170112 ===> Overriding tools for xenkernel48-4.8.0nb1 ===> Extracting for xenkernel48-4.8.0nb1 ===> Patching for xenkernel48-4.8.0nb1 => Applying pkgsrc patches for xenkernel48-4.8.0nb1 => Verifying /data/pkgsrc/sysutils/xenkernel48/patches/patch-Config.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel48/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:09 bouyer Exp $ | |--- Config.mk.orig 2016-12-05 13:03:27.000000000 +0100 |+++ Config.mk 2017-03-21 17:03:57.000000000 +0100 -------------------------- Patching file Config.mk using Plan A... Hunk #1 succeeded at 36. done => Verifying /data/pkgsrc/sysutils/xenkernel48/patches/patch-XSA-212 => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel48/patches/patch-XSA-212 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-XSA-212,v 1.1 2017/04/08 12:30:43 spz Exp $ | |memory: properly check guest memory ranges in XENMEM_exchange handling | |The use of guest_handle_okay() here (as introduced by the XSA-29 fix) |is insufficient here, guest_handle_subrange_okay() needs to be used |instead. | |Note that the uses are okay in |- XENMEM_add_to_physmap_batch handling due to the size field being only | 16 bits wide, |- livepatch_list() due to the limit of 1024 enforced on the | number-of-entries input (leaving aside the fact that this can be | called by a privileged domain only anyway), |- compat mode handling due to counts there being limited to 32 bits, |- everywhere else due to guest arrays being accessed sequentially from | index zero. | |This is XSA-212. | |Reported-by: Jann Horn |Signed-off-by: Jan Beulich |Reviewed-by: Andrew Cooper | |--- xen/common/memory.c |+++ xen/common/memory.c -------------------------- Patching file xen/common/memory.c using Plan A... Hunk #1 succeeded at 437 (offset 1 line). Hunk #2 succeeded at 448 (offset 1 line). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |--- xen/include/asm-x86/x86_64/uaccess.h |+++ xen/include/asm-x86/x86_64/uaccess.h -------------------------- Patching file xen/include/asm-x86/x86_64/uaccess.h using Plan A... Hunk #1 succeeded at 29. Hunk #2 succeeded at 41. done => Verifying /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-xen_Makefile,v 1.1 2017/03/30 09:15:09 bouyer Exp $ | |--- xen/Makefile.orig 2016-02-09 14:44:19.000000000 +0000 |+++ xen/Makefile -------------------------- Patching file xen/Makefile using Plan A... Hunk #1 succeeded at 166 (offset 31 lines). done => Verifying /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_Rules.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_Rules.mk Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-xen_Rules.mk,v 1.1 2017/03/30 09:15:09 bouyer Exp $ | |--- xen/Rules.mk.orig 2017-03-21 18:32:41.000000000 +0100 |+++ xen/Rules.mk 2017-03-21 18:33:07.000000000 +0100 -------------------------- Patching file xen/Rules.mk using Plan A... Hunk #1 succeeded at 5. done => Verifying /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_arch_x86_Rules.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_arch_x86_Rules.mk Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-xen_arch_x86_Rules.mk,v 1.1 2017/03/30 09:15:09 bouyer Exp $ | |--- ./xen/arch/x86/Rules.mk.orig 2016-12-05 13:03:27.000000000 +0100 |+++ ./xen/arch/x86/Rules.mk 2017-03-21 16:59:28.000000000 +0100 -------------------------- Patching file ./xen/arch/x86/Rules.mk using Plan A... Hunk #1 succeeded at 5. done => Verifying /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_arch_x86_boot_build32.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_arch_x86_boot_build32.mk Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-xen_arch_x86_boot_build32.mk,v 1.1 2017/03/30 09:15:09 bouyer Exp $ |linux's toolchain doesn't generate a .eh_frame section but NetBSD does. |remove it. | |--- xen/arch/x86/boot/build32.mk.orig 2017-03-24 16:06:14.000000000 +0100 |+++ xen/arch/x86/boot/build32.mk 2017-03-24 16:06:37.000000000 +0100 -------------------------- Patching file xen/arch/x86/boot/build32.mk using Plan A... Hunk #1 succeeded at 24. done => Verifying /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_tools_symbols.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_tools_symbols.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-xen_tools_symbols.c,v 1.1 2017/03/30 09:15:09 bouyer Exp $ |fix "error: array subscript has type 'char'" | |--- xen/tools/symbols.c.orig 2017-03-21 17:37:05.000000000 +0100 |+++ xen/tools/symbols.c 2017-03-21 17:37:53.000000000 +0100 -------------------------- Patching file xen/tools/symbols.c using Plan A... Hunk #1 succeeded at 173. done ===> Creating toolchain wrappers for xenkernel48-4.8.0nb1