Up1600#52
Conversation
…nda-forge-pinning 2025.02.03.10.35.56
…nda-forge-pinning 2025.02.03.10.35.56
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
…nda-forge-pinning 2025.02.03.10.35.56
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13112822110. Examine the logs at this URL for more detail. |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Cool that you're reviving this feedstock - it could really use a maintainer! :) I tried this a while ago, here are some relevant notes |
|
Thanks @h-vetinari! needed it for a project and realised the version in cf is quite outdated. Lets see if I can crack it. |
|
Arggg almost there! but the OSX build is failing with some linker error right at the end: |
|
Ok @h-vetinari, I got it building. Feel free to add me as maintainer. Would be great if you give the PR a review :P |
|
Great news! 👏
Can you add yourself in this PR?
Many of them, yes (because those have been closed in the meantime and a rerender from the global pinning does the same as they would have done then).
let me have a look :) |
h-vetinari
left a comment
There was a problem hiding this comment.
Looks alright, just a few things that need cleaning up (+ a rerender)
|
Not sure what's wrong with the osx builds just now. I restarted, but it happened again in both jobs: It also happens before the recipe is actually run (and the rerender commit changed nothing of consequence on osx) Beyond that, looking at the last passing run, there's a few more things that need fixing. For example, we end up shipping which should be solvable by adding We also end up reshipping kokkos, which likewise needs to go away: More importantly, it seems that trilinos sets its own version as the SOVERSION for all its vendored libraries (actual versions see here), so this would conflict and possibly break badly together with the actual kokkos. |
…nda-forge-pinning 2025.02.10.08.21.42
|
Other feedstocks OSX builds are failing, I reckon this is some transient issue outside the scope of this feedstock... |
|
The builds now fail with this message at config time: It seems like Trilinos needs a very specific version of kokkos to compile. Alas, the required one is not on conda-forge: I do not know what the best course of action is here. It does not make sense for someone wanting kokkos to install the whole of trilinos. Kokkos is a part of trilinos, so if conda-forge shipping that separately, should this feedstock be split into many, one for each trilinos package? |
The best course of action IMO is to patch out the too-tight constraint in tpetra and keep depending on our own kokkos here. Even more so because (due to kokkos' silly version scheme, where patch versions have a leading 0), there isn't actually a v4.3.1 of kokkos.
One does not necessarily imply the other. Unvendoring kokkos (and potentially other pieces of trilinos that we might be shipping separately already) does not mean that the package has to be split into many components. It just means that trilinos should first and foremost make use of the existing packages, unless very strong reasons not to materialize. |
|
Makes sense to me, seems like TPetra can be coerced into trying any kokkos version: |
|
Compiles fine but then fails with this: |
|
Just add - libgomp # [linux]
- llvm-openmp # [osx]in host, those should have the right run-exports. |
|
Trying to build using conda-forge's kokkos-kernels, seems to fail finding it: Probably due to the kokkos-kernels feedstock being at version 4.1. Perhaps that should be updated before moving on here. But that feedstock also looks abandoned. |
|
Updated version in #58, if other features are still desired please feel free to start a new PR. |
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)Closes #42