pkg/56411: xentools build failure since eventfd support

[prlw1%cam.ac.uk@localhost]

>Number:         56411
>Category:       pkg
>Synopsis:       xentools build failure since eventfd support
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 20 12:40:00 +0000 2021
>Originator:     Patrick Welche
>Release:        pkgsrc-current 2021-Sep-20
>Organization:
>Environment:
NetBSD-9.99.88/amd64
>Description:
Now that NetBSD-current supports eventfd, xentools builds ivshmem-{client,server}. This was checked with xentools413 and xentools415.

A work around for -current users is simply e.g.,


Index: PLIST
===================================================================
RCS file: /cvsroot/pkgsrc/sysutils/xentools415/PLIST,v
retrieving revision 1.1
diff -u -r1.1 PLIST
--- PLIST       18 Apr 2021 12:31:26 -0000      1.1
+++ PLIST       20 Sep 2021 12:33:28 -0000
@@ -301,6 +301,8 @@
 lib/xenfsimage/xfs/fsimage.so
 lib/xenfsimage/zfs/fsimage.so
 libexec/xen/bin/convert-legacy-stream
+libexec/xen/bin/ivshmem-client
+libexec/xen/bin/ivshmem-server
 libexec/xen/bin/libxl-save-helper
 libexec/xen/bin/lsevtchn
 libexec/xen/bin/pygrub


but obviously no good for non-current users.

xen-4.15.0/tools/qemu-xen/configure is a shell script, so also not
easy to simply prevent ivshmem-* from being built, programmatically.

Maybe a blanket

# We can only support ivshmem if we have eventfd
if [ "$eventfd" = "yes" ]; then
  ivshmem=yes
fi

change to ivshmem=no is good enough?


>How-To-Repeat:

>Fix: