Opened 4 years ago
Closed 2 years ago
#60718 closed update (fixed)
sundials @3.1.2 update to versions 4.1.0 and 5.3.0
| Reported by: | rwirth (Roland Wirth) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | Schamschula (Marius Schamschula), mascguy (Christopher Nielsen) | |
| Port: | sundials |
Description
The package API changed between versions 3 and 4, so code written for version 3 will not compile with version 4. Version 5 contains some incompatible changes that affect user implementations of certain submodules.
Change History (6)
comment:1 follow-up: 6 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 4 years ago by Schamschula (Marius Schamschula)
At least octave needs to use a more modern version of sundials. sundials2 fails in ./configure.
comment:3 Changed 4 years ago by Schamschula (Marius Schamschula)
| Cc: | Schamschula added |
|---|
comment:4 Changed 4 years ago by Schamschula (Marius Schamschula)
comment:5 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
comment:6 Changed 2 years ago by mascguy (Christopher Nielsen)
| Cc: | mascguy added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Replying to ryandesign:
The sundials and sundials2 ports currently conflict with another. This is not desired. If we are to keep several ports around for SUNDIALS at different versions, they should install to different places and not conflict with one another.
The various sundials ports are now segregated, eliminating these headaches. Fixed per issue:63631
We currently have a sundials port at version 3.1.2 and a sundials2 port at version 2.7.0, but all of the ports in MacPorts that use SUNDIALS depend on sundials2 presumably because they are not compatible with version 3. And you're saying that versions 4 and 5 exist and they also break compatibility. It sounds like maybe we need to rename the sundials port to sundials3 and add sundials4 and sundials5 ports and just accept that we need to keep many different versions around.
Based on my testing, the four dependents of our various sundials ports, are all set: One (petsc) uses sundials2, while the other three (deal.ii, cantera, and octave) all work fine with sundials5.
Of note, deal.ii and cantera are broken due to other issues, so they currently don't build. But I've validated that they properly find/use sundials5, so that's one less thing to worry about.
We currently have a sundials port at version 3.1.2 and a sundials2 port at version 2.7.0, but all of the ports in MacPorts that use SUNDIALS depend on sundials2 presumably because they are not compatible with version 3. And you're saying that versions 4 and 5 exist and they also break compatibility. It sounds like maybe we need to rename the sundials port to sundials3 and add sundials4 and sundials5 ports and just accept that we need to keep many different versions around.
The sundials and sundials2 ports currently conflict with another. This is not desired. If we are to keep several ports around for SUNDIALS at different versions, they should install to different places and not conflict with one another.