I've finally gotten our local patches applied to perl 5.28.1 and it now could use some testing. I was trying to get a few more of my architectures working, but I ran out of time and now I have to go visit family for the holidays so it's up to y'all to do some testing for me.
The infrastructure to do that is still here on github, including instructions on using it: https://github.com/afresh1/OpenBSD-perl/ You can also download a pre-patched perl from here, use it to replace src/gnu/usr.bin/perl and do a normal build to get it installed, do note that any XS modules that were built with the old version of perl will no longer work, so be careful. http://cvs.afresh1.com/~andrew/OpenBSD-perl-5.28.1.tar.gz You can read more on the new features and changes on the metacpan. https://metacpan.org/release/SHAY/perl-5.28.1 You find them in the perldelta for the versions since 5.24. https://metacpan.org/pod/release/SHAY/perl-5.28.1/pod/perl5260delta.pod https://metacpan.org/pod/release/SHAY/perl-5.28.1/pod/perl5280delta.pod https://metacpan.org/pod/release/SHAY/perl-5.28.1/pod/perldelta.pod One of the important changes, and the one most likely to cause trouble is the removal of "." from the @INC library search list. This seems to work on most of the architectures I have available: arm64; amd64; i386; and macppc. However, my alpha and octeon are slow enough that they needed to set the PERL_TEST_TIME_OUT_FACTOR as high as 20 to pass all tests. I have seen that sometimes there is a syslog test that fails unless you restart syslogd just before starting the build, not yet sure why. My octeon is an EdgeRouter Lite which has software floating point. On this machine perl gets the wrong answer when comparing some numbers to "NaN". I've emailed a test case to visa@ and there may be a patch to fix something coming out before long. I did run into some problems with my other test machines, but the problem seems unrelated to perl. My armv7 is apparently mad at me, it is a Beaglebone Black and doesn't want to build some of the test programs in the Configure script so that just failed. bbb$ sysctl -n kern.version OpenBSD 6.4-current (GENERIC) #105: Sun Dec 23 12:49:26 MST 2018 dera...@armv7.openbsd.org:/usr/src/sys/arch/armv7/compile/GENERIC bbb$ cat >try.c <<EOL > #include <stdio.h> > int main() { printf("Ok\n"); return(0); } > EOL bbb$ cc -o try try.c -lm /usr/lib/libm.so.10.1: file not recognized: File format not recognized cc: error: linker command failed with exit code 1 (use -v to see invocation) My sparc64, a Sun Fire V100, first decided to have a bad hard disk and two new disks later I think there must be something else wrong with the machine as I am now getting bus errors and sent to DDB. When I get back home I'll try swapping the disk into a different V100 and see if I have better luck.
