=> 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 xen411/xen-4.11.0.tar.gz => Checksum RMD160 OK for xen411/xen-4.11.0.tar.gz => Checksum SHA512 OK for xen411/xen-4.11.0.tar.gz ===> Installing dependencies for xenkernel411-4.11.0 ========================================================================== The following variables will affect the build process of this package, xenkernel411-4.11.0. 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.2.1nb1 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Build dependency python27>=2.7.1nb2: found python27-2.7.15nb1 => Build dependency cwrappers>=20150314: found cwrappers-20180325 ===> Overriding tools for xenkernel411-4.11.0 ===> Extracting for xenkernel411-4.11.0 ===> Patching for xenkernel411-4.11.0 => Applying pkgsrc patches for xenkernel411-4.11.0 => Verifying /data/pkgsrc/sysutils/xenkernel411/patches/patch-Config.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel411/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 2018/07/24 13:40:11 bouyer Exp $ | |--- Config.mk.orig 2018-04-17 19:21:31.000000000 +0200 |+++ Config.mk 2018-04-23 13:29:47.000000000 +0200 -------------------------- Patching file Config.mk using Plan A... Hunk #1 succeeded at 32. done => Verifying /data/pkgsrc/sysutils/xenkernel411/patches/patch-xen_Makefile => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel411/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 2018/07/24 13:40:11 bouyer Exp $ | |--- xen/Makefile.orig 2018-04-17 19:21:31.000000000 +0200 |+++ xen/Makefile 2018-04-23 13:29:47.000000000 +0200 -------------------------- Patching file xen/Makefile using Plan A... Hunk #1 succeeded at 167. done => Verifying /data/pkgsrc/sysutils/xenkernel411/patches/patch-xen_Rules.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel411/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 2018/07/24 13:40:11 bouyer Exp $ | |--- xen/Rules.mk.orig 2018-04-23 14:50:02.000000000 +0200 |+++ xen/Rules.mk 2018-04-23 14:50:32.000000000 +0200 -------------------------- Patching file xen/Rules.mk using Plan A... Hunk #1 succeeded at 1. done => Verifying /data/pkgsrc/sysutils/xenkernel411/patches/patch-xen_arch_x86_Rules.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel411/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 2018/07/24 13:40:11 bouyer Exp $ | |--- xen/arch/x86/Rules.mk.orig 2018-04-17 19:21:31.000000000 +0200 |+++ xen/arch/x86/Rules.mk 2018-04-23 13:31:24.000000000 +0200 -------------------------- Patching file xen/arch/x86/Rules.mk using Plan A... Hunk #1 succeeded at 8. done => Verifying /data/pkgsrc/sysutils/xenkernel411/patches/patch-xen_arch_x86_boot_build32.mk => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel411/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 2018/07/24 13:40:11 bouyer Exp $ |linux's toolchain doesn't generate a .eh_frame section but NetBSD does. |remove it. | |--- xen/arch/x86/boot/build32.mk.orig 2018-04-17 19:21:31.000000000 +0200 |+++ xen/arch/x86/boot/build32.mk 2018-04-23 13:29:47.000000000 +0200 -------------------------- Patching file xen/arch/x86/boot/build32.mk using Plan A... Hunk #1 succeeded at 25. done => Verifying /data/pkgsrc/sysutils/xenkernel411/patches/patch-xen_tools_symbols.c => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel411/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 2018/07/24 13:40:11 bouyer Exp $ |fix "error: array subscript has type 'char'" | |--- xen/tools/symbols.c.orig 2018-04-17 19:21:31.000000000 +0200 |+++ xen/tools/symbols.c 2018-04-23 13:29:47.000000000 +0200 -------------------------- Patching file xen/tools/symbols.c using Plan A... Hunk #1 succeeded at 173. done => Verifying /data/pkgsrc/sysutils/xenkernel411/patches/patch-zz-JBeulich => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel411/patches/patch-zz-JBeulich Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-zz-JBeulich,v 1.1 2018/07/24 13:40:11 bouyer Exp $ | |x86: further avoid setting TLB flush time stamp | |NetBSD's use of linear page tables in 32-bit mode exposes an issue with |us still storing TLB flush time stamps too early, corrupting the |linear_pt_count field living in the same union. Since we go that path |(for page tables) only when neither PGT_validated nor PGT_partial are |set on a page, we don't really require a flush to happen (see also the |code comment), yet we're also no concerned if one happens which isn't |needed (which might occur when we never write the time stamp). | |Reported-by: Manuel Bouyer |Signed-off-by: Jan Beulich | |--- ./xen/arch/x86/mm.c.orig 2018-07-09 15:47:19.000000000 +0200 |+++ ./xen/arch/x86/mm.c 2018-07-16 12:38:47.000000000 +0200 -------------------------- Patching file ./xen/arch/x86/mm.c using Plan A... Hunk #1 succeeded at 2538. Hunk #2 succeeded at 2569. done => Verifying /data/pkgsrc/sysutils/xenkernel411/patches/patch-zz-bouyer => Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel411/patches/patch-zz-bouyer Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-zz-bouyer,v 1.1 2018/07/24 13:40:11 bouyer Exp $ |Dirty hack to avoid assert failure. This has been discussed on xen-devel |but no solution has been fonud so far. |The box producing http://www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/ |is running with this patch; the printk has fired but the |hypervisor keeps running. | |--- xen/arch/x86/mm.c.orig 2018-07-19 10:32:07.000000000 +0200 |+++ xen/arch/x86/mm.c 2018-07-21 20:47:47.000000000 +0200 -------------------------- Patching file xen/arch/x86/mm.c using Plan A... Hunk #1 succeeded at 674. done ===> Creating toolchain wrappers for xenkernel411-4.11.0