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
single branch builds for mumps-seq, mumps-mpi #36
Conversation
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 ( |
if no outputs match the top-level name
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:
|
- call the seq package mumps-seq (no more mumps package) - mumps-include package for shared headers used for both mumps-seq, mumps-mpi, unix-only - _seq.a suffix for mumps-seq libs (matches debian packaging) - libseq headers in include/mumps_seq (matches debian packaging)
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 ( |
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:
|
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 ( |
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:
|
so ~dp0 is the recipe dir, not where we want it
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 ( |
- no headers in mumps-mpi (mumps-headers covers that) - mpi.h, mpif.h from libseq go in include/mumps_seq (no others from libseq)
ok, I believe this is entirely ready to go now |
Great work! Hopefully this will lead to fewer problems when using kwant + Fenics. |
Should we do a local test build of kwant with the new mumps-seq to make sure this works? |
it should have no hash inputs
I did a local build of kwant but found an issue. This is creating two builds of mumps-include which are pinned exactly as a dependency but have different hash inputs. Fixing the build string on mumps-include should do it. |
mumps-seq doesn’t need this because it’s a new package but once a package has made the mistake of adopting the blas_openblas feature, it cannot drop it until conda-forge moves to blas 2.0 metapackage
use x.x.x pinning instead of exact seems to cause weird package-not-found errors on Windows (surely a conda-build bug)
I was able to use the latest commit (18edb09) and |
@basnijholt any more testing you want to do before landing this one? |
Thanks a lot for testing! I have complete faith in that it will work 👍 I'll merge this now. |
So the cf automation tools can update both flavors.
I'd like to resolve #34 here as well. Until/unless I hear otherwise,
I will implement option 4 there: produce a
mumps-seq
andmumps-mpi
package,where
mumps-seq
gets_seq
suffixes on its libs and its headers go ininclude/mumps_seq
.mumps-mpi
remains unchanged. This follows a pattern established by the debian packaging of mumps and mumps-seq (there mumps is mumps-mpi, but I don't want to do that here, since it will break everything currently depending on serial mumps).The
mumps
package will be deprecated but not removed so that nothing breaks.TODO:
mumps
tomumps-seq
_seq
to mumps-seq librariesinclude/mumps_seq
mumps-include
package for the common headers