-
Notifications
You must be signed in to change notification settings - Fork 456
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
hidden visibility for the static library / building with -DOPJ_STATIC against shared lib #802
Comments
There has been no ABI change. On debian here is what I used to check. I would check my compilation option, and make sure the openjpeg lib is being passed on the linker line. I would close that as invalid, once OP double check. |
Thanks, I'll have a look to see if it's an underlinking issue. It's puzzling though as those two packages built flawlessly against openjpeg 2.1 and there were no big packaging changes on our side. I'll report back once I've investigated further. |
See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203327 for mupdf, which mentions that this issue happens on FreeBSD too due to 3ed5858. Apparently they went with patching mupdf, so I guess I'll try to do the same, and see what can be done for ghostscript. |
I believe this issue can be closed as invalid, unless you consider that those build issues as a consequence of 3ed5858 are an upstream bug and not a downstream misuse of the library. |
For the reference, I hacked ghostscript with this patch and it seems to build properly: http://svnweb.mageia.org/packages/cauldron/ghostscript/current/SOURCES/ghostscript-9.19-openjpeg2-non-static.patch?view=markup&pathrev=1043163 |
This is also an issue for FFmpeg: #766 |
@malaterre what would be your advice to fix this issue (and #766) ? |
@detonin other than keeping this issue open for reference, I believe this can simply be closed. If I understand correctly @mayeut from: #804 (comment) it seems OPJ does not use an old hack to get symbol export from static lib anymore. |
Hi there,
We recently updated openjpeg from 2.1 to 2.1.1 in Mageia to address the various security issues it fixes (Mageia bug report for the reference).
The release announcement promises no API/ABI break, but our experience of rebuilding some openjpeg reverse dependencies seems to show otherwise:
Is this an expected change, or an unwanted API breakage?
The text was updated successfully, but these errors were encountered: