Conversation
|
I suspect that any upgrade step will solely involve changing instances of to |
|
Merging because changes straightforward and it keeps CI going. |
|
Would this affect testing with fortran on windows? |
|
Not quite sure what the question is asking. The majority of the windows CI infra uses rtools to supply pkg-config, gcc, gfortran. The jobs started failing because the choco update meant rtools was in a different location, meaning that the build tools weren't found. This PR pins the version of rtools, so the tools that were working can be found again. |
|
I was asking because we have started getting CI failures involving Fortran when running full tests on Windows 32 bit, see numpy/numpy#23675. I was wondering if there could be a connection. |
|
I think there will be a connection. The azure job installs rtools. Rtools43 is now the default on choco and that will be installed in a different location. I suspect you need to pin the version. |
See scipy/scipy#18374 for the reason. Closes numpy#23675.
See scipy/scipy#18374 for the reason. Closes numpy#23675.
See scipy/scipy#18374 for the reason. Closes numpy#23675.
|
@andyfaff Just for your information, it turns out that rtools dropped support for 32 bit builds in version 4.2. |
See scipy/scipy#18374 for the reason. Closes numpy#23675.
See scipy/scipy#18374 for the reason. Closes numpy#23675.
There is a new rtools release on
choco, version 4.3. This has caused a large proportion of Windows CI to stop working as the binaries are in a different place to the previous version available on choco. This meant that meson couldn't find pkg-config (different install location), so the whole build ground to a halt.This PR pins the rtools version to 4.0. Decided to stick with that because 4.3 may bundle different gcc versions, etc.