+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/p5-IO-AIO-4.76/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/p5-IO-AIO-4.76/work.log
=> Bootstrap dependency digest>=20211023: found digest-20220214
=> Checksum BLAKE2s OK for IO-AIO-4.76.tar.gz
=> Checksum SHA512 OK for IO-AIO-4.76.tar.gz
===> Installing dependencies for p5-IO-AIO-4.76
=> Tool dependency mktools-[0-9]*: found mktools-20220614
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency p5-Canary-Stability-[0-9]*: found p5-Canary-Stability-2013nb2
=> Full dependency p5-common-sense-[0-9]*: found p5-common-sense-3.75nb2
=> Full dependency perl>=5.34.0<5.36.0: found perl-5.34.1
===> Overriding tools for p5-IO-AIO-4.76
===> Extracting for p5-IO-AIO-4.76
===> Patching for p5-IO-AIO-4.76
===> Creating toolchain wrappers for p5-IO-AIO-4.76
===> Configuring for p5-IO-AIO-4.76
=> Checking for portability problems in extracted files

***
*** Canary::Stability COMPATIBILITY AND SUPPORT CHECK
*** =================================================
***
*** Hi!
***
*** I do my best to provide predictable and reliable software.
***
*** However, in recent releases, P5P (who maintain perl) have been
*** introducing regressions that are sometimes subtle and at other times
*** catastrophic, often for personal preferences with little or no concern
*** for existing code, most notably CPAN.
***
*** For this reason, it has become very hard for me to maintain the level
*** of reliability and support I have committed myself to in the past, at
*** least with some perl versions: I simply can't keep up working around new
*** bugs or gratituous incompatibilities, and in turn you might suffer from
*** unanticipated problems.
***
*** Therefore I have introduced a support and compatibility check, the results
*** of which follow below, together with a FAQ and some recommendations.
***
*** This check is just to let you know that there might be a risk, so you can
*** make judgement calls on how to proceed - it will not keep the module from
*** installing or working.
***
*** The stability canary says: (nothing, it was driven away by harsh weather)
***
*** It seems you are running perl version 5.034001, likely the "official" or
*** "standard" version. While there is nothing wrong with doing that,
*** standard perl versions 5.022 and up are not supported by IO::AIO.
*** While this might be fatal, it might also be all right - if you run into
*** problems, you might want to downgrade your perl or switch to the
*** stability branch.
***
*** If everything works fine, you can ignore this message.
***
***
*** Stability canary mini-FAQ:
***
*** Do I need to do anything?
***    With luck, no. While some distributions are known to fail
***    already, most should probably work. This message is here
***    to alert you that your perl is not supported by IO::AIO,
***    and if things go wrong, you either need to downgrade, or
***    sidegrade to the stability variant of your perl version,
***    or simply live with the consequences.
***
*** What is this canary thing?
***    It's purpose is to check support status of IO::AIO with
***    respect to your perl version.
***
*** What is this "stability branch"?
***    It's a branch or fork of the official perl, by schmorp, to
***    improve stability and compatibility with existing modules.
***
*** How can I skip this prompt on automated installs?
***    Set PERL_CANARY_STABILITY_NOPROMPT=1 in your environment.
***    More info is in the Canary::Stability manpage.
***
*** Long version of this FAQ: http://stableperl.schmorp.de/faq.html
*** Stability Branch homepage: http://stableperl.schmorp.de/
***

Continue anyways?  [y] y
checking for 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 the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for wchar.h... yes
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether _XOPEN_SOURCE should be defined... no
checking for gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking for stdint.h... (cached) yes
checking for sys/syscall.h... yes
checking for sys/prctl.h... no
checking for library containing pthread_create... none required
checking for utimes... yes
checking for futimes... yes
checking for readahead... no
checking for fdatasync... yes
checking for sendfile... no
checking for sync_file_range... no
checking for fallocate... no
checking for sys_syncfs... no
checking for prctl_set_name... no
checking for posix_close... no
checking for renameat2... no
checking for set/getrlimit... yes
checking for posix_madvise... yes
checking for posix_fadvise... yes
checking for linux/fs.h... no
checking for linux/fiemap.h... no
checking for sys/sysmacros.h... yes
checking for sys/mkdev.h... yes
checking for sys/uio.h... yes
checking for siginfo_t... yes
checking for unix-style syscall interface... yes
checking for splice, vmsplice and tee... no
checking for pipe2... yes
checking for eventfd... yes
checking for timerfd_*... yes
checking for memfd_create... no
checking for copy_file_range... no
checking for st_xtimensec... no
checking for st_xtimespec... yes
checking for st_birthtimensec... no
checking for st_birthtimespec... no
checking for st_gen... no
checking for statx... no
checking for accept4... yes
configure: creating ./config.status
config.status: creating config.h
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for IO::AIO
Writing MYMETA.yml and MYMETA.json