Conversation
|
|
I think xyce should switch to cmake build system in align. trilinos has ref to stdenv.cc and binutils, which make the final closure lagre, we should nuk-ref them. Ref:
|
|
@qbisi Feel free to open your own PR. I don't use this package. The only motivation was fixing the build. |
I will try before 25.11 release. This pr LGTM as a fixup, for now, the main block is downstream xyce (we should use cmake to build xyce too). |
|
Hey, effectively this package is only used by Xyce which requires a specific version of trilinos. It was not updated to the latest for this reason. Please reverse the commit! |
|
It would also be polite to wait a couple of days to get feedback from the maintainer... |
To clarify: In fact, i agree with updating/unpin trilinos, but we should not break xyce. If cant, either use a simple cmake minimual version substitution or mark trilinos broken. The best solution is to switch xyce build system to cmake, so xyce can find trilinos components. However, we should not enforce that on the maintainer. |
|
As I said above, trilinos and xyce were both broken before this PR. So this is a strict improvement. |
|
Have you checked the upper trilinos supported by latest Xyce? Maybe we'll need a downgrade of the former. |
As per https://github.com/Xyce/Xyce/blob/master/INSTALL.md |
Diff: trilinos/Trilinos@trilinos-release-12-12-1...trilinos-release-16-1-0
related: #445447, #451447 (comment)
Note that xyce is still broken but at least trilinos builds.
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.