-
Notifications
You must be signed in to change notification settings - Fork 466
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
FFMpeg will not link to 2.1.1 release built as shared library #766
Comments
I believe this is now solved upstream. Closing. |
Mathieu Malaterre wrote:
What kind of believed upstream do you mean? winfried libavcodec/libopenjpegdec.o: In function |
that seemed to me like an exact duplicate of #802. Am I wrong ? |
@malaterre , I have made a test. FFMPEG compiles bug-free with openjpeg-1.5.x . So I made a copy of openjpeg2-git-2016-09-21-1/src/lib/openjp2/openjpeg.h . In openjpeg.h I Then I inserted at line 79 the respective lines of openjpeg-1.5.3-1/libopenjpeg/openjpeg.h, Now I was able to compile and install ffmpeg-3.1.3 bug-free. winfried |
@malaterre , I used the following compilers: gcc (GCC) 5.3.0 (Linux 4.7.3) winfried |
@szukw000 you should instead follow instructions from: #802 (comment) |
FFMPeg will link with the 2.1 release.
It seems that a recent change to visibility of symbols is the cause: if OPJ_STATIC is defined,
then API symbols are marked "hidden". However, FFMpeg always defines OPJ_STATIC when linking, even for dynamic builds. So, linking fails in this case.
The reason why FFMpeg always define OPJ_STATIC is because of mingw builds: mingw doesn't mangle names like gcc,
The text was updated successfully, but these errors were encountered: