=> 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 xen413/xen-4.13.1.tar.gz
=> Checksum RMD160 OK for xen413/xen-4.13.1.tar.gz
=> Checksum SHA512 OK for xen413/xen-4.13.1.tar.gz
===> Installing dependencies for xenkernel413-4.13.1
==========================================================================
The following variables will affect the build process of this package,
xenkernel413-4.13.1.  Their current value is shown below:

        * PYTHON_VERSION_DEFAULT = 37

Based on these variables, the following variables have been set:

        * PYPACKAGE = python37

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 python37>=3.7.0: found python37-3.7.7
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
===> 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'.
===> Overriding tools for xenkernel413-4.13.1
===> Extracting for xenkernel413-4.13.1
===> Patching for xenkernel413-4.13.1
=> Applying pkgsrc patches for xenkernel413-4.13.1
=> Verifying /data/pkgsrc/sysutils/xenkernel413/patches/patch-Config.mk
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel413/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 2020/05/26 11:12:10 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/xenkernel413/patches/patch-xen_Makefile
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel413/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 2020/05/26 11:12:10 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 174 (offset 7 lines).
done
=> Verifying /data/pkgsrc/sysutils/xenkernel413/patches/patch-xen_Rules.mk
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel413/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 2020/05/26 11:12:10 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/xenkernel413/patches/patch-xen_arch_x86_Rules.mk
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel413/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 2020/05/26 11:12:10 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/xenkernel413/patches/patch-xen_arch_x86_boot_build32.mk
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel413/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 2020/05/26 11:12:10 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/xenkernel413/patches/patch-xen_arch_x86_mm_p2m.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel413/patches/patch-xen_arch_x86_mm_p2m.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xen_arch_x86_mm_p2m.c,v 1.1 2020/05/26 11:12:10 bouyer Exp $
|
|silent a noisy warning
|
|--- xen/arch/x86/mm/p2m.c.orig	2020-05-03 21:13:56.173269058 +0200
|+++ xen/arch/x86/mm/p2m.c	2020-05-03 21:15:38.477174874 +0200
--------------------------
Patching file xen/arch/x86/mm/p2m.c using Plan A...
Hunk #1 succeeded at 1367.
done
=> Verifying /data/pkgsrc/sysutils/xenkernel413/patches/patch-xen_drivers_passthrough_x86_iommu.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel413/patches/patch-xen_drivers_passthrough_x86_iommu.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xen_drivers_passthrough_x86_iommu.c,v 1.1 2020/05/26 11:12:10 bouyer Exp $
|
|Silent noisy warning
|
|--- xen/drivers/passthrough/x86/iommu.c.orig	2020-05-03 22:03:37.840754709 +0200
|+++ xen/drivers/passthrough/x86/iommu.c	2020-05-03 22:04:36.676914512 +0200
--------------------------
Patching file xen/drivers/passthrough/x86/iommu.c using Plan A...
Hunk #1 succeeded at 234.
done
=> Verifying /data/pkgsrc/sysutils/xenkernel413/patches/patch-xen_tools_symbols.c
=> Applying pkgsrc patch /data/pkgsrc/sysutils/xenkernel413/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 2020/05/26 11:12:10 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
===> Creating toolchain wrappers for xenkernel413-4.13.1