>>> Building on exopi-1 under devel/p5-IO-AIO BDEPENDS = [devel/p5-Canary-Stability] DIST = [devel/p5-IO-AIO:IO-AIO-4.8.tar.gz] FULLPKGNAME = p5-IO-AIO-4.80p0 RDEPENDS = [devel/p5-common-sense] (Junk lock obtained for exopi-1 at 1732133309.57) >>> Running depends in devel/p5-IO-AIO at 1732133309.61 last junk was in graphics/xpaint /usr/sbin/pkg_add -aI -Drepair p5-Canary-Stability-2013p0 was: /usr/sbin/pkg_add -aI -Drepair p5-Canary-Stability-2013p0 /usr/sbin/pkg_add -aI -Drepair p5-Canary-Stability-2013p0 >>> Running show-prepare-results in devel/p5-IO-AIO at 1732133311.60 ===> devel/p5-IO-AIO ===> Building from scratch p5-IO-AIO-4.80p0 ===> p5-IO-AIO-4.80p0 depends on: p5-Canary-Stability->=2001 -> p5-Canary-Stability-2013p0 ===> Verifying specs: c perl pthread ===> found c.100.3 perl.24.0 pthread.27.1 p5-Canary-Stability-2013p0 (Junk lock released for exopi-1 at 1732133312.15) distfiles size=189363 >>> Running build in devel/p5-IO-AIO at 1732133312.17 ===> devel/p5-IO-AIO ===> Checking files for p5-IO-AIO-4.80p0 `/exopi-cvs/ports/distfiles/IO-AIO-4.8.tar.gz' is up to date. >> (SHA256) all files: OK ===> Extracting for p5-IO-AIO-4.80p0 ===> Patching for p5-IO-AIO-4.80p0 ===> Applying OpenBSD patch patch-AIO_pm Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |indirect method invocation is deprecated | |Index: AIO.pm |--- AIO.pm.orig |+++ AIO.pm -------------------------- Patching file AIO.pm using Plan A... Hunk #1 succeeded at 26. Hunk #2 succeeded at 931. Hunk #3 succeeded at 970. Hunk #4 succeeded at 1044. Hunk #5 succeeded at 1132. Hunk #6 succeeded at 1140. Hunk #7 succeeded at 1155. Hunk #8 succeeded at 1209. Hunk #9 succeeded at 1226. Hunk #10 succeeded at 1284. Hunk #11 succeeded at 1414. Hunk #12 succeeded at 1563. Hunk #13 succeeded at 1761. Hunk #14 succeeded at 1803. Hunk #15 succeeded at 1874. done ===> Compiler link: clang -> /usr/bin/clang ===> Compiler link: clang++ -> /usr/bin/clang++ ===> Compiler link: cc -> /usr/bin/cc ===> Compiler link: c++ -> /usr/bin/c++ ===> Generating configure for p5-IO-AIO-4.80p0 ===> Configuring for p5-IO-AIO-4.80p0 *** *** 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.038002, 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 If you have problems with deadlocks or crashes on your system, make sure your perl has been linked with -lpthread (you might try LD_PRELOAD=/path/to/libpthread.so as a workaround). Also, pthread support under many BSDs is not the best - before reporting a bug in this module, make sure it's not an OS bug. checking for gcc... cc 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 cc accepts -g... yes checking for cc 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) cc checking whether the compiler supports GNU C... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc 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... -lpthread 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... no checking for linux/fs.h... no checking for linux/fiemap.h... no checking for sys/sysmacros.h... no checking for sys/mkdev.h... no checking for sys/uio.h... yes checking for fexecve... no checking for siginfo_t... yes checking for unix-style syscall interface... no checking for splice, vmsplice and tee... no checking for pipe2... yes checking for eventfd... no checking for timerfd_*... no checking for memfd_create... no checking for copy_file_range... no checking for st_xtimensec... yes checking for st_xtimespec... yes checking for st_birthtimensec... no checking for st_birthtimespec... no checking for st_gen... yes checking for statx... no checking for accept4... yes checking for sys/mount.h... yes checking for mount... no checking for umount... no checking for umount2... no configure: creating ./config.status config.status: creating config.h Warning: prerequisite common::sense 0 not found. Checking if your kit is complete... Looks good Generating a Unix-style Makefile Writing Makefile for IO::AIO Writing MYMETA.yml and MYMETA.json ===> Building for p5-IO-AIO-4.80p0 cp AIO.pm blib/lib/IO/AIO.pm Running Mkbootstrap for AIO () chmod 644 "AIO.bs" "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- AIO.bs blib/arch/auto/IO/AIO/AIO.bs 644 "/usr/bin/perl" "/usr/libdata/perl5/ExtUtils/xsubpp" -typemap '/usr/libdata/perl5/ExtUtils/typemap' -typemap '/exopi-obj/pobj/p5-IO-AIO-4.80/IO-AIO-4.8/typemap' AIO.xs > AIO.xsc mv AIO.xsc AIO.c cc -c -DNO_LOCALE_NUMERIC -DNO_LOCALE_COLLATE -fno-strict-aliasing -fno-delete-null-pointer-checks -pipe -fstack-protector-strong -I/usr/local/include -O2 -DVERSION=\"4.8\" -DXS_VERSION=\"4.8\" -DPIC -fpic "-I/usr/libdata/perl5/amd64-openbsd/CORE" AIO.c In file included from AIO.xs:205: ./libeio/eio.c:983:7: warning: add explicit braces to avoid dangling else [-Wdangling-else] else ^ ./libeio/eio.c:1482:13: warning: add explicit braces to avoid dangling else [-Wdangling-else] else ^ 2 warnings generated. rm -f blib/arch/auto/IO/AIO/AIO.so LD_RUN_PATH="/usr/lib" cc -shared -fpic -fstack-protector-strong -L/usr/local/lib AIO.o -o blib/arch/auto/IO/AIO/AIO.so -lpthread chmod 755 blib/arch/auto/IO/AIO/AIO.so cp bin/treescan blib/script/treescan "/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/treescan Manifying 1 pod document Manifying 1 pod document >>> Running package in devel/p5-IO-AIO at 1732133334.56 ===> devel/p5-IO-AIO ===> Faking installation for p5-IO-AIO-4.80p0 "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- AIO.bs blib/arch/auto/IO/AIO/AIO.bs 644 Manifying 1 pod document Manifying 1 pod document Files found in blib/arch: installing files in blib/lib into architecture dependent library tree Installing /exopi-obj/pobj/p5-IO-AIO-4.80/fake-amd64/usr/local/libdata/perl5/site_perl/amd64-openbsd/auto/IO/AIO/AIO.so Installing /exopi-obj/pobj/p5-IO-AIO-4.80/fake-amd64/usr/local/libdata/perl5/site_perl/amd64-openbsd/IO/AIO.pm Installing /exopi-obj/pobj/p5-IO-AIO-4.80/fake-amd64/usr/local/man/man1/treescan.1 Installing /exopi-obj/pobj/p5-IO-AIO-4.80/fake-amd64/usr/local/man/man3p/IO::AIO.3p Installing /exopi-obj/pobj/p5-IO-AIO-4.80/fake-amd64/usr/local/bin/treescan Appending installation info to /exopi-obj/pobj/p5-IO-AIO-4.80/fake-amd64/usr/./libdata/perl5/amd64-openbsd/perllocal.pod ===> Building package for p5-IO-AIO-4.80p0 Create /exopi-cvs/ports/packages/amd64/all/p5-IO-AIO-4.80p0.tgz Creating package p5-IO-AIO-4.80p0 reading plist| checking dependencies| checking dependencies|devel/p5-common-sense checksumming| checksumming| | 0% checksumming|*** | 5% checksumming|****** | 10% checksumming|********* | 15% checksumming|************ | 20% checksumming|*************** | 25% checksumming|****************** | 30% checksumming|********************* | 35% checksumming|************************ | 40% checksumming|*************************** | 45% checksumming|******************************* | 50% checksumming|********************************** | 55% checksumming|************************************* | 60% checksumming|**************************************** | 65% checksumming|******************************************* | 70% checksumming|********************************************** | 75% checksumming|************************************************* | 80% checksumming|**************************************************** | 85% checksumming|******************************************************* | 90% checksumming|********************************************************** | 95% checksumming|*************************************************************|100% archiving| archiving| | 0% archiving|********************* | 32% archiving|********************************************* | 70% archiving|********************************************** | 72% archiving|*************************************************************** | 98% archiving|****************************************************************|100% Link to /exopi-cvs/ports/packages/amd64/ftp/p5-IO-AIO-4.80p0.tgz >>> Running clean in devel/p5-IO-AIO at 1732133336.92 ===> devel/p5-IO-AIO ===> Cleaning for p5-IO-AIO-4.80p0 >>> Ended at 1732133337.14 max_stuck=0.00/depends=1.99/show-prepare-results=0.58/build=22.39/package=2.36/clean=0.24