Skip to content
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

Linked to jpeg8 #2

Closed
dopplershift opened this issue Apr 15, 2016 · 2 comments
Closed

Linked to jpeg8 #2

dopplershift opened this issue Apr 15, 2016 · 2 comments

Comments

@dopplershift
Copy link
Member

So the jasper packages I've gotten from conda-forge are linked against jpeg8 (at least on osx):

>otool -L libjasper.dylib
libjasper.dylib:
    @rpath/libjasper.1.dylib (compatibility version 2.0.0, current version 2.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)
    @rpath/libjpeg.8.dylib (compatibility version 13.0.0, current version 13.0.0)

But conda-forge now has jpeg9. This is currently causing CI failures for pygrib, and failures on my system once I remove the homebrew install of jpeg8.

@pelson
Copy link
Member

pelson commented Apr 16, 2016

The correct solution would be to start adding some annotation to the recipe for pinning the jpeg version. I'm extremely frustrated with the lack of progress from conda/conda-build#747. Pinging @kalefranz as this is the number one issue with conda-build right now - I'm happy to help with finding a solution, but it needs some guidance from you in order to find a healthy solution for conda-build.

@ocefpaf
Copy link
Member

ocefpaf commented Apr 16, 2016

The correct solution would be to start adding some annotation to the recipe for pinning the jpeg version.

Indeed. I am preparing PRs to add that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants