Front page | perl.perl5.porters |
Postings from July 2022
On Sat, Jul 2, 2022 at 1:56 AM Paul "LeoNerd" Evans <leonerd@leonerd.org.uk> wrote: > > Socket-2.034 is now on CPAN with your patch in. > > (And actually just today I've put version 2.035 which adds a couple > more constants). > > Oh .. excellent !! Both 2.034 and 2.035 build and test fine on my Windows 7 system. I tested the following archname-version combinations: MSWin32-x86-multi-thread in 5.34.0 and 5.36.0 MSWin32-x86-multi-thread-ld in 5.34.0 and 5.36.0 MSWin32-x86-multi-thread-quadmath in 5.34.0 and 5.36.0 MSWin32-x86-multi-thread-64int in all stable 5.x.0 versions in the range 5.20.0 to 5.36.0 (inclusive) MSWin32-x86-multi-thread-64int-ld in all stable 5.x.0 versions in the range 5.22.0 to 5.36.0 (inclusive) MSWin32-x86-multi-thread-64int-quadmath in 5.34.0 and 5.36.0 MSWin32-x64-multi-thread in all stable 5.x.0 versions in the range 5.20.0 to 5.36.0 (inclusive) MSWin32-x64-multi-thread-64int-ld in all stable 5.x.0 versions in the range 5.22.0 to 5.36.0 (inclusive) MSWin32-x64-multi-thread-quadmath in 5.34.0 and 5.36.0 For perl-5.37.1 I settled for testing Socket-2.035 only. In addition to the 9 archnames listed above, I also tested in: MSWin32-x64-perlio MSWin32-x64-perlio-ld MSWin32-x64-perlio-quadmath MSWin32-x86-perlio-quadmath MSWin32-x86-perlio-64int-quadmath. AFAICT, on Windows the occurrence of "-perlio" just means non multi-thread. I expected (eg) "MSWin32-x64-perlio " to be simply "MSWin32-x64". It seems odd to me that the makefiles go to the trouble of deliberately adding the "-perlio", and I don't know why they do that. Because they're unthreaded, the fork() function is not implemented, and t/socketpair.t is therefore skipped on those "-perlio" builds. The different perl versions generally involve different gcc compilers (from 4.8.x up to 12.1.0) and different mingw-w64 runtimes (from 3.1 to 10.0). So I've covered a fairly broad range of mingw-w64 toolchains. I also tested 2.034 and 2.035 on my x64 perl-5.36.0 built using Microsoft's Visual Studio 2019. No issues there, either. LGTM, and I look forward to seeing 2.035 (or 2.034) pushed to blead in the not-too-distant-future. Thanks Paul. Cheers, RobThread Previous | Thread Next