>>> perl-ev: Building testing/perl-ev 4.33-r1 (using abuild 3.9.0-r0) started Wed, 08 Jun 2022 09:11:04 +0000 >>> perl-ev: Checking sanity of /home/buildozer/aports/testing/perl-ev/APKBUILD... >>> perl-ev: Analyzing dependencies... >>> perl-ev: Installing for build: build-base perl perl-common-sense perl-dev perl-canary-stability (1/10) Installing libbz2 (1.0.8-r1) (2/10) Installing perl (5.36.0-r0) (3/10) Installing perl-common-sense (3.75-r2) (4/10) Installing perl-utils (5.36.0-r0) (5/10) Installing perl-dev (5.36.0-r0) (6/10) Installing perl-canary-stability (2013-r1) (7/10) Installing .makedepends-perl-ev (20220608.091105) (8/10) Installing perl-error (0.17029-r1) (9/10) Installing perl-git (2.36.1-r0) (10/10) Installing git-perl (2.36.1-r0) Executing busybox-1.35.0-r14.trigger OK: 279 MiB in 100 packages >>> perl-ev: Cleaning up srcdir >>> perl-ev: Cleaning up pkgdir >>> perl-ev: Fetching https://distfiles.alpinelinux.org/distfiles/edge//EV-4.33.tar.gz >>> perl-ev: Fetching https://distfiles.alpinelinux.org/distfiles/edge//EV-4.33.tar.gz >>> perl-ev: Checking sha512sums... EV-4.33.tar.gz: OK >>> perl-ev: Unpacking /var/cache/distfiles/edge/EV-4.33.tar.gz... *** *** 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.036000, 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 EV. *** 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 EV, *** 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 EV 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 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Welcome to EV configuration. If you are in a hurry, just press return here and hope for the best. The defaults should usually do. Skip further questions and use defaults (y/n)? [y] y *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** POSIX optionally offers support for a monotonic clock source. EV can take advantage of this clock source to detect time jumps more reliably. Unfortunately, some systems are bound to be broken, so you can disable this here: you can completely disable the detection and use of the monotonic clock by answering 'n' here. Support for this clock type will otherwise be autodetected at both compile- and runtime. (this setting currently affects the use of nanosleep over select as well). Enable optional support for CLOCK_MONOTONIC (y/n)? [y] y *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** POSIX optionally offers support for a (potentially) high-resolution realtime clock interface. In a good implementation, using it is faster than the normal method of using gettimeofday. Unfortunately, this option is also bound to be broken on some systems, and current EV versions do not actually call gettimeofday very often, so it defaults to no. Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)? [n] n *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** EV can use various backends with various portability issues. The select backend is the most portable and makes for a good fallback, but it can be limited to a low number of file descriptors and/or might not compile. If you have problems with compiling ev_select.c, you might try to play around with disabling it here, or forcing it to use the fd_set provided by your OS, via the next question. I highly recommend keeping it in. Enable select backend (y/n)? [y] y *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** The select backend can operate in two modes. One uses the system-provided fd_set and is usually limited to 1024 file descriptors (64 on windows), the other requires your header files to define NFDBITS and declare a suitable fd_mask type. If you run into problems compiling ev_select.c, you can try forcing the use of the system fd_set here. Force use of system fd_set for select backend (y/n)? [n] n *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** The second very portable backend is poll(2). It does not exist on windows and various versions of Mac OS X (and on the other versions it simply doesn't work), but works basically everywhere else. It is recommended to use the default here unless you run into compilation problems in ev_poll.c. Enable poll backend (y/n)? [y] y *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Select and poll make it hard to write efficient servers, especially if the number of active connections is much lower than the watched ones. GNU/Linux systems have a more scalable method called "epoll", which EV can use. For this to work, both your kernel and glibc have to support epoll, but if you can compile it, the detection will be done at runtime, and EV will safely fall back to using select when epoll isn't available. If unsure, accept the default. Enable epoll backend (y/n)? [y] y *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Linux 4.18 introduced another event polling interface, this time using the Linux AIO API. While this API is far superior to epoll and almost rivals kqueue, it also suffers from the same issues as kqueue typically does: only a subset of file types are supported (as of 4.19, I have seen eventfd, pipes, sockets files and some devices, but no ttys). It also is subject arbitrary system-wide limits imposed on it. Therefore, this backend is not used by default, even when it is compiled in, and you have to request it explicitly, e.g. with LIBEV_FLAGS=64. If unsure, accept the default. Enable linux aio backend (y/n)? [n] n *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Linux 4.19 introduced another event polling interface, "io_uring". While this API is far superior to epoll and almost rivals linuxaio, it also suffers from the same issues as kqueue typically does: only a subset of file types are supported (as of 5.2). It is also very buggy still, and most importantly, very very slow for most workloads. Therefore, this backend is not used by default, even when it is compiled in, and you have to request it explicitly, e.g. with LIBEV_FLAGS=128. If unsure, accept the default. Enable linux io_uring backend (y/n)? [n] n *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** EV can take advantage of kqueue on many BSD systems. Support for kqueue will be detected at runtime, with a safe fallback to other methods when it cannot be used. Note that kqueue is subtly broken on most operating systems, so by default it won't be used on many platforms, but you can still create your own event loop with kqueue backend if you ask specifically for it. Here is what we know: NetBSD: partially working in at least 3.1 and later. Yeah! :) FreeBSD: broken on at least 6.2-STABLE, spotty in later versions, sockets *likely* work, ptys definitely don't. OpenBSD: reports indicate that it likely doesn't work (similar problems as on FreeBSD). OS X: completely, utterly broken on at least <= 10.6. Enable kqueue backend (y/n)? [n] n *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Similarly to the kqueue backend above, EV can take advantage of the solaris 10 event port interface. Support for event ports will be detected at runtime, with a safe fallback to other methods when it cannot be used. Enable event port backend (y/n)? [n] n *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** EV needs the functions pthread_atfork and clock_gettime. On most systems you need some special libraries for this (such as -lrt and -lpthread). You can specify additional libraries to provide these calls (and any other required by EV) now, or accept the default. On GNU/Linux systems, EV uses the LSB 3.1 __register_atfork function to avoid the dependency on libpthread, and directly uses the clock_gettime syscall to avoid a dependency on librt. Extra libraries for pthread_atfork and clock_gettime? [ ] *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** A backend of a different kind is the Linux inotify(7) interface, which can be used to speed up (and reduce resource consumption) of stat watchers. If you have the include file and libc support for it, it is usually a good idea to enable it, as kernel availability is detected at runtime. Enable inotify support (y/n)? [y] y *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Another useful bit of functionality is the Linux eventfd, which is useful for faster signal handling (don't care) and intra-thread communications (more relevant). Kernel support for this will be probed at runtime, but your libc must contain the necessary wrapper. Glibc 2.7 and later should have this wrapper. Enable linux eventfd support (y/n)? [y] y *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Another sometimes useful bit of functionality is the Linux signalfd, which is useful for faster signal handling (don't care). Kernel support for this will be probed at runtime, but your libc must contain the necessary wrapper. Glibc 2.7 and later should have this wrapper. Enable linux signalfd support (y/n)? [y] y *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Linux kernels can notify userspace about realtime clock timejumps using timerfd. Libev by default will try to take advantage of this if possible. You can completely disable the detection and use of timerfd for this purpose by answering 'n' here. Support for timerfd will otherwise be autodetected at both compile- and runtime. Enable optional support for timerfd to detect timejumps (y/n)? [y] y *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Libev contains numerous internal assert() invocations to check for consistency and user errors. These are normally enabled, but most perl builds disable this error reporting mechanism by default. You can re-enable these asserts here. Enabling them might help you catch programming bugs earlier, but might cause a small slowdown. Also, failures will be reported by aboritng your program, instead of throwing a perl exception. If unsure, enable this if you only use this perl installation for development, and leave it off for use in production environments. Make sure assertions are enabled? (y/n)? [n] n *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Very rarely, people want to tweak EV even more, e.g. to exclude or include certain watcher types or backends. This can be done by adding extra -D options here, or via the EV_EXTRA_DEFS environment variable. For example, if you run into compilation problems because of missing memory fences (or you just want extra performance), you can tell EV to not support smp and threads via -DEV_NO_THREADS. Most people would just press enter. Any extra -D options? [] *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Checking if your kit is complete... Looks good Generating a Unix-style Makefile Writing Makefile for EV Writing MYMETA.yml and MYMETA.json Running Mkbootstrap for EV () "/usr/bin/perl" "/usr/share/perl5/core_perl/ExtUtils/xsubpp" -typemap '/usr/share/perl5/core_perl/ExtUtils/typemap' -typemap '/home/buildozer/aports/testing/perl-ev/src/EV-4.33/typemap' EV.xs > EV.xsc chmod 644 "EV.bs" "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- EV.bs blib/arch/auto/EV/EV.bs 644 cp libev/ev.pod blib/lib/EV/libev.pod cp EV/EVAPI.h blib/lib/EV/EVAPI.h cp EV.pm blib/lib/EV.pm cp EV/MakeMaker.pm blib/lib/EV/MakeMaker.pm cp libev/ev.h blib/lib/EV/ev.h mv EV.xsc EV.c cc -c -Ilibev -D_REENTRANT -D_GNU_SOURCE -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Os -fomit-frame-pointer -DVERSION=\"4.33\" -DXS_VERSION=\"4.33\" -fPIC "-I/usr/lib/perl5/core_perl/CORE" -DEV_USE_REALTIME=0 -DEV_USE_SELECT=1 -DEV_USE_POLL=1 -DEV_USE_EPOLL=1 -DEV_USE_LINUXAIO=0 -DEV_USE_IOURING=0 -DEV_USE_KQUEUE=0 -DEV_USE_PORT=0 -DEV_USE_INOTIFY=1 -DEV_USE_EVENTFD=1 -DEV_USE_SIGNALFD=1 EV.c rm -f blib/arch/auto/EV/EV.so cc -shared -Os -fomit-frame-pointer -L/usr/local/lib -fstack-protector-strong EV.o -o blib/arch/auto/EV/EV.so \ \ chmod 755 blib/arch/auto/EV/EV.so Manifying 3 pod documents "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- EV.bs blib/arch/auto/EV/EV.bs 644 PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/00_load.t ........ ok t/01_timer.t ....... ok t/02_once.t ........ ok t/03_keepalive.t ... ok t/04_stat.t ........ ok t/05_priority.t .... ok t/06_loop_once.t ... ok t/07_loop_timer.t .. ok t/08_async.t ....... ok t/09_brandon.t ..... ok t/11_signal.t ...... ok All tests successful. Files=11, Tests=6875, 6 wallclock secs ( 0.71 usr 0.02 sys + 0.41 cusr 0.11 csys = 1.25 CPU) Result: PASS >>> perl-ev: Entering fakeroot... "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- EV.bs blib/arch/auto/EV/EV.bs 644 Manifying 3 pod documents Appending installation info to /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/lib/perl5/core_perl/perllocal.pod Files found in blib/arch: installing files in blib/lib into architecture dependent library tree Installing /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/lib/perl5/vendor_perl/auto/EV/EV.so Installing /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/lib/perl5/vendor_perl/EV.pm Installing /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/lib/perl5/vendor_perl/EV/MakeMaker.pm Installing /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/lib/perl5/vendor_perl/EV/EVAPI.h Installing /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/lib/perl5/vendor_perl/EV/ev.h Installing /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/lib/perl5/vendor_perl/EV/libev.pod Installing /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/share/man/man3/EV::libev.3pm Installing /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/share/man/man3/EV::MakeMaker.3pm Installing /home/buildozer/aports/testing/perl-ev/pkg/perl-ev/usr/share/man/man3/EV.3pm >>> perl-ev-doc*: Running split function doc... >>> perl-ev-doc*: Preparing subpackage perl-ev-doc... >>> perl-ev-doc*: Running postcheck for perl-ev-doc >>> perl-ev*: Running postcheck for perl-ev >>> perl-ev*: Preparing package perl-ev... >>> perl-ev*: Stripping binaries >>> perl-ev-doc*: Scanning shared objects >>> perl-ev*: Scanning shared objects >>> perl-ev-doc*: Tracing dependencies... >>> perl-ev-doc*: Package size: 128.0 KB >>> perl-ev-doc*: Compressing data... >>> perl-ev-doc*: Create checksum... >>> perl-ev-doc*: Create perl-ev-doc-4.33-r1.apk >>> perl-ev*: Tracing dependencies... perl perl-common-sense so:libc.musl-ppc64le.so.1 >>> perl-ev*: Package size: 544.0 KB >>> perl-ev*: Compressing data... >>> perl-ev*: Create checksum... >>> perl-ev*: Create perl-ev-4.33-r1.apk >>> perl-ev: Build complete at Wed, 08 Jun 2022 09:11:20 +0000 elapsed time 0h 0m 16s >>> perl-ev: Cleaning up srcdir >>> perl-ev: Cleaning up pkgdir >>> perl-ev: Uninstalling dependencies... (1/10) Purging .makedepends-perl-ev (20220608.091105) (2/10) Purging perl-common-sense (3.75-r2) (3/10) Purging perl-dev (5.36.0-r0) (4/10) Purging perl-utils (5.36.0-r0) (5/10) Purging perl-canary-stability (2013-r1) (6/10) Purging git-perl (2.36.1-r0) (7/10) Purging perl-git (2.36.1-r0) (8/10) Purging perl-error (0.17029-r1) (9/10) Purging perl (5.36.0-r0) (10/10) Purging libbz2 (1.0.8-r1) Executing busybox-1.35.0-r14.trigger OK: 230 MiB in 90 packages >>> perl-ev: Updating the testing/ppc64le repository index... >>> perl-ev: Signing the index...