=> Bootstrap dependency digest>=20211023: found digest-20220214 => Checksum BLAKE2s OK for xen415/ipxe-988d2c13cdf0f0b4140685af35ced70ac5b3283c.tar.gz => Checksum SHA512 OK for xen415/ipxe-988d2c13cdf0f0b4140685af35ced70ac5b3283c.tar.gz => Checksum BLAKE2s OK for xen415/seabios-1.16.0.tar.gz => Checksum SHA512 OK for xen415/seabios-1.16.0.tar.gz => Checksum BLAKE2s OK for xen415/xen-4.15.5.tar.gz => Checksum SHA512 OK for xen415/xen-4.15.5.tar.gz ===> Installing dependencies for xentools415-4.15.5nb4 ========================================================================== The following variables will affect the build process of this package, xentools415-4.15.5nb4. Their current value is shown below: * CURSES_DEFAULT = curses * PYTHON_VERSION_DEFAULT = 312 * VARBASE = /var Based on these variables, the following variables have been set: * CURSES_TYPE = curses * PYPACKAGE = python312 * TERMCAP_TYPE = termcap You may want to abort the process now with CTRL-C and change the value of variables in the first group before continuing. Be sure to run `/usr/bin/make clean' after the changes. ========================================================================== => Tool dependency dev86-[0-9]*: found dev86-0.16.21 => Tool dependency py312-setuptools-[0-9]*: found py312-setuptools-78.1.1 => Tool dependency glib2-tools-[0-9]*: found glib2-tools-2.82.5 => Tool dependency mktools-[0-9]*: found mktools-20250213 => Tool dependency bash-[0-9]*: found bash-5.2.37 => Tool dependency bison>=1.0: found bison-3.8.2nb1 => Tool dependency cmake>=3.18: found cmake-3.31.7nb2 => Tool dependency gmake>=3.81: found gmake-4.4.1 => Tool dependency gsed>=3.0.2: found gsed-4.9nb1 => Tool dependency perl>=5.0: found perl-5.40.2 => Tool dependency pkgconf-[0-9]*: found pkgconf-2.4.3 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Build dependency x11-links>=1.36: found x11-links-1.36 => Full dependency argp>=1.3: found argp-1.3nb3 => Full dependency glib2>=2.76.4nb1: found glib2-2.82.5 => Full dependency libgcrypt>=1.6.0: found libgcrypt-1.11.0nb2 => Full dependency ocaml>=4.14.0: found ocaml-4.14.2 => Full dependency ocaml-findlib>=1.9.3nb1: found ocaml-findlib-1.9.8nb1 => Full dependency pciutils>=3.8: found pciutils-3.13.0 => Full dependency python312>=3.12.0nb1: found python312-3.12.10nb1 => Full dependency yajl>=1.0.9: found yajl-2.1.0 => Full dependency zstd>=1.3.6: found zstd-1.5.7 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Overriding tools for xentools415-4.15.5nb4 ===> Extracting for xentools415-4.15.5nb4 ===> Patching for xentools415-4.15.5nb4 => Applying pkgsrc patches for xentools415-4.15.5nb4 => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-.._seabios-rel-1.16.0_src_string.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-.._seabios-rel-1.16.0_src_string.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-.._seabios-rel-1.16.0_src_string.c,v 1.1 2023/08/24 10:27:09 bouyer Exp $ | |when the code is compiled -fwhole-program, memcpy() will be ommitted by gcc |because nothing in the file references it. Later the link fails with |undefined references to memcpy(). |Force the inclusion with (externally_visible) attribute | |--- ../seabios-rel-1.16.0/src/string.c.orig 2021-04-17 22:32:25.409876075 +0200 |+++ ../seabios-rel-1.16.0/src/string.c 2021-04-17 22:32:39.873615679 +0200 -------------------------- Patching file ../seabios-rel-1.16.0/src/string.c using Plan A... Hunk #1 succeeded at 149. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-Config.mk => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/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 2021/04/18 12:31:26 bouyer Exp $ | |Make sure to pass pkgsrc CFLAGS. |Use -R instead if -rpath, to appease our linker (--enable-rpath bug ?) | |--- Config.mk.orig 2020-12-08 15:28:31.000000000 +0100 |+++ Config.mk 2020-12-14 11:48:10.669586105 +0100 -------------------------- Patching file Config.mk using Plan A... Hunk #1 succeeded at 33. Hunk #2 succeeded at 188. Hunk #3 succeeded at 200. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- Makefile.orig 2019-12-17 15:23:09.000000000 +0100 |+++ Makefile 2020-05-08 20:05:12.875067651 +0200 -------------------------- Patching file Makefile using Plan A... Hunk #1 succeeded at 71 (offset 6 lines). Hunk #2 succeeded at 142 (offset 6 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-XSA440 => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-XSA440 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-XSA440,v 1.1 2023/11/15 15:59:36 bouyer Exp $ | |From 5d8b3d1ec98e56155d9650d7f4a70cd8ba9dc27d Mon Sep 17 00:00:00 2001 |From: Julien Grall |Date: Fri, 22 Sep 2023 11:32:16 +0100 |Subject: tools/xenstored: domain_entry_fix(): Handle conflicting transaction | |The function domain_entry_fix() will be initially called to check if the |quota is correct before attempt to commit any nodes. So it would be |possible that accounting is temporarily negative. This is the case |in the following sequence: | | 1) Create 50 nodes | 2) Start two transactions | 3) Delete all the nodes in each transaction | 4) Commit the two transactions | |Because the first transaction will have succeed and updated the |accounting, there is no guarantee that 'd->nbentry + num' will still |be above 0. So the assert() would be triggered. |The assert() was introduced in dbef1f748289 ("tools/xenstore: simplify |and fix per domain node accounting") with the assumption that the |value can't be negative. As this is not true revert to the original |check but restricted to the path where we don't update. Take the |opportunity to explain the rationale behind the check. | |This CVE-2023-34323 / XSA-440. | |Reported-by: Stanislav Uschakow |Fixes: dbef1f748289 ("tools/xenstore: simplify and fix per domain node accounting") |Signed-off-by: Julien Grall |Reviewed-by: Juergen Gross | |diff --git a/tools/xenstore/xenstored_domain.c b/tools/xenstore/xenstored_domain.c |index aa86892fed9e..6074df210c6e 100644 |--- tools/xenstore/xenstored_domain.c.orig |+++ tools/xenstore/xenstored_domain.c -------------------------- Patching file tools/xenstore/xenstored_domain.c using Plan A... Hunk #1 succeeded at 1068 (offset -26 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-XSA443 => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-XSA443 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-XSA443,v 1.1 2023/11/15 15:59:36 bouyer Exp $ | |From c4d597f63832a53bbb1b826af7a4677e40e9fded Mon Sep 17 00:00:00 2001 |From: Alejandro Vallejo |Date: Thu, 14 Sep 2023 13:22:50 +0100 |Subject: [PATCH 01/11] libfsimage/xfs: Remove dead code | |xfs_info.agnolog (and related code) and XFS_INO_AGBNO_BITS are dead code |that serve no purpose. | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Alejandro Vallejo |Reviewed-by: Jan Beulich |--- | tools/libfsimage/xfs/fsys_xfs.c | 18 ------------------ | 1 file changed, 18 deletions(-) | |diff --git a/tools/libfsimage/xfs/fsys_xfs.c b/tools/libfsimage/xfs/fsys_xfs.c |index d735a88e55f3..2800699f5985 100644 |--- tools/libfsimage/xfs/fsys_xfs.c.orig |+++ tools/libfsimage/xfs/fsys_xfs.c -------------------------- Patching file tools/libfsimage/xfs/fsys_xfs.c using Plan A... Hunk #1 succeeded at 37. Hunk #2 succeeded at 64. Hunk #3 succeeded at 146. Hunk #4 succeeded at 455. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From f75b0a70da392672fb7d9feed2a9e9515d74df2c Mon Sep 17 00:00:00 2001 |From: Alejandro Vallejo |Date: Thu, 14 Sep 2023 13:22:51 +0100 |Subject: [PATCH 02/11] libfsimage/xfs: Amend mask32lo() to allow the value 32 | |agblklog could plausibly be 32, but that would overflow this shift. |Perform the shift as ULL and cast to u32 at the end instead. | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Alejandro Vallejo |Acked-by: Jan Beulich |--- | tools/libfsimage/xfs/fsys_xfs.c | 2 +- | 1 file changed, 1 insertion(+), 1 deletion(-) | |diff --git a/tools/libfsimage/xfs/fsys_xfs.c b/tools/libfsimage/xfs/fsys_xfs.c |index 2800699f5985..4720bb4505c8 100644 |--- tools/libfsimage/xfs/fsys_xfs.c.orig |+++ tools/libfsimage/xfs/fsys_xfs.c -------------------------- Patching file tools/libfsimage/xfs/fsys_xfs.c using Plan A... Hunk #1 succeeded at 60. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From 25fae23b32ee4d990ae11368ee21e28e66dbfa25 Mon Sep 17 00:00:00 2001 |From: Alejandro Vallejo |Date: Thu, 14 Sep 2023 13:22:52 +0100 |Subject: [PATCH 03/11] libfsimage/xfs: Sanity-check the superblock during | mounts | |Sanity-check the XFS superblock for wellformedness at the mount handler. |This forces pygrub to abort parsing a potentially malformed filesystem and |ensures the invariants assumed throughout the rest of the code hold. | |Also, derive parameters from previously sanitized parameters where possible |(rather than reading them off the superblock) | |The code doesn't try to avoid overflowing the end of the disk, because |that's an unlikely and benign error. Parameters used in calculations of |xfs_daddr_t (like the root inode index) aren't in critical need of being |sanitized. | |The sanitization of agblklog is basically checking that no obvious |overflows happen on agblklog, and then ensuring agblocks is contained in |the range (2^(sb_agblklog-1), 2^sb_agblklog]. | |This is part of XSA-443 / CVE-2023-34325 | |Reported-by: Ferdinand Nölscher |Signed-off-by: Alejandro Vallejo |Reviewed-by: Jan Beulich |--- | tools/libfsimage/xfs/fsys_xfs.c | 48 ++++++++++++++++++++++++++------- | tools/libfsimage/xfs/xfs.h | 12 +++++++++ | 2 files changed, 50 insertions(+), 10 deletions(-) | |diff --git a/tools/libfsimage/xfs/fsys_xfs.c b/tools/libfsimage/xfs/fsys_xfs.c |index 4720bb4505c8..e4eb7e1ee26f 100644 |--- tools/libfsimage/xfs/fsys_xfs.c.orig |+++ tools/libfsimage/xfs/fsys_xfs.c -------------------------- Patching file tools/libfsimage/xfs/fsys_xfs.c using Plan A... Hunk #1 succeeded at 17. Hunk #2 succeeded at 434. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libfsimage/xfs/xfs.h b/tools/libfsimage/xfs/xfs.h |index 40699281e44d..b87e37d3d7e9 100644 |--- tools/libfsimage/xfs/xfs.h.orig |+++ tools/libfsimage/xfs/xfs.h -------------------------- Patching file tools/libfsimage/xfs/xfs.h using Plan A... Hunk #1 succeeded at 134. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From e72c68e702dd930bc6013182bb44d3e8fbbb6bf4 Mon Sep 17 00:00:00 2001 |From: Alejandro Vallejo |Date: Thu, 14 Sep 2023 13:22:53 +0100 |Subject: [PATCH 04/11] libfsimage/xfs: Add compile-time check to libfsimage | |Adds the common tools include folder to the -I compile flags |of libfsimage. This allows us to use: | xen-tools/common-macros.h:BUILD_BUG_ON() | |With it, statically assert a sanitized "blocklog - SECTOR_BITS" cannot |underflow. | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Alejandro Vallejo |Reviewed-by: Jan Beulich |--- | tools/libfsimage/Rules.mk | 2 +- | tools/libfsimage/xfs/fsys_xfs.c | 4 +++- | 2 files changed, 4 insertions(+), 2 deletions(-) | |diff --git a/tools/libfsimage/Rules.mk b/tools/libfsimage/Rules.mk |index bb6d42abb494..80598fb70aa7 100644 |--- tools/libfsimage/Rules.mk.orig |+++ tools/libfsimage/Rules.mk -------------------------- Patching file tools/libfsimage/Rules.mk using Plan A... Hunk #1 succeeded at 1. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libfsimage/xfs/fsys_xfs.c b/tools/libfsimage/xfs/fsys_xfs.c |index e4eb7e1ee26f..4a8dd6f2397b 100644 |--- tools/libfsimage/xfs/fsys_xfs.c.orig |+++ tools/libfsimage/xfs/fsys_xfs.c -------------------------- Patching file tools/libfsimage/xfs/fsys_xfs.c using Plan A... Hunk #1 succeeded at 19. Hunk #2 succeeded at 478. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From 75fdc03c5a6b7fac0c3a5ac06a5beaac73aad36f Mon Sep 17 00:00:00 2001 |From: Alejandro Vallejo |Date: Mon, 25 Sep 2023 18:32:21 +0100 |Subject: [PATCH 05/11] tools/pygrub: Remove unnecessary hypercall | |There's a hypercall being issued in order to determine whether PV64 is |supported, but since Xen 4.3 that's strictly true so it's not required. | |Plus, this way we can avoid mapping the privcmd interface altogether in the |depriv pygrub. | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Alejandro Vallejo |Reviewed-by: Andrew Cooper |--- | tools/pygrub/src/pygrub | 12 +----------- | 1 file changed, 1 insertion(+), 11 deletions(-) | |diff --git a/tools/pygrub/src/pygrub b/tools/pygrub/src/pygrub |index ce7ab0eb8cf3..ce4e07d3e823 100755 |--- tools/pygrub/src/pygrub.orig |+++ tools/pygrub/src/pygrub -------------------------- Patching file tools/pygrub/src/pygrub using Plan A... Hunk #1 succeeded at 18. Hunk #2 succeeded at 667. Hunk #3 succeeded at 675. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From 1083a16f63461e844e9515ac4d35d48bf55785af Mon Sep 17 00:00:00 2001 |From: Alejandro Vallejo |Date: Mon, 25 Sep 2023 18:32:22 +0100 |Subject: [PATCH 06/11] tools/pygrub: Small refactors | |Small tidy up to ensure output_directory always has a trailing '/' to ease |concatenating paths and that `output` can only be a filename or None. | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Alejandro Vallejo |Acked-by: Andrew Cooper |--- | tools/pygrub/src/pygrub | 10 +++++----- | 1 file changed, 5 insertions(+), 5 deletions(-) | |diff --git a/tools/pygrub/src/pygrub b/tools/pygrub/src/pygrub |index ce4e07d3e823..1042c05b8676 100755 |--- tools/pygrub/src/pygrub.orig |+++ tools/pygrub/src/pygrub -------------------------- Patching file tools/pygrub/src/pygrub using Plan A... Hunk #1 succeeded at 793. Hunk #2 succeeded at 815. Hunk #3 succeeded at 848. Hunk #4 succeeded at 861. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From 350db30e33f39af40c1e3752d73c0a30ef2d26e7 Mon Sep 17 00:00:00 2001 |From: Alejandro Vallejo |Date: Mon, 25 Sep 2023 18:32:23 +0100 |Subject: [PATCH 07/11] tools/pygrub: Open the output files earlier | |This patch allows pygrub to get ahold of every RW file descriptor it needs |early on. A later patch will clamp the filesystem it can access so it can't |obtain any others. | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Alejandro Vallejo |Acked-by: Andrew Cooper |--- | tools/pygrub/src/pygrub | 37 ++++++++++++++++++++++--------------- | 1 file changed, 22 insertions(+), 15 deletions(-) | |diff --git a/tools/pygrub/src/pygrub b/tools/pygrub/src/pygrub |index 1042c05b8676..91e2ec2ab105 100755 |--- tools/pygrub/src/pygrub.orig |+++ tools/pygrub/src/pygrub -------------------------- Patching file tools/pygrub/src/pygrub using Plan A... Hunk #1 succeeded at 738. Hunk #2 succeeded at 749. Hunk #3 succeeded at 857. Hunk #4 succeeded at 924. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From 1548ad2291ec7a72ae6949c11d2e50cea135a48d Mon Sep 17 00:00:00 2001 |From: Alejandro Vallejo |Date: Mon, 25 Sep 2023 18:32:24 +0100 |Subject: [PATCH 08/11] tools/libfsimage: Export a new function to preload all | plugins | |This is work required in order to let pygrub operate in highly deprivileged |chroot mode. This patch adds a function that preloads every plugin, hence |ensuring that a on function exit, every shared library is loaded in memory. | |The new "init" function is supposed to be used before depriv, but that's |fine because it's not acting on untrusted data. | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Alejandro Vallejo |Acked-by: Andrew Cooper |--- | tools/libfsimage/common/fsimage_plugin.c | 4 ++-- | tools/libfsimage/common/mapfile-GNU | 1 + | tools/libfsimage/common/mapfile-SunOS | 1 + | tools/libfsimage/common/xenfsimage.h | 8 ++++++++ | tools/pygrub/src/fsimage/fsimage.c | 15 +++++++++++++++ | 5 files changed, 27 insertions(+), 2 deletions(-) | |diff --git a/tools/libfsimage/common/fsimage_plugin.c b/tools/libfsimage/common/fsimage_plugin.c |index de1412b4233a..d0cb9e96a654 100644 |--- tools/libfsimage/common/fsimage_plugin.c.orig |+++ tools/libfsimage/common/fsimage_plugin.c -------------------------- Patching file tools/libfsimage/common/fsimage_plugin.c using Plan A... Hunk #1 succeeded at 119. Hunk #2 succeeded at 180. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libfsimage/common/mapfile-GNU b/tools/libfsimage/common/mapfile-GNU |index 26d4d7a69ec7..2d54d527d7f5 100644 |--- tools/libfsimage/common/mapfile-GNU.orig |+++ tools/libfsimage/common/mapfile-GNU -------------------------- Patching file tools/libfsimage/common/mapfile-GNU using Plan A... Hunk #1 succeeded at 1. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libfsimage/common/mapfile-SunOS b/tools/libfsimage/common/mapfile-SunOS |index e99b90b65077..48deedb4252f 100644 |--- tools/libfsimage/common/mapfile-SunOS.orig |+++ tools/libfsimage/common/mapfile-SunOS -------------------------- Patching file tools/libfsimage/common/mapfile-SunOS using Plan A... Hunk #1 succeeded at 1. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libfsimage/common/xenfsimage.h b/tools/libfsimage/common/xenfsimage.h |index 201abd54f23a..341883b2d71a 100644 |--- tools/libfsimage/common/xenfsimage.h.orig |+++ tools/libfsimage/common/xenfsimage.h -------------------------- Patching file tools/libfsimage/common/xenfsimage.h using Plan A... Hunk #1 succeeded at 35. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/pygrub/src/fsimage/fsimage.c b/tools/pygrub/src/fsimage/fsimage.c |index 2ebbbe35df92..92fbf2851f01 100644 |--- tools/pygrub/src/fsimage/fsimage.c.orig |+++ tools/pygrub/src/fsimage/fsimage.c -------------------------- Patching file tools/pygrub/src/fsimage/fsimage.c using Plan A... Hunk #1 succeeded at 286. Hunk #2 succeeded at 306. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From 4d331b0b914dfc17bd2d883bc55aeb798930832a Mon Sep 17 00:00:00 2001 |From: Alejandro Vallejo |Date: Mon, 25 Sep 2023 18:32:25 +0100 |Subject: [PATCH 09/11] tools/pygrub: Deprivilege pygrub | |Introduce a --runas= flag to deprivilege pygrub on Linux and *BSDs. It |also implicitly creates a chroot env where it drops a deprivileged forked |process. The chroot itself is cleaned up at the end. | |If the --runas arg is present, then pygrub forks, leaving the child to |deprivilege itself, and waiting for it to complete. When the child exists, |the parent performs cleanup and exits with the same error code. | |This is roughly what the child does: | 1. Initialize libfsimage (this loads every .so in memory so the chroot | can avoid bind-mounting /{,usr}/lib* | 2. Create a temporary empty chroot directory | 3. Mount tmpfs in it | 4. Bind mount the disk inside, because libfsimage expects a path, not a | file descriptor. | 5. Remount the root tmpfs to be stricter (ro,nosuid,nodev) | 6. Set RLIMIT_FSIZE to a sensibly high amount (128 MiB) | 7. Depriv gid, groups and uid | |With this scheme in place, the "output" files are writable (up to |RLIMIT_FSIZE octets) and the exposed filesystem is immutable and contains |the single only file we can't easily get rid of (the disk). | |If running on Linux, the child process also unshares mount, IPC, and |network namespaces before dropping its privileges. | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Alejandro Vallejo |Acked-by: Andrew Cooper |--- | tools/pygrub/setup.py | 2 +- | tools/pygrub/src/pygrub | 162 +++++++++++++++++++++++++++++++++++++--- | 2 files changed, 154 insertions(+), 10 deletions(-) | |diff --git a/tools/pygrub/setup.py b/tools/pygrub/setup.py |index b8f1dc4590cf..f16187b6d118 100644 |--- tools/pygrub/setup.py.orig |+++ tools/pygrub/setup.py -------------------------- Patching file tools/pygrub/setup.py using Plan A... Hunk #1 succeeded at 17. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/pygrub/src/pygrub b/tools/pygrub/src/pygrub |index 91e2ec2ab105..7cea496ade08 100755 |--- tools/pygrub/src/pygrub.orig |+++ tools/pygrub/src/pygrub -------------------------- Patching file tools/pygrub/src/pygrub using Plan A... Hunk #1 succeeded at 16. Hunk #2 succeeded at 30. Hunk #3 succeeded at 864. Hunk #4 succeeded at 888. Hunk #5 succeeded at 898. Hunk #6 succeeded at 919. Hunk #7 succeeded at 943. Hunk #8 succeeded at 986. Hunk #9 succeeded at 1011. Hunk #10 succeeded at 1069. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From 576e7aa02ab838b6768b498f310c70ca49537202 Mon Sep 17 00:00:00 2001 |From: Roger Pau Monne |Date: Mon, 25 Sep 2023 14:30:20 +0200 |Subject: [PATCH 10/11] libxl: add support for running bootloader in restricted | mode |MIME-Version: 1.0 |Content-Type: text/plain; charset=UTF-8 |Content-Transfer-Encoding: 8bit | |Much like the device model depriv mode, add the same kind of support for the |bootloader. Such feature allows passing a UID as a parameter for the |bootloader to run as, together with the bootloader itself taking the necessary |actions to isolate. | |Note that the user to run the bootloader as must have the right permissions to |access the guest disk image (in read mode only), and that the bootloader will |be run in non-interactive mode when restricted. | |If enabled bootloader restrict mode will attempt to re-use the user(s) from the |QEMU depriv implementation if no user is provided on the configuration file or |the environment. See docs/features/qemu-deprivilege.pandoc for more |information about how to setup those users. | |Bootloader restrict mode is not enabled by default as it requires certain |setup to be done first (setup of the user(s) to use in restrict mode). | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Roger Pau Monné |Reviewed-by: Anthony PERARD |--- | docs/man/xl.1.pod.in | 33 +++++++++++ | tools/libs/light/libxl_bootloader.c | 89 ++++++++++++++++++++++++++++- | tools/libs/light/libxl_dm.c | 8 +-- | tools/libs/light/libxl_internal.h | 8 +++ | 4 files changed, 131 insertions(+), 7 deletions(-) | |diff --git a/docs/man/xl.1.pod.in b/docs/man/xl.1.pod.in |index 45e1430aeb74..96e6fb1c32a3 100644 |--- docs/man/xl.1.pod.in.orig |+++ docs/man/xl.1.pod.in -------------------------- Patching file docs/man/xl.1.pod.in using Plan A... Hunk #1 succeeded at 1976. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libs/light/libxl_bootloader.c b/tools/libs/light/libxl_bootloader.c |index 18e9ebd7148c..97d9bf4ddc0a 100644 |--- tools/libs/light/libxl_bootloader.c.orig |+++ tools/libs/light/libxl_bootloader.c -------------------------- Patching file tools/libs/light/libxl_bootloader.c using Plan A... Hunk #1 succeeded at 14. Hunk #2 succeeded at 47. Hunk #3 succeeded at 129. Hunk #4 succeeded at 164. Hunk #5 succeeded at 529. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libs/light/libxl_dm.c b/tools/libs/light/libxl_dm.c |index b86e8ccc858f..59de5c1ae22f 100644 |--- tools/libs/light/libxl_dm.c.orig |+++ tools/libs/light/libxl_dm.c -------------------------- Patching file tools/libs/light/libxl_dm.c using Plan A... Hunk #1 succeeded at 80. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libs/light/libxl_internal.h b/tools/libs/light/libxl_internal.h |index cc27c72ecf30..8415d1feed16 100644 |--- tools/libs/light/libxl_internal.h.orig |+++ tools/libs/light/libxl_internal.h -------------------------- Patching file tools/libs/light/libxl_internal.h using Plan A... Hunk #1 succeeded at 4864. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |-- |2.42.0 | |From 34221884752bb835bbdab66378b3cecbf133e3d3 Mon Sep 17 00:00:00 2001 |From: Roger Pau Monne |Date: Thu, 28 Sep 2023 12:22:35 +0200 |Subject: [PATCH 11/11] libxl: limit bootloader execution in restricted mode |MIME-Version: 1.0 |Content-Type: text/plain; charset=UTF-8 |Content-Transfer-Encoding: 8bit | |Introduce a timeout for bootloader execution when running in restricted mode. | |Allow overwriting the default time out with an environment provided value. | |This is part of XSA-443 / CVE-2023-34325 | |Signed-off-by: Roger Pau Monné |Reviewed-by: Anthony PERARD |--- | docs/man/xl.1.pod.in | 8 ++++++ | tools/libs/light/libxl_bootloader.c | 40 +++++++++++++++++++++++++++++ | tools/libs/light/libxl_internal.h | 2 ++ | 3 files changed, 50 insertions(+) | |diff --git a/docs/man/xl.1.pod.in b/docs/man/xl.1.pod.in |index 96e6fb1c32a3..8f056450a730 100644 |--- docs/man/xl.1.pod.in.orig |+++ docs/man/xl.1.pod.in -------------------------- Patching file docs/man/xl.1.pod.in using Plan A... Hunk #1 succeeded at 2007. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libs/light/libxl_bootloader.c b/tools/libs/light/libxl_bootloader.c |index 97d9bf4ddc0a..3ca6463e5f63 100644 |--- tools/libs/light/libxl_bootloader.c.orig |+++ tools/libs/light/libxl_bootloader.c -------------------------- Patching file tools/libs/light/libxl_bootloader.c using Plan A... Hunk #1 succeeded at 34. Hunk #2 succeeded at 303. Hunk #3 succeeded at 321. Hunk #4 succeeded at 383. Hunk #5 succeeded at 646. Hunk #6 succeeded at 730. Hunk #7 succeeded at 761. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/tools/libs/light/libxl_internal.h b/tools/libs/light/libxl_internal.h |index 8415d1feed16..a9581289f462 100644 |--- tools/libs/light/libxl_internal.h.orig |+++ tools/libs/light/libxl_internal.h -------------------------- Patching file tools/libs/light/libxl_internal.h using Plan A... Hunk #1 succeeded at 103. Hunk #2 succeeded at 3739. Hmm... Ignoring the trailing garbage. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-config_FreeBSD.mk => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-config_FreeBSD.mk Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-config_FreeBSD.mk,v 1.1 2025/03/31 11:32:05 sborrill Exp $ | |Align paths on FreeBSD with pkgsrc | |--- config/FreeBSD.mk.orig 2025-03-28 08:57:55.905441000 +0000 |+++ config/FreeBSD.mk 2025-03-28 08:58:37.291735000 +0000 -------------------------- Patching file config/FreeBSD.mk using Plan A... Hunk #1 succeeded at 2. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_man_xl.1.pod.in => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_man_xl.1.pod.in Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-docs_man_xl.1.pod.in,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- docs/man/xl.1.pod.in.orig 2021-04-06 19:14:18.000000000 +0200 |+++ docs/man/xl.1.pod.in 2021-04-17 13:34:37.085288645 +0200 -------------------------- Patching file docs/man/xl.1.pod.in using Plan A... Hunk #1 succeeded at 33. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_man_xl.cfg.5.pod.in => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_man_xl.cfg.5.pod.in Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-docs_man_xl.cfg.5.pod.in,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- docs/man/xl.cfg.5.pod.in.orig 2018-04-17 19:21:31.000000000 +0200 |+++ docs/man/xl.cfg.5.pod.in 2018-04-23 16:14:18.000000000 +0200 -------------------------- Patching file docs/man/xl.cfg.5.pod.in using Plan A... Hunk #1 succeeded at 4. Hunk #2 succeeded at 2894 (offset 271 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_man_xlcpupool.cfg.5.pod => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_man_xlcpupool.cfg.5.pod Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-docs_man_xlcpupool.cfg.5.pod,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- docs/man/xlcpupool.cfg.5.pod.orig 2017-03-24 17:41:23.000000000 +0100 |+++ docs/man/xlcpupool.cfg.5.pod 2017-03-24 17:41:50.000000000 +0100 -------------------------- Patching file docs/man/xlcpupool.cfg.5.pod using Plan A... Hunk #1 succeeded at 4. Hunk #2 succeeded at 117. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_misc_block-scripts.txt => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_misc_block-scripts.txt Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-docs_misc_block-scripts.txt,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- ./docs/misc/block-scripts.txt.orig 2018-04-23 16:23:34.000000000 +0200 |+++ ./docs/misc/block-scripts.txt 2018-04-23 16:23:39.000000000 +0200 -------------------------- Patching file ./docs/misc/block-scripts.txt using Plan A... Hunk #1 succeeded at 18. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_misc_vtd.txt => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-docs_misc_vtd.txt Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-docs_misc_vtd.txt,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- docs/misc/vtd.txt.orig 2020-05-08 16:46:26.400241453 +0200 |+++ docs/misc/vtd.txt 2020-05-08 16:46:50.253734556 +0200 -------------------------- Patching file docs/misc/vtd.txt using Plan A... Hunk #1 succeeded at 39. Hunk #2 succeeded at 77. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/Makefile.orig 2020-12-08 15:50:17.000000000 +0100 |+++ tools/Makefile 2020-12-09 15:44:35.415904040 +0100 -------------------------- Patching file tools/Makefile using Plan A... Hunk #1 succeeded at 34. Hunk #2 succeeded at 247. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_configure => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_configure Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_configure,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/configure.orig 2020-12-08 15:54:42.000000000 +0100 |+++ tools/configure 2020-12-09 15:47:21.690205178 +0100 -------------------------- Patching file tools/configure using Plan A... Hunk #1 succeeded at 2454 (offset 10 lines). Hunk #2 succeeded at 3896 (offset 2 lines). Hunk #3 succeeded at 10888 (offset 175 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_console_daemon_utils.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_console_daemon_utils.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_console_daemon_utils.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/console/daemon/utils.c.orig 2020-12-08 15:28:31.000000000 +0100 |+++ tools/console/daemon/utils.c 2020-12-09 16:22:49.947276738 +0100 -------------------------- Patching file tools/console/daemon/utils.c using Plan A... Hunk #1 succeeded at 107. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_examples_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_examples_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_examples_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/examples/Makefile.orig 2021-01-10 21:34:35.490019719 +0100 |+++ tools/examples/Makefile 2021-01-10 21:35:00.852608954 +0100 -------------------------- Patching file tools/examples/Makefile using Plan A... Hunk #1 succeeded at 1. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_firmware_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_firmware_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_firmware_Makefile,v 1.2 2023/08/24 10:27:09 bouyer Exp $ | |--- tools/firmware/Makefile.orig 2020-05-14 14:19:32.000000000 +0200 |+++ tools/firmware/Makefile 2020-08-26 19:39:04.950176746 +0200 -------------------------- Patching file tools/firmware/Makefile using Plan A... Hunk #1 succeeded at 24. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_firmware_etherboot_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_firmware_etherboot_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_firmware_etherboot_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/firmware/etherboot/Makefile.orig 2019-12-17 15:23:09.000000000 +0100 |+++ tools/firmware/etherboot/Makefile 2020-05-08 16:59:46.337172477 +0200 -------------------------- Patching file tools/firmware/etherboot/Makefile using Plan A... Hunk #1 succeeded at 32. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_hotplug_NetBSD_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_hotplug_NetBSD_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_hotplug_NetBSD_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/hotplug/NetBSD/Makefile.orig 2021-02-03 15:23:25.000000000 +0100 |+++ tools/hotplug/NetBSD/Makefile 2021-02-03 15:28:32.949717159 +0100 -------------------------- Patching file tools/hotplug/NetBSD/Makefile using Plan A... Hunk #1 succeeded at 10. Hunk #2 succeeded at 26. Hunk #3 succeeded at 44. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_hotplug_NetBSD_block => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_hotplug_NetBSD_block Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_hotplug_NetBSD_block,v 1.1 2022/05/30 09:09:34 bouyer Exp $ | |work around an issue in NetBSD 9.99.x kernel: pass the vnd name to vnconfig, |not the path to the block device. | |--- tools/hotplug/NetBSD/block.orig 2022-01-31 10:42:09.000000000 +0100 |+++ tools/hotplug/NetBSD/block 2022-05-30 10:50:42.821527086 +0200 -------------------------- Patching file tools/hotplug/NetBSD/block using Plan A... Hunk #1 succeeded at 64. Hunk #2 succeeded at 74. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_hotplug_common_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_hotplug_common_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_hotplug_common_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/hotplug/common/Makefile.orig 2018-04-17 19:21:31.000000000 +0200 |+++ tools/hotplug/common/Makefile 2018-04-23 16:03:55.000000000 +0200 -------------------------- Patching file tools/hotplug/common/Makefile using Plan A... Hunk #1 succeeded at 26. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_include_xen-sys_NetBSD_evtchn.h => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_include_xen-sys_NetBSD_evtchn.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_include_xen-sys_NetBSD_evtchn.h,v 1.2 2021/04/18 19:42:19 bouyer Exp $ | |Use system-provided headers instead of local, outdated definitions | |--- tools/include/xen-sys/NetBSD/evtchn.h.orig 2021-04-17 13:48:20.754547947 +0200 |+++ tools/include/xen-sys/NetBSD/evtchn.h 2021-04-17 13:51:39.136816295 +0200 -------------------------- Patching file tools/include/xen-sys/NetBSD/evtchn.h using Plan A... Hunk #1 succeeded at 2. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_include_xen-sys_NetBSD_privcmd.h => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_include_xen-sys_NetBSD_privcmd.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_include_xen-sys_NetBSD_privcmd.h,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |Use system-provided headers instead of local, outdated definitions | |--- tools/include/xen-sys/NetBSD/privcmd.h.orig 2021-04-17 13:48:20.759557127 +0200 |+++ tools/include/xen-sys/NetBSD/privcmd.h 2021-04-17 13:53:28.776879861 +0200 -------------------------- Patching file tools/include/xen-sys/NetBSD/privcmd.h using Plan A... Hunk #1 succeeded at 1. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_call_libxencall.map => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_call_libxencall.map Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_call_libxencall.map,v 1.1 2025/03/31 11:32:05 sborrill Exp $ | |Fix build on FreeBSD | |--- tools/libs/call/libxencall.map.orig 2023-08-07 13:08:26.000000000 +0100 |+++ tools/libs/call/libxencall.map 2025-03-28 08:34:13.697578000 +0000 -------------------------- Patching file tools/libs/call/libxencall.map using Plan A... Hunk #1 succeeded at 9. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_ctrl_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_ctrl_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_ctrl_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |PKG_CONFIG is an environnement variable, rename to PKG_CONFIG_PC | |--- tools/libs/ctrl/Makefile.orig 2020-12-09 18:39:19.902854035 +0100 |+++ tools/libs/ctrl/Makefile 2020-12-09 18:39:37.171930411 +0100 -------------------------- Patching file tools/libs/ctrl/Makefile using Plan A... Hunk #1 succeeded at 51 (offset 1 line). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_libs.mk => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_libs.mk Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_libs.mk,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |PKG_CONFIG is defined in environnement, rename to PKG_CONFIG_PC | |--- tools/libs/libs.mk.orig 2021-04-06 19:14:18.000000000 +0200 |+++ tools/libs/libs.mk 2021-04-17 13:40:31.365641659 +0200 -------------------------- Patching file tools/libs/libs.mk using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 29. Hunk #3 succeeded at 38. Hunk #4 succeeded at 112. Hunk #5 succeeded at 132. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_light_libxl.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_light_libxl.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_light_libxl.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |error: array subscript has type 'char' [-Werror=char-subscripts] | |--- tools/libs/light/libxl.c.orig 2021-04-17 22:11:04.304715386 +0200 |+++ tools/libs/light/libxl.c 2021-04-17 22:12:29.062613549 +0200 -------------------------- Patching file tools/libs/light/libxl.c using Plan A... Hunk #1 succeeded at 673. Hunk #2 succeeded at 703. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_light_libxl_pci.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_light_libxl_pci.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_light_libxl_pci.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |error: array subscript has type 'char' [-Werror=char-subscripts] | |--- tools/libs/light/libxl_pci.c.orig 2021-04-17 22:15:01.075399964 +0200 |+++ tools/libs/light/libxl_pci.c 2021-04-17 22:15:30.482517194 +0200 -------------------------- Patching file tools/libs/light/libxl_pci.c using Plan A... Hunk #1 succeeded at 779 (offset 2 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_util_libxlu_pci.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_util_libxlu_pci.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_util_libxlu_pci.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |error: array subscript has type 'char' [-Werror=char-subscripts] | |--- ./tools/libs/util/libxlu_pci.c.orig 2021-04-17 22:17:52.998629860 +0200 |+++ ./tools/libs/util/libxlu_pci.c 2021-04-17 22:18:06.194127140 +0200 -------------------------- Patching file ./tools/libs/util/libxlu_pci.c using Plan A... Hunk #1 succeeded at 19. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_xenstore_xenstored_control.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libs_xenstore_xenstored_control.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libs_xenstore_xenstored_control.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |error: array subscript has type 'char' [-Werror=char-subscripts] | |--- tools/xenstore/xenstored_control.c.orig 2021-04-17 22:20:28.658953461 +0200 |+++ tools/xenstore/xenstored_control.c 2021-04-17 22:20:41.265121523 +0200 -------------------------- Patching file tools/xenstore/xenstored_control.c using Plan A... Hunk #1 succeeded at 710 (offset 109 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libxl_libxl_dom.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libxl_libxl_dom.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_libxl_dom.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/libs/light/libxl_dom.c.orig 2020-12-08 15:28:31.000000000 +0100 |+++ tools/libs/light/libxl_dom.c 2020-12-09 15:59:56.104509990 +0100 -------------------------- Patching file tools/libs/light/libxl_dom.c using Plan A... Hunk #1 succeeded at 1230 (offset 2 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libxl_libxl_event.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libxl_libxl_event.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_libxl_event.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |The SIGCHLD handler just writes to a pipe where the reader is the |same process. The idea is that this will cause poll(2) in the main |thread to exit with the reaper pipe readable, and do child cleanup here. | |Unfortunably, is the child also has a write pipe back to the |parent (as e.g. with pygrub), the loop in afterpoll_internal() may see the |POLLHUP event on this pipe before the POLLIN even on the reaper pipe, and |this will be considered as an error (from e.g. pygrub). | |work around by filtering POLLHUP events here | |--- tools/libs/light/libxl_event.c.orig 2020-12-08 15:28:31.000000000 +0100 |+++ tools/libs/light/libxl_event.c 2020-12-09 16:00:48.840221028 +0100 -------------------------- Patching file tools/libs/light/libxl_event.c using Plan A... Hunk #1 succeeded at 1443. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libxl_libxl_internal.h => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_libxl_libxl_internal.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_libxl_libxl_internal.h,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |bump some timeouts to more reasonable values. 40s is not enough |if there is lots of them (e.g lots of network interfaces) and they |need to be serialized. | |--- tools/libs/light/libxl_internal.h.orig 2020-12-08 15:28:31.000000000 +0100 |+++ tools/libs/light/libxl_internal.h 2020-12-09 16:01:49.819103324 +0100 -------------------------- Patching file tools/libs/light/libxl_internal.h using Plan A... Hunk #1 succeeded at 93. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_misc_xenhypfs.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_misc_xenhypfs.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_misc_xenhypfs.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |error: array subscript has type 'char' [-Werror=char-subscripts] | |--- tools/misc/xenhypfs.c.orig 2021-04-17 22:22:30.893118826 +0200 |+++ tools/misc/xenhypfs.c 2021-04-17 22:23:04.525580088 +0200 -------------------------- Patching file tools/misc/xenhypfs.c using Plan A... Hunk #1 succeeded at 22. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_common.make => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_common.make Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_common.make,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |Handle ocaml-findlib 1.7.3 already appending destdir | |--- tools/ocaml/common.make.orig 2020-12-08 15:28:31.000000000 +0100 |+++ tools/ocaml/common.make 2021-01-09 19:27:02.447285099 +0100 -------------------------- Patching file tools/ocaml/common.make using Plan A... Hunk #1 succeeded at 3. Hunk #2 succeeded at 17. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_libs_xc_xenctrl_stubs.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_libs_xc_xenctrl_stubs.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_libs_xc_xenctrl_stubs.c,v 1.1 2022/06/09 17:11:27 bouyer Exp $ | |avoid xenctrl_stubs.c:46: error: "Val_none" redefined [-Werror] | |--- ./tools/ocaml/libs/xc/xenctrl_stubs.c.orig 2022-06-09 18:27:02.969197078 +0200 |+++ ./tools/ocaml/libs/xc/xenctrl_stubs.c 2022-06-09 18:27:19.448183361 +0200 -------------------------- Patching file ./tools/ocaml/libs/xc/xenctrl_stubs.c using Plan A... Hunk #1 succeeded at 43. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_libs_xentoollog_xentoollog_stubs.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_libs_xentoollog_xentoollog_stubs.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_libs_xentoollog_xentoollog_stubs.c,v 1.1 2022/06/09 17:11:27 bouyer Exp $ | |Avoid xentoollog_stubs.c:57: error: "Some_val" redefined [-Werror] | |--- ./tools/ocaml/libs/xentoollog/xentoollog_stubs.c.orig 2022-01-31 10:42:09.000000000 +0100 |+++ ./tools/ocaml/libs/xentoollog/xentoollog_stubs.c 2022-06-09 18:22:10.699889986 +0200 -------------------------- Patching file ./tools/ocaml/libs/xentoollog/xentoollog_stubs.c using Plan A... Hunk #1 succeeded at 53. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_libs_xl_xenlight_stubs.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_libs_xl_xenlight_stubs.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_libs_xl_xenlight_stubs.c,v 1.1 2022/06/09 17:11:27 bouyer Exp $ | |avoid xenlight_stubs.c:231: error: "Some_val" redefined [-Werror] | |--- ./tools/ocaml/libs/xl/xenlight_stubs.c.orig 2022-06-09 18:29:38.816998959 +0200 |+++ ./tools/ocaml/libs/xl/xenlight_stubs.c 2022-06-09 18:30:07.080850306 +0200 -------------------------- Patching file ./tools/ocaml/libs/xl/xenlight_stubs.c using Plan A... Hunk #1 succeeded at 227. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_xenstored_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_xenstored_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_xenstored_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/ocaml/xenstored/Makefile.orig 2016-02-09 14:44:19.000000000 +0000 |+++ tools/ocaml/xenstored/Makefile -------------------------- Patching file tools/ocaml/xenstored/Makefile using Plan A... Hunk #1 succeeded at 1. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_xenstored_utils.ml => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_ocaml_xenstored_utils.ml Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_ocaml_xenstored_utils.ml,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/ocaml/xenstored/utils.ml.orig 2021-01-10 18:02:05.000000000 +0100 |+++ tools/ocaml/xenstored/utils.ml 2021-01-10 20:20:53.433611357 +0100 -------------------------- Patching file tools/ocaml/xenstored/utils.ml using Plan A... Hunk #1 succeeded at 86. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_pygrub_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_pygrub_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_pygrub_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/pygrub/Makefile.orig 2020-12-14 15:48:30.300876169 +0100 |+++ tools/pygrub/Makefile 2020-12-14 15:48:47.821580386 +0100 -------------------------- Patching file tools/pygrub/Makefile using Plan A... Hunk #1 succeeded at 3. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_python_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_python_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_python_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/python/Makefile.orig 2020-12-14 15:32:06.314547060 +0100 |+++ tools/python/Makefile 2020-12-14 15:33:29.005101260 +0100 -------------------------- Patching file tools/python/Makefile using Plan A... Hunk #1 succeeded at 5. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen-traditional/Makefile.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/Makefile 2015-01-19 14:16:12.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/Makefile using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 232 (offset 1 line). Hunk #3 succeeded at 276 (offset 1 line). Hunk #4 succeeded at 285 (offset 1 line). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_block-raw-posix.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_block-raw-posix.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_block-raw-posix.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |- if given a block device, use the character device instead. | |--- tools/qemu-xen-traditional/block-raw-posix.c.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/block-raw-posix.c 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/block-raw-posix.c using Plan A... Hunk #1 succeeded at 65. Hunk #2 succeeded at 73. Hunk #3 succeeded at 1017 (offset 1 line). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_configure => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_configure Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_configure,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen-traditional/configure.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/configure 2015-01-20 22:58:07.000000000 +0100 -------------------------- Patching file tools/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 /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_e1000.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_e1000.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_e1000.c,v 1.1 2021/04/18 12:31:26 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 | |--- tools/qemu-xen-traditional/hw/e1000.c.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/e1000.c 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/e1000.c using Plan A... Hunk #1 succeeded at 265. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_ide.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_ide.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_ide.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/ide.c.orig 2014-01-09 13:44:42.000000000 +0100 |+++ tools/qemu-xen-traditional/hw/ide.c 2015-06-11 16:15:49.000000000 +0200 -------------------------- Patching file tools/qemu-xen-traditional/hw/ide.c using Plan A... Hunk #1 succeeded at 757. Hunk #2 succeeded at 817. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_pass-through.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_pass-through.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_pass-through.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/pass-through.c.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/pass-through.c 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/pass-through.c using Plan A... Hunk #1 succeeded at 84. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_pt-graphics.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_pt-graphics.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_pt-graphics.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/pt-graphics.c.orig 2015-01-19 16:14:46.000000000 +0100 |+++ tools/qemu-xen-traditional/hw/pt-graphics.c 2015-01-19 16:14:51.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/pt-graphics.c using Plan A... Hunk #1 succeeded at 4. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_pt-msi.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_pt-msi.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_pt-msi.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/pt-msi.c.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/pt-msi.c 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/pt-msi.c using Plan A... Hunk #1 succeeded at 22. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_pt-msi.h => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_hw_pt-msi.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_hw_pt-msi.h,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen-traditional/hw/pt-msi.h.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/hw/pt-msi.h 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/hw/pt-msi.h using Plan A... Hunk #1 succeeded at 1. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_i386-dm_hookstarget.mak => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_i386-dm_hookstarget.mak Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_i386-dm_hookstarget.mak,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen-traditional/i386-dm/hookstarget.mak.orig 2014-10-06 17:50:24.000000000 +0200 |+++ tools/qemu-xen-traditional/i386-dm/hookstarget.mak 2015-01-19 13:16:38.000000000 +0100 -------------------------- Patching file tools/qemu-xen-traditional/i386-dm/hookstarget.mak using Plan A... Hunk #1 succeeded at 2. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_net.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_net.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_net.c,v 1.2 2022/05/13 16:04:23 wiz Exp $ | | |--- tools/qemu-xen-traditional/net.c.orig 2016-11-29 17:36:38.000000000 +0100 |+++ tools/qemu-xen-traditional/net.c 2017-03-29 18:16:54.000000000 +0200 -------------------------- Patching file tools/qemu-xen-traditional/net.c using Plan A... Hunk #1 succeeded at 990. Hunk #2 succeeded at 1029. Hunk #3 succeeded at 1050. Hunk #4 succeeded at 1969. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_xen-hooks.mak => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen-traditional_xen-hooks.mak Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen-traditional_xen-hooks.mak,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |enable PCI passthrough when pciutils is present | |--- tools/qemu-xen-traditional/xen-hooks.mak.orig 2020-12-08 16:54:20.000000000 +0100 |+++ tools/qemu-xen-traditional/xen-hooks.mak 2020-12-09 16:07:04.817171636 +0100 -------------------------- Patching file tools/qemu-xen-traditional/xen-hooks.mak using Plan A... Hunk #1 succeeded at 61. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen_audio_audio.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen_audio_audio.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen_audio_audio.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen/audio/audio.c.orig 2020-12-08 16:58:46.000000000 +0100 |+++ tools/qemu-xen/audio/audio.c 2020-12-09 16:09:37.068801135 +0100 -------------------------- Patching file tools/qemu-xen/audio/audio.c using Plan A... Hunk #1 succeeded at 890. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen_configure => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen_configure Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen_configure,v 1.2 2021/09/22 18:40:43 bouyer Exp $ | |-lrt is needed for shm_open() |-stopgap measure to make the package build on HEAD: ignore eventfd | |--- tools/qemu-xen/configure.orig 2021-04-07 17:38:52.000000000 +0200 |+++ tools/qemu-xen/configure 2021-09-22 19:09:30.727151120 +0200 -------------------------- Patching file tools/qemu-xen/configure using Plan A... Hunk #1 succeeded at 851. Hunk #2 succeeded at 4780. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen_net_tap-bsd.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen_net_tap-bsd.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen_net_tap-bsd.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/qemu-xen/net/tap-bsd.c.orig 2020-05-18 10:41:00.816005830 +0200 |+++ tools/qemu-xen/net/tap-bsd.c 2020-05-18 15:02:30.497691415 +0200 -------------------------- Patching file tools/qemu-xen/net/tap-bsd.c using Plan A... Hunk #1 succeeded at 39 (offset -1 lines). Hunk #2 succeeded at 111 (offset -1 lines). Hunk #3 succeeded at 136 (offset -1 lines). Hunk #4 succeeded at 153 (offset -1 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen_net_tap.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_qemu-xen_net_tap.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_qemu-xen_net_tap.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |From Roman Shaposhnik via xen-devel: pass bridge name to ifup script | |--- tools/qemu-xen/net/tap.c.orig |+++ tools/qemu-xen/net/tap.c -------------------------- Patching file tools/qemu-xen/net/tap.c using Plan A... Hunk #1 succeeded at 63 (offset 1 line). Hunk #2 succeeded at 301 (offset 1 line). Hunk #3 succeeded at 398 (offset 1 line). Hunk #4 succeeded at 423 (offset 1 line). Hunk #5 succeeded at 613 (offset 5 lines). Hunk #6 succeeded at 631 (offset 1 line). Hunk #7 succeeded at 950 (offset 31 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_xenpaging_xenpaging.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_xenpaging_xenpaging.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_xenpaging_xenpaging.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |Fix "error: 'buffer' may be used uninitialized" | |--- tools/xenpaging/xenpaging.c.orig 2021-04-17 14:43:41.053494277 +0200 |+++ tools/xenpaging/xenpaging.c 2021-04-17 14:44:17.167271008 +0200 -------------------------- Patching file tools/xenpaging/xenpaging.c using Plan A... Hunk #1 succeeded at 180. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_xenstore_xs_lib.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_xenstore_xs_lib.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_xenstore_xs_lib.c,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/xenstore/xs_lib.c.orig |+++ tools/xenstore/xs_lib.c -------------------------- Patching file tools/xenstore/xs_lib.c using Plan A... Hunk #1 succeeded at 52. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_xl_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-tools_xl_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_xl_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |--- tools/xl/Makefile.orig 2021-01-26 12:35:19.000000000 +0100 |+++ tools/xl/Makefile 2021-01-26 19:21:03.038848363 +0100 -------------------------- Patching file tools/xl/Makefile using Plan A... Hunk #1 succeeded at 43. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-xen_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/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 2021/04/18 12:31:26 bouyer Exp $ | |Use a more strict pattern; on NetBSD it includes some extra compiler |outputs. | |--- xen/Makefile.orig 2020-12-10 16:06:07.432987067 +0100 |+++ xen/Makefile 2020-12-10 16:06:10.485550293 +0100 -------------------------- Patching file xen/Makefile using Plan A... Hunk #1 succeeded at 415 (offset 4 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-xen_Rules.mk => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/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 2021/04/18 12:31:26 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 5 (offset 4 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-xen_arch_x86_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-xen_arch_x86_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-xen_arch_x86_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |also filter out flags added by pkgsrc | |--- xen/arch/x86/Makefile.orig 2020-12-11 18:09:56.686501836 +0100 |+++ xen/arch/x86/Makefile 2020-12-11 18:10:47.737620837 +0100 -------------------------- Patching file xen/arch/x86/Makefile using Plan A... Hunk #1 succeeded at 267 (offset 15 lines). done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-xen_common_libelf_libelf-loader.c => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-xen_common_libelf_libelf-loader.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-xen_common_libelf_libelf-loader.c,v 1.1 2024/04/02 22:01:23 bouyer Exp $ | |Compute total symbol table with the same size as used to build the |symbol table. |This bug only shows up with 32bit guest kernels, and if the end of the |symbol table ends less than 64 bytes from a page boundary. When this |happens the string table is not copied, and the guest sees all symbols with |empty names. | |--- xen/common/libelf/libelf-loader.c.orig 2023-11-16 22:44:21.000000000 +0100 |+++ xen/common/libelf/libelf-loader.c 2024-04-02 17:12:05.322638541 +0200 -------------------------- Patching file xen/common/libelf/libelf-loader.c using Plan A... Hunk #1 succeeded at 204. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-xen_include_Makefile => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/sysutils/xentools415/patches/patch-xen_include_Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-xen_include_Makefile,v 1.1 2021/04/18 12:31:26 bouyer Exp $ | |also filter out flags added by pkgsrc | |--- xen/include/Makefile.orig 2020-12-10 17:08:48.270718042 +0100 |+++ xen/include/Makefile 2020-12-10 17:11:56.553825047 +0100 -------------------------- Patching file xen/include/Makefile using Plan A... Hunk #1 succeeded at 57. done ===> Creating toolchain wrappers for xentools415-4.15.5nb4 ===> Configuring for xentools415-4.15.5nb4 => Substituting "conf" in docs/misc/block-scripts.txt docs/misc/vtd.txt => Fixing getopt_long_only => Fixing rpath-link syntax => 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 tools/misc/xencons tools/misc/xenpvnetboot tools/misc/xensymoops tools/python/scripts/convert-legacy-stream tools/python/scripts/verify-stream-v2 tools/xenmon/xenmon.py tools/misc/xencov_split. => Replacing Perl interpreter in 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. => Checking for portability problems in extracted files configure: WARNING: unrecognized options: --enable-rpath, --disable-golang checking build system type... x86_64--netbsd checking host system type... x86_64--netbsd Will build the following subsystems: xen tools stubdom docs configure: creating ./config.status config.status: creating config/Toplevel.mk config.status: creating config/Paths.mk === configuring in tools (/tmp/sysutils/xentools415/work/xen-4.15.5/tools) configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr/pkg' '--enable-rpath' '--disable-golang' '--sysconfdir=/usr/pkg/etc' '--x-includes=/usr/X11R7/include' '--x-libraries=/usr/X11R7/lib' '--build=x86_64--netbsd' '--host=x86_64--netbsd' '--mandir=/usr/pkg/man' '--enable-option-checking=yes' 'build_alias=x86_64--netbsd' 'host_alias=x86_64--netbsd' --cache-file=/dev/null --srcdir=. 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... gcc 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 gcc accepts -g... yes checking for gcc 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 as86... /usr/pkg/bin/as86 checking for ld86... /usr/pkg/bin/ld86 checking for bcc... /usr/pkg/bin/bcc checking for lzma_version_number in -llzma... yes checking for x86_64--netbsd-gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc 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 pbulk -g wheel checking for flex... /usr/bin/flex checking for abi-dumper... no checking for perl... /usr/pkg/bin/perl checking for awk... /usr/bin/awk checking for x86_64--netbsd-ocamlc... no checking for ocamlc... ocamlc OCaml version is 4.14.2 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... /tmp/sysutils/xentools415/work/.tools/bin/bash checking for python3.12... /usr/pkg/bin/python3.12 checking for python version >= 2.6 ... yes checking how to run the C preprocessor... gcc -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 python3.12-config... /usr/pkg/bin/python3.12-config checking Python.h usability... yes checking Python.h presence... yes checking for Python.h... yes checking for PyArg_ParseTuple... yes checking whether Python setup.py brokenly enables -D_FORTIFY_SOURCE... no 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 pixman... yes checking for wget... no checking for false... (cached) false checking for ftp... /tmp/sysutils/xentools415/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 libzstd... 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 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 argp.h usability... yes checking argp.h presence... yes checking for argp.h... yes checking for argp_usage in -largp... yes 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 and COLO. Please install libnl3 libraries (including libnl3-route), command line tools and devel headers - version 3.2.8 or higher checking for SYSTEMD... no checking for SYSTEMD... no checking for bison... /tmp/sysutils/xentools415/work/.tools/bin/bison checking endian.h usability... yes checking endian.h presence... yes checking for endian.h... yes 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/FreeBSD/rc.d/xendriverdomain config.status: creating hotplug/Linux/init.d/sysconfig.xencommons config.status: creating hotplug/Linux/init.d/sysconfig.xendomains 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/init.d/xendriverdomain config.status: creating hotplug/Linux/launch-xenstore config.status: creating hotplug/Linux/vif-setup 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 hotplug/NetBSD/rc.d/xendriverdomain config.status: creating ocaml/xenstored/oxenstored.conf config.status: creating config.h === configuring in stubdom (/tmp/sysutils/xentools415/work/xen-4.15.5/stubdom) configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr/pkg' '--enable-rpath' '--disable-golang' '--sysconfdir=/usr/pkg/etc' '--x-includes=/usr/X11R7/include' '--x-libraries=/usr/X11R7/lib' '--build=x86_64--netbsd' '--host=x86_64--netbsd' '--mandir=/usr/pkg/man' '--enable-option-checking=yes' 'build_alias=x86_64--netbsd' 'host_alias=x86_64--netbsd' --cache-file=/dev/null --srcdir=. configure: WARNING: unrecognized options: --enable-rpath, --disable-golang checking build system type... x86_64--netbsd checking host system type... x86_64--netbsd xyy checking for wget... no checking for false... (cached) false checking for ftp... /tmp/sysutils/xentools415/work/.tools/bin/ftp checking for x86_64--netbsd-gcc... gcc 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 gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c -o pbulk -g wheel checking for cmake... /tmp/sysutils/xentools415/work/.tools/bin/cmake Will build the following stub domains: pv-grub xenstore-stubdom xenstorepvh-stubdom vtpm-stubdom vtpmmgr-stubdom ioemu-stubdom configure: creating ./config.status config.status: creating ../config/Stubdom.mk configure: WARNING: unrecognized options: --enable-rpath, --disable-golang === configuring in docs (/tmp/sysutils/xentools415/work/xen-4.15.5/docs) configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr/pkg' '--enable-rpath' '--disable-golang' '--sysconfdir=/usr/pkg/etc' '--x-includes=/usr/X11R7/include' '--x-libraries=/usr/X11R7/lib' '--build=x86_64--netbsd' '--host=x86_64--netbsd' '--mandir=/usr/pkg/man' '--enable-option-checking=yes' 'build_alias=x86_64--netbsd' 'host_alias=x86_64--netbsd' --cache-file=/dev/null --srcdir=. configure: WARNING: unrecognized options: --enable-rpath, --disable-golang checking for fig2dev... no configure: WARNING: fig2dev is not available so some documentation won't be built checking for pod2man... /tmp/sysutils/xentools415/work/.tools/bin/pod2man checking for pod2html... /usr/pkg/bin/pod2html checking for pod2text... /usr/pkg/bin/pod2text checking for pandoc... no configure: WARNING: pandoc is not available so some documentation won't be built checking for perl... /usr/pkg/bin/perl configure: creating ./config.status config.status: creating ../config/Docs.mk config.status: creating man/xl.cfg.5.pod config.status: creating man/xl.1.pod config.status: creating man/xl-disk-configuration.5.pod config.status: creating man/xl-network-configuration.5.pod config.status: creating man/xl.conf.5.pod configure: WARNING: unrecognized options: --enable-rpath, --disable-golang configure: WARNING: unrecognized options: --enable-rpath, --disable-golang