JuliaPackaging
[SCS] link against libblastrampoline
whenever it makes sense; No changes to scsmkl, since it is already linked against mkl directly.
CC: @odow
This needs a new version number (and then some changes to SCS.jl), so let's just wait for the next upstream release.
there's also a build failure due to libblastrampoline not found on aarch64-unknown-freebsd, is that expected @giordano ?
@ararslan what version of libblastrampoline supports aarch64-freebsd? Is it easier to just skip that platform?
Should we move freebsd-aarch64 to experimental until Julia 1.12 is out?
The experimental option didn't work very well because it's a moving target, I prefer being explicit.
My general approach with building a package for such a niche platform like aarch64-freebsd is "if it works easily, awesome, if it takes too much effort to make it work then just exclude it and move on".
what version of libblastrampoline supports aarch64-freebsd?
I believe it's 5.11.0. I can do a rebuild of 5.4.0 if needed.
what version of libblastrampoline supports aarch64-freebsd?
I believe it's 5.11.0. I can do a rebuild of 5.4.0 if needed.
should we filter platforms and create two separate deps with different compat for blastrampoline? What is the compat we should use when targeting julia-1.10 and higher?
I believe the only thing to do for now is to filter out freebsd aarch64.
IIUC, libblastrampoline is the rare example where bumping the compat is not a problem. I went through a similar situation recently and that was my takeaway. Perhaps @giordano can confirm?
stdlibs are always bound to a specific version of Julia. I think you did recently on suitesparse, which is a stdlib itself, so the problem doesn't really matter there.
Ah right, okay. Looking at the builders that depend on libblastrampoline, the most common compat setting is 5.4, so perhaps it could be worthwhile to rebuild that anyway.
Both 1.10.5 and 1.11.0 have libblastrampoline 5.11.0. However 1.10.0 has LBT 5.4.
Trying LBT update in in https://github.com/JuliaPackaging/Yggdrasil/pull/9641
Thanks Viral! Sorry for not following up on this sooner, I've had basically no time for anything lately.
Yeah. Ideally we would have merged this in before tagging a release of SCS_jll. We'll need to wait for the next upstream release. This motivated the component_owners mechanism so I can now get a ping before any changes to SCS.
You don't need to wait for an upstream release; the version numbers do not need to agree. (This happens frequently in Yggdrasil.)
the version numbers do not need to agree. (This happens frequently in Yggdrasil.)
I know, but I try very hard to keep them in sync. I'm not in a rush for LBT in SCS, so it can wait.
SCS 3.2.9 has just been released, so you can add it now without getting the numbers out of sync.
