-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perl 5.36.1 builds with gcc-13.1 #100
Comments
Extlibs files are at https://github.com/StrawberryPerl/build-extlibs/releases/tag/dev_gcc13.1_20230502 The docker instances are the same as for https://github.com/StrawberryPerl/spbuild/tree/main/5.34 except the winlibs URL was updated to the gcc-13.1 version. |
I struck those Not sure if that piece of information is in any way helpful .... ;-( Cheers, |
Yes, the errors go away when libmcfgthread-1.dll is copied across. |
PDL still fails with the same errors, though. |
That pesky niceslice issue again ? Cheers, |
Thanks Rob. Will be interesting to see if it can be replicated using a different machine. |
FYI there is now a PDL 2.083 and it would be helpful to see if that makes a difference? |
Hmmm ... if perl-5.36.1 is built using LH_Mouse's 1310 compiler then PDL-2.082 and 2.083 build, test and install fine. TBC, as is to be expected, in all cases I build PDL using the actual compiler that built perl-5.36.1. With LH_Mouse's compiler, PDL-2.082 and 2.083 require the Math/Basic/Makefile.PL and IO/Browser/Makefile.pl patches that I've already mentioned somewhere in some previous post. IIRC, PDL-2.082 is fine with winlibs-13.1.0, perl-5.37.11. Cheers, |
It would be good to have Strawberry PDL builds for all versions of PDL, obviously. But I don't have a lot of time to invest in helping with that currently, so those who do get to make the calls :-) |
@sisyphus - just to be absolutely sure, did you also compile PDL with PDL compiled with gcc-10 when using I'll try to have a go later today. |
But on the good news front, since this issue is for the full build with gcc-13.1, the CPAN step worked to completion and the system generated all the requisite outputs. This was for a config without the PDL component. I'll upload the artefacts later today for people to test. |
I believe so. Cheers, |
I also built with |
I tried So I went one step further and built perl-5.36.1 with winlibs-13.1.0 with My main interest in LH_Mouse's compiler is that his 32-bit 13.1.0 is the only compiler I've ever struck that produces MSWin32-x86-multi-thread-quadmath && MSWin32-x86-mutli-thread-64int-quadmath builds that pass all tests. Admittedly, it's only 32-bit quadmath builds - which are hardly high priority. Cheers, |
And just as another data point I tried with I'm building one with |
There's also the brute force option of repeatedly building PDL with the -O1 optimisation set but with one turned off at a time. That assumes there are no interactions between optimisations, of course, but it's otherwise a simple loop. The list can be obtained by running |
GDB backtrace below after building with @mohawk2 - does this help with diagnosis? Or do we also need a perl built with debugging? (The gdb warning is probably due to the docker env, or because I removed 60+MB of python stuff from the winlibs directory tree).
|
The main topics of this issue have been handled now that #93 has been resolved. The remaining topics have their own issues. I'll close this issue but please add a note if there is a reason to reopen it. |
I should have noted this before closing. A new dev release with a working PDL is available from https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/dev_5361_20230524_gcc13 |
Given the discussion in #93 regarding PDL builds, I've had a go at using gcc-13.1.
I'll push commits to the wip_536 branch soon but below are some notes.
-Os
(which we have already been using for 5.36.0, FWIW).perl/bin
dir, the same as for libwinpthread-1.dllThe build ran to completion but then we hit some test fails. Several of these are already known.
op/magic.t
is under Failed test 186 - ENV store downgrades utf8 in setenv at op/magic.t line 75 (also test 187) #60porting/customized.t
is because we are patching a module and have not updated the tests.cpan/ExtUtils-MakeMaker/t/basic.t
seems to be a docker issue and is also in 5.37.11: 5.37.11 build #97 (comment)cpan/ExtUtils-PL2Bat/t/make_executable.t
has an open issue at Test Failures on Windows Perl-Toolchain-Gang/extutils-pl2bat#7 and is probably to do with the docker setup as it builds locally without error. It did not affect the gcc-10 builds.The text was updated successfully, but these errors were encountered: