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

        * PYTHON_VERSION_DEFAULT = 37

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.17nb2
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
===> Overriding tools for xenkernel48-4.8.5
===> Extracting for xenkernel48-4.8.5
===> Patching for xenkernel48-4.8.5
=> Applying pkgsrc patches for xenkernel48-4.8.5
=> 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-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_arch_x86_mm.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel48/patches/patch-xen_arch_x86_mm.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xen_arch_x86_mm.c,v 1.1 2019/08/30 13:23:09 bouyer Exp $
|remove assert, which fires when freeing a page table page
|
|--- xen/arch/x86/mm.c.orig	2019-08-30 12:51:48.000000000 +0200
|+++ xen/arch/x86/mm.c	2019-08-30 12:52:21.000000000 +0200
--------------------------
Patching file xen/arch/x86/mm.c using Plan A...
Hunk #1 succeeded at 2590.
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.5