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
[Bug]: python3.7/site-packages/matplotlib/ft2font.so: Undefined symbol "FT_Done_Glyph" #21202
Comments
For this code this same python3.7/site-packages/matplotlib/ft2font.so: Undefined symbol "FT_Done_Glyph" |
You have a crossed up install, and probably need to try again. I strongly recommend conda. |
What you mind "crossed up install"?
I uninstall again, and no changes. freetype-config --version |
I recommending do test on freebsd12 if can do somebody to confirm that working. |
I do not think that this is a OS/platform issue (I fully expect Matplotlib to work on freeBSD given that https://www.freshports.org/math/py-matplotlib/ exists), but rather a local installation issue. How did you install Matplotlib and which freetype so is the linker finding at run time? From the error I believe that you built Matplotlib with one version of freetype, but are finding a different one at run time. To debug this we will need to know how you installed Matplotlib (did you get a wheel or build it locally?), what compiler you are using (from conversation in gitter I think you are using llvm?), did you use the system freetype? How did you make your virtual env? Without this information (and without access to a freeBSD system set up exactly as your is), the best we can do is guess. |
Matplotlib was installed by pip and whole process was done in this way, this same other versions.
Not sure about this question. What you mind? I'm not touching this in other way than simple usage of import matplotlib. |
I try without venv and this same.
|
Looks was this type issue related to compiler |
So you are building from source (rather than grabbing a wheel). Something is clearly going wrong with the linking, but without a freebsd system I can not debug further. I suggest looking at the MAKEFILE in the port to see what they are doing. It might be helpful to post the output of |
after pip install -v matplotlib. ..part of long log
|
Adding bether log |
Please post results of which pip and which python. Try 'python -m pip install matplotlib'. Those warning above really make it look like your pip is for python2 |
pip --version How is possible that pip is for python2 when python38? Anyway I try.. and no effect, this same. After install on python27 matplotlib-2.2.5.tar.gz for test, working. Also no relation with problems around ft2font.so?
|
FreeBSD 12 ships with Python 3.8, so I'm not sure where you got 3.6 or 3.7 from. And I don't know where you got this wheel from:
but you should delete all the matplotlib wheels you have and build again cleanly. |
Well.. after delete cache etc. now this type line not exist.. but it was just cache.. |
You have gcc installed, and the FreeType configure finds that instead of clang which is being used by Python, and something gets broken with mixed compilers (probably LTO). You can work around that by exporting |
@QuLogic I can confirm that working now. Some requiments for kiwisolver is needed only. Thx.
|
Thank you for reporting this @ManPython ! |
Otherwise, mixed compilers might break things when compiled together into the extension. Fixes matplotlib#21202
Otherwise, mixed compilers might break things when compiled together into the extension. Fixes #21202
ManPython commentedSep 27, 2021
•
edited
Bug summary
python3.7/site-packages/matplotlib/ft2font.so: Undefined symbol "FT_Done_Glyph"
https://stackoverflow.com/questions/34226818/undefined-reference-to-ft-load-glyph-and-other-sdl2-ttf-functions-using-cmak
Does matplotlib support this function on FreeBSD ?
Code for reproduction
Actual outcome
Expected outcome
Chart
Operating system
FreeBSD
Matplotlib Version
matplotlib-3.4.3
Matplotlib Backend
No response
Python version
Python 3.7.9
Jupyter version
6.0.1
Other libraries
No response
Installation
pip
Conda channel
No response
The text was updated successfully, but these errors were encountered: