START devel/p5-Coro 2025-01-30T11:52:26Z ===> Building from scratch p5-Coro-6.570p0 ===> p5-Coro-6.570p0 depends on: p5-AnyEvent->=5.00 -> p5-AnyEvent-7.17p2v0 ===> p5-Coro-6.570p0 depends on: p5-EV->=4.0 -> p5-EV-4.34 ===> p5-Coro-6.570p0 depends on: p5-Event->=1.08 -> p5-Event-1.28 ===> p5-Coro-6.570p0 depends on: p5-Guard->=0.5 -> p5-Guard-1.023p0 ===> p5-Coro-6.570p0 depends on: p5-common-sense-* -> p5-common-sense-3.75 ===> p5-Coro-6.570p0 depends on: p5-Canary-Stability-* -> p5-Canary-Stability-2013p0 ===> Verifying specs: c perl ===> found c.100.3 perl.25.0 ===> Checking files for p5-Coro-6.570p0 `/usr/ports/distfiles/Coro-6.57.tar.gz' is up to date. >> (SHA256) all files: OK ===> Extracting for p5-Coro-6.570p0 ===> Patching for p5-Coro-6.570p0 ===> Applying OpenBSD patch patch-Coro_AnyEvent_pm Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Indirect Object Syntax | |Outside of the file handle case, use of this syntax is discouraged as it |can confuse the Perl interpreter. See below for more details. | |Index: Coro/AnyEvent.pm |--- Coro/AnyEvent.pm.orig |+++ Coro/AnyEvent.pm -------------------------- Patching file Coro/AnyEvent.pm using Plan A... Hunk #1 succeeded at 217. Hunk #2 succeeded at 225. done ===> Applying OpenBSD patch patch-Coro_Handle_pm Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Indirect Object Syntax | |Outside of the file handle case, use of this syntax is discouraged as it |can confuse the Perl interpreter. See below for more details. | |Index: Coro/Handle.pm |--- Coro/Handle.pm.orig |+++ Coro/Handle.pm -------------------------- Patching file Coro/Handle.pm using Plan A... Hunk #1 succeeded at 77. done ===> Applying OpenBSD patch patch-Coro_Socket_pm Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |The 5.36 bundle also disables the features "indirect", and |"multidimensional". | |Indirect Object Syntax | |Outside of the file handle case, use of this syntax is discouraged as it |can confuse the Perl interpreter. See below for more details. | |Index: Coro/Socket.pm |--- Coro/Socket.pm.orig |+++ Coro/Socket.pm -------------------------- Patching file Coro/Socket.pm using Plan A... Hunk #1 succeeded at 62. Hunk #2 succeeded at 195. done ===> Applying OpenBSD patch patch-Coro_Storable_pm Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Indirect Object Syntax | |Outside of the file handle case, use of this syntax is discouraged as it |can confuse the Perl interpreter. See below for more details. | |Index: Coro/Storable.pm |--- Coro/Storable.pm.orig |+++ Coro/Storable.pm -------------------------- Patching file Coro/Storable.pm using Plan A... Hunk #1 succeeded at 89. done ===> Applying OpenBSD patch patch-Coro_Util_pm Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Indirect Object Syntax | |Outside of the file handle case, use of this syntax is discouraged as it |can confuse the Perl interpreter. See below for more details. | |Index: Coro/Util.pm |--- Coro/Util.pm.orig |+++ Coro/Util.pm -------------------------- Patching file Coro/Util.pm using Plan A... Hunk #1 succeeded at 45. done ===> Applying OpenBSD patch patch-Coro_pm Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Indirect Object Syntax | |Outside of the file handle case, use of this syntax is discouraged as it |can confuse the Perl interpreter. See below for more details. | |Index: Coro.pm |--- Coro.pm.orig |+++ Coro.pm -------------------------- Patching file Coro.pm using Plan A... Hunk #1 succeeded at 18. Hunk #2 succeeded at 426. Hunk #3 succeeded at 1057. Hunk #4 succeeded at 1069. done ===> Applying OpenBSD patch patch-EV_EV_pm Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Indirect Object Syntax | |Outside of the file handle case, use of this syntax is discouraged as it |can confuse the Perl interpreter. See below for more details. | |Index: EV/EV.pm |--- EV/EV.pm.orig |+++ EV/EV.pm -------------------------- Patching file EV/EV.pm using Plan A... Hunk #1 succeeded at 66. done ===> Applying OpenBSD patch patch-Event_Event_pm Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Indirect Object Syntax | |Outside of the file handle case, use of this syntax is discouraged as it |can confuse the Perl interpreter. See below for more details. | |Index: Event/Event.pm |--- Event/Event.pm.orig |+++ Event/Event.pm -------------------------- Patching file Event/Event.pm using Plan A... Hunk #1 succeeded at 190. 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-Coro-6.570p0 ===> Configuring for p5-Coro-6.570p0 *** *** 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.040001, 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 Coro. *** 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 Coro, *** 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 Coro 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 Event.c: loadable library and perl binaries are mismatched (got first handshake key 0xf280000, needed 0xf180000) *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:3030 'do-configure': @:; cd /usr/ports/pobj/p5-Coro-6.570/Coro-6.57; /usr/bin/en...) *** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:3050 '/usr/ports/pobj/p5-Coro-6.570/.configure_done': @cd /usr/ports/devel/p5-Cor...) *** Error 2 in /usr/ports/devel/p5-Coro (/usr/ports/infrastructure/mk/bsd.port.mk:2712 'build': @lock=p5-Coro-6.570p0; export _LOCKS_HELD="...) NOEXIT devel/p5-Coro Command 'make build' failed: 512