The following packages will be installed:
 perl-EV 
Fetching README...  0%100%100%100%100%100%Done
Fetching perl-EV.SlackBuild...  0%100%100%100%100%100%Done
Fetching perl-EV.info...  0%100%100%100%100%100%Done
Fetching slack-desc...  0%100%100%100%100%100%Done
EV-4.25/
EV-4.25/COPYING
EV-4.25/libev/
EV-4.25/libev/ev_port.c
EV-4.25/libev/ev_vars.h
EV-4.25/libev/ev.c
EV-4.25/libev/ev_win32.c
EV-4.25/libev/ev_poll.c
EV-4.25/libev/ev_select.c
EV-4.25/libev/ev_kqueue.c
EV-4.25/libev/LICENSE
EV-4.25/libev/ev.pod
EV-4.25/libev/ev_wrap.h
EV-4.25/libev/ev.h
EV-4.25/libev/ev_epoll.c
EV-4.25/libev/Changes
EV-4.25/libev/README
EV-4.25/schmorp.h
EV-4.25/MANIFEST
EV-4.25/t/
EV-4.25/t/04_stat.t
EV-4.25/t/00_load.t
EV-4.25/t/07_loop_timer.t
EV-4.25/t/06_loop_once.t
EV-4.25/t/09_brandon.t
EV-4.25/t/03_keepalive.t
EV-4.25/t/01_timer.t
EV-4.25/t/02_once.t
EV-4.25/t/11_signal.t
EV-4.25/t/05_priority.t
EV-4.25/t/08_async.t
EV-4.25/EV.pm
EV-4.25/Makefile.PL
EV-4.25/EV/
EV-4.25/EV/EVAPI.h
EV-4.25/EV/MakeMaker.pm
EV-4.25/EV.xs
EV-4.25/typemap
EV-4.25/README
EV-4.25/Changes
EV-4.25/META.yml
EV-4.25/META.json

***
*** The stability canary says: (nothing, it was driven away by harsh weather)
***
*** It seems you are running perl version 5.034000, 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/
***


*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


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 compile 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

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


Similarly to the epoll backend above, 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 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

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


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 compile 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.

Normal persons 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
cp EV/MakeMaker.pm blib/lib/EV/MakeMaker.pm
cp EV/EVAPI.h blib/lib/EV/EVAPI.h
cp libev/ev.h blib/lib/EV/ev.h
cp EV.pm blib/lib/EV.pm
cp libev/ev.pod blib/lib/EV/libev.pod
Running Mkbootstrap for EV ()
chmod 644 "EV.bs"
"/usr/bin/perl5.34.0" -MExtUtils::Command::MM -e 'cp_nonempty' -- EV.bs blib/arch/auto/EV/EV.bs 644
"/usr/bin/perl5.34.0" "/usr/share/perl5/ExtUtils/xsubpp"  -typemap '/usr/share/perl5/ExtUtils/typemap' -typemap '/usr/src/slapt-src/perl/perl-EV/EV-4.25/typemap'  EV.xs > EV.xsc
mv EV.xsc EV.c
cc -c  -Ilibev -D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -O2 -fPIC   -DVERSION=\"4.25\" -DXS_VERSION=\"4.25\" -fPIC "-I/usr/lib64/perl5/CORE"  -DEV_USE_REALTIME=0 -DEV_USE_SELECT=1 -DEV_USE_POLL=1 -DEV_USE_EPOLL=1 -DEV_USE_KQUEUE=0 -DEV_USE_PORT=0 -DEV_USE_INOTIFY=1 -DEV_USE_EVENTFD=1 -DEV_USE_SIGNALFD=1  EV.c
In file included from EV.xs:40:
libev/ev.c: In function ‘evpipe_write’:
libev/ev.c:2475:11: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
 2475 |           write (evpipe [1], &counter, sizeof (uint64_t));
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libev/ev.c:2487:11: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
 2487 |           write (evpipe [1], &(evpipe [1]), 1);
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libev/ev.c: In function ‘pipecb’:
libev/ev.c:2508:11: warning: ignoring return value of ‘read’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
 2508 |           read (evpipe [1], &counter, sizeof (uint64_t));
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libev/ev.c:2522:11: warning: ignoring return value of ‘read’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
 2522 |           read (evpipe [0], &dummy, sizeof (dummy));
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rm -f blib/arch/auto/EV/EV.so
cc  -shared -O2 -fPIC -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/perl5.34.0" -MExtUtils::Command::MM -e 'cp_nonempty' -- EV.bs blib/arch/auto/EV/EV.bs 644
PERL_DL_NONLAZY=1 "/usr/bin/perl5.34.0" "-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,  5 wallclock secs ( 0.25 usr  0.01 sys +  0.12 cusr  0.02 csys =  0.40 CPU)
Result: PASS
"/usr/bin/perl5.34.0" -MExtUtils::Command::MM -e 'cp_nonempty' -- EV.bs blib/arch/auto/EV/EV.bs 644
Manifying 3 pod documents
Files found in blib/arch: installing files in blib/lib into architecture dependent library tree
Installing /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/lib64/perl5/vendor_perl/auto/EV/EV.so
Installing /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/lib64/perl5/vendor_perl/EV.pm
Installing /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/lib64/perl5/vendor_perl/EV/MakeMaker.pm
Installing /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/lib64/perl5/vendor_perl/EV/EVAPI.h
Installing /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/lib64/perl5/vendor_perl/EV/ev.h
Installing /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/lib64/perl5/vendor_perl/EV/libev.pod
Installing /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/man/man3/EV.3
Installing /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/man/man3/EV::MakeMaker.3
Installing /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/man/man3/EV::libev.3
Appending installation info to /usr/src/slapt-src/perl/perl-EV/package-perl-EV/usr/lib64/perl5/perllocal.pod

Slackware package maker, version 3.14159265.

Searching for symbolic links:

No symbolic links were found, so we won't make an installation script.
You can make your own later in ./install/doinst.sh and rebuild the
package if you like.

This next step is optional - you can set the directories in your package
to some sane permissions. If any of the directories in your package have
special permissions, then DO NOT reset them here!

Would you like to reset all directory permissions to 755 (drwxr-xr-x) and
directory ownerships to root.root ([y]es, [n]o)? n

Creating Slackware package:  /usr/src/slapt-src/perl/perl-EV/perl-EV-4.25-x86_64-1salix15.0.txz

./
install/
install/slack-desc
usr/
usr/doc/
usr/doc/perl-EV-4.25/
usr/doc/perl-EV-4.25/COPYING
usr/doc/perl-EV-4.25/Changes
usr/doc/perl-EV-4.25/README
usr/doc/perl-EV-4.25/perl-EV.SlackBuild
usr/lib64/
usr/lib64/perl5/
usr/lib64/perl5/vendor_perl/
usr/lib64/perl5/vendor_perl/EV/
usr/lib64/perl5/vendor_perl/EV.pm
usr/lib64/perl5/vendor_perl/EV/EVAPI.h
usr/lib64/perl5/vendor_perl/EV/MakeMaker.pm
usr/lib64/perl5/vendor_perl/EV/ev.h
usr/lib64/perl5/vendor_perl/EV/libev.pod
usr/lib64/perl5/vendor_perl/auto/
usr/lib64/perl5/vendor_perl/auto/EV/
usr/lib64/perl5/vendor_perl/auto/EV/EV.so
usr/man/
usr/man/man3/
usr/man/man3/EV.3.gz
usr/man/man3/EV::MakeMaker.3.gz
usr/man/man3/EV::libev.3.gz

Slackware package /usr/src/slapt-src/perl/perl-EV/perl-EV-4.25-x86_64-1salix15.0.txz created.

Installing package perl-EV-4.25-x86_64-1salix15.0...
| perl-EV (perl interface to libev)
| 
| This module is very fast and scalable. It is actually so fast that
| you can use it through the AnyEvent module, stay portable to other
| event loops and still be faster than with any other event loop
| currently supported in Perl.
| 
| Homepage: https://metacpan.org/pod/EV
| 
| 
| 
| 
|