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

import error : avpriv_vga16_font #5

Open
AlexDupont93 opened this issue Jan 24, 2017 · 4 comments
Open

import error : avpriv_vga16_font #5

AlexDupont93 opened this issue Jan 24, 2017 · 4 comments

Comments

@AlexDupont93
Copy link

Hi,

when importing h264decode, I run into the following issue:
h264decode.so : undefined symbol avpriv_vga16_font

Do you know how to fix this?
I have tested with ffmpeg 2.4, 2.3.6 and the newest version as well. Running python 2.7 on raspbian.

tzwenn added a commit that referenced this issue Jan 25, 2017
@tzwenn
Copy link
Owner

tzwenn commented Jan 25, 2017

That's quite interesting, since avpriv_vga16_font is part of avutil, but never referenced by me.
I pushed a small change, that now explicitly links against libavutil.
Can you recompile and check with ldd build/lib.*/h264decode.so | grep avutil whether it is now properly found?

@tzwenn
Copy link
Owner

tzwenn commented Jan 25, 2017

Also: Did you install libavutil-dev, or however the package is called on raspbian?

@AlexDupont93
Copy link
Author

Thanks for the quick reply !

I've installed the new version, libavutil-dev and libx264-dev, however now I get the error :
File "testh264.py", line 1, in
import h264decode
ImportError: /usr/local/lib/python2.7/dist-packages/h264decode.so: undefined symbol: x264_bit_depth

I've also tried compiling x264 from source and installing it.

Any thoughts?

@tzwenn
Copy link
Owner

tzwenn commented Jan 27, 2017

Check agin which version of avcodec is currently linked by running ldd build/lib.*/h264decode.so and furthermore check wether this is using x264 and some point (also by ldd).

It seems to me you've got quite a zoo of libraries now on your system.
Since I'm not referring to x264_bit_depth anywhere in my module, your number of conflicting versions of ffmpeg/x264 and so forth may be the issue here.

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

2 participants