-
Notifications
You must be signed in to change notification settings - Fork 749
ImportError undefined symbol _ZTIPi on import clr
#939
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
Comments
Looks like this is the same issue as is being discussed here #925 (comment) Temporary workaround is to revert and pin mono to 5.20.1 |
It doesn't work for me with older versions of mono:
Tried with older version as well, didn't work:
How can I make it work? |
|
Thanks @filmor, I didn't notice that package had higher version, now it works, thanks. |
Is that still an issue? I just ran into this using pythonnet 2.4 with a dotnetcore2.0 build and having latest mono-devel installed which is, at time of writing, 6.8.0. |
I think I figured out the root cause, but don't know yet what is the proper way to fix it: mono/mono#19628 TL;DR; properly linking libmono from Mono 6.8 requires C++ linker or to manually specify C++ stdlib to be linked with C linker (e.g. ...
libs = mono_libs.strip() + " " + glib_libs.strip() + " -lstdc++"
... I'll wait for Mono response to give us a supported way to do this. |
Aaaand after getting pythonnet successfully install with this workaround I hit #1034 |
The C++ linker does a bit more than just |
And the module functions need to be |
Environment
pythonnet installed inside a virtualenv
Details
Importing the clr library results in an import error:
Minimal example:
This had been working just fine, however it looks like libmonosgen-2.0.so.1 updated on the 9th and I think that's what is the cause of this issue. Rebuilding completely from scratch in a fresh virtualenv doesn't fix this problem.
The text was updated successfully, but these errors were encountered: