-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
patch for setting install_name during install #23
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 ( |
LGTM 👍 @jakirkham @grlee77 what do you think? |
I am not familiar enough with 1.) In short, this patch only modifies behavior on OS X and causes the dynamic libraries to use e.g. 2.) Do we know that |
According to the variables in the Makefiles, it would be
We know that suitesparse is setting the compatibility version in its dylibs, so at least the libraries themselves claim compatibility at the major version level. I can't speak for the project in general, but a cursory test of a conda package compiled against 4.5.3 updated manually to load 4.5.4 does work. |
sorry this PR has gone neglected. I think now the build number should be bumped to 202 since the OpenBLAS update bumped it to 201. @minrk: Is this otherwise good to go? if interested, please add yourself as a maintainer as well |
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
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 ( |
According to the ABI report for SuiteSparse it appears that at least 4.5 has been stable across patch release. Before that it was static libraries that are fairly old, which makes it hard to say much about its compatibility during that period. |
Should we add a file test to ensure that the library name is as expected? |
Good idea, I'll add a few calls to Aside: it would be cool if conda-build test environments could verify compatibility by running the test env with multiple versions of the built package. In general, a useful pattern for verifying C libs that their linking config is set up correctly:
|
33e96a6
to
e987def
Compare
Sorry for taking so long with the tests. The tests are here now, so we can start getting a suitesparse with correct linking on mac. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add compilers and remove openblas
pinning?
recipe/meta.yaml
Outdated
@@ -10,10 +10,13 @@ source: | |||
fn: SuiteSparse-{{ version }}.tar.gz | |||
url: http://faculty.cse.tamu.edu/davis/SuiteSparse/SuiteSparse-{{ version }}.tar.gz | |||
sha256: de5fb496bdc029e55955e05d918a1862a177805fbbd5b957e8b5ce6632f6c77e | |||
patches: | |||
- install_name.patch | |||
|
|||
build: | |||
skip: true # [win] | |||
number: 200 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove this line?
recipe/meta.yaml
Outdated
|
||
build: | ||
skip: true # [win] | ||
number: 200 | ||
number: 201 | ||
features: | ||
- blas_{{ variant }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add
run_export:
- {{ pin_subpackage("suitesparse") }}
here?
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 ( |
This is now also a full conda-build 3 update per @isuruf's request. |
patch submitted upstream
master has been updated since this PR was opened
Rebased again |
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 ( I do have some suggestions for making it better though... 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 ( |
I think this is good to go now (and has been for a year or so). Anything else blocking the merge? |
👍 |
now redundant with conda-forge-pinning
Conflicts resolved again, build number bumped again. |
All builds have succeeded. This should be ready to go again. Not sure why osx shows as still queued, since it's succeeded a while ago. |
- move pinning to conda_build_config.yaml pin_run_as_build - add host - cb3 compiler spec
I've submitted this patch upstream. Not sure yet if it will be accepted.
closes #22