-
-
Notifications
You must be signed in to change notification settings - Fork 487
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
suitesparse: Update to 7.0.1, fix DESTDIR bug #34206
Comments
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:3
DrTimothyAldenDavis/SuiteSparse#86 - "build system: Support staged installs via DESTDIR" |
comment:4
My original spkg was always a quick and dirty job. It shouldn't be a surprise that some bugs appear. |
comment:7
I guess I should have a stab at this. |
comment:8
Way too many things are built by default. We can split the package or at least not building the big stuff that we do not need like graphblas and mongoose which are very specialised stuff. |
comment:9
I think our optional |
comment:10
That's new and graphblas wasn't built before because I had removed all the subpackages using cmake at the time the initial suitesparse was included in sage. But if it can be used, why not. In other news, |
comment:11
Cannot see a dependency on GraphBLAS in igraph but if you can point to it, I'll certainly include it. |
comment:12
I am testing a first draft locally. The changes are big enough that none of the current patches actually apply or are meaningful. I will need your input for any tweaks you require for BLAS/LAPACK on OS X. It should be easy enough to figure out if something is needed. |
comment:13
Replying to François Bissey:
Sorry for the noise - looks like I misremembered |
comment:14
Do we want to build and install static libraries? |
comment:15
No, only shared |
Changed branch from u/mkoeppe/suitesparse__fix_destdir_bug to u/fbissey/suitsparse6.0.1 |
Changed commit from |
Author: François Bissey |
comment:16
Ready for inspection. |
Changed branch from u/fbissey/suitsparse6.0.1 to trac/u/fbissey/suitsparse6.0.1 |
Changed branch from trac/u/fbissey/suitsparse6.0.1 to u/fbissey/suitesparse6.0.1 |
comment:51
Yes, it starts making much more sense. |
comment:52
But there should be other similar failures potentially - at least you would think, since this is also tested in autoconf packages as soon blas/lapack is mixed with C code. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:54
Let's try this |
comment:55
If it works, I'll have to re-enable "supernodal" in cholmod. |
comment:56
running at https://github.com/mkoeppe/SuiteSparse/actions/runs/3674049225 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:58
still failing - https://github.com/mkoeppe/SuiteSparse/actions/runs/3674049225/jobs/6211825144 |
comment:59
in the failing build, gfortran still does not list zstd as a supported compression algorithm:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:61
In gentoo we just seem to do |
comment:62
Installing |
comment:63
gfortran is now configured correctly
|
comment:64
Replying to François Bissey:
Quite possible that this is needed, yes |
comment:65
suitesparse still fails to build. comment:49 has changed - getting a different error now
|
comment:66
This will need more work on another day |
comment:68
I have given it some thoughts. bookworm and sid are the only you report failing at this stage. It looks to me that they are both using gcc-12.2.0+patches - gentoo currently similarly ship gcc-12.2.1_pre20221210, some kind of pre-release. It seems it has incompatibilities with earlier gcc/gfortran releases, at least in debian. And our gcc/gfortran is an earlier and official release. I don't see a way out of this that doesn't forbid this version of the compiler unless there are both gcc and gfortran installed. |
comment:69
I agree, the Debian patches are likely the cause for the incompatibility. I think the LTO data comes with a version annotation, and Debian should probably have bumped the version along with their patches. (We also carry a patch, for macOS M1/M2 support, but I don't think it is the problem here.) |
<!-- ^^^^^ Upgrade the shipped suitesparse components to 7.6.0 --> This is to fix sagemath#37192 and supersedes sagemath#34206 The new cmake superbuild is leveraged to only build the suitesparse components of interest * amd * camd * colamd * ccolamd * cholmod * umfpack ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> <!-- Feel free to remove irrelevant items. --> - [x] The title is concise, informative, and self-explanatory. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> URL: sagemath#37204 Reported by: François Bissey Reviewer(s): Dima Pasechnik, Matthias Köppe
<!-- ^^^^^ Upgrade the shipped suitesparse components to 7.6.0 --> This is to fix sagemath#37192 and supersedes sagemath#34206 The new cmake superbuild is leveraged to only build the suitesparse components of interest * amd * camd * colamd * ccolamd * cholmod * umfpack ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> <!-- Feel free to remove irrelevant items. --> - [x] The title is concise, informative, and self-explanatory. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> URL: sagemath#37204 Reported by: François Bissey Reviewer(s): Dima Pasechnik, Matthias Köppe
(from #34203 comment:34)
DESTDIR
is used twice in the-o
.DESTDIR
handling is coming frombuild/pkgs/suitesparse/patches/03-buildflags.patch
We upgrade to 5.12.0 and pick up a fresh set of patches from Debian or another distro
Depends on #34746
Depends on #34835
CC: @kiwifb
Component: packages: standard
Author: François Bissey
Branch/Commit: u/mkoeppe/suitesparse6.0.1 @
424cb49
Issue created by migration from https://trac.sagemath.org/ticket/34206
The text was updated successfully, but these errors were encountered: