-
Notifications
You must be signed in to change notification settings - Fork 749
System.DllNotFoundException when trying to import clr, despite referenced assembly existing #1034
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
After upgrading to Mono 6.11, I get the following, slightly different error:
|
I am experiencing an identical issue. Also on Arch Linux.
|
Judging by stack trace, this must be a Mono issue. You can try reproducing it by opening C# REPL and running |
Compiled mono master branch directly and
Turns out it just wasn't in my path. Fixing that gets me a slightly different error:
|
There's a similar issue open over at mono/mono#17079 So far everyone encountering the issue has been using Arch and Python. |
@Zer0897 as a workaround you could try adding the true path to |
@lostmsu Yeah I was able to get that recognized by adding it to path, but |
I'm actually observing the same issue on my Gentoo system, looking into it. The path is fine, the actual issue (if you run with |
I experienced a similar problem in Ubuntu 18.4, not via For me, the solution was to pre-load
By doing this, the problem went away. It can also be done from code, via |
Same issue on Amazon Linux in SageMaker : https://stackoverflow.com/questions/67212443/pythonnet-on-sagemaker-cannot-import-clr |
@Masutani there's a workaround for 2.4.0 mentioned above. Previews of 3.0.x do not have this issue anymore. |
Environment
Details
Trying to import clr so that I can import a library.
When trying to import this, the following error is thrown:
I'm not sure what is going on, msbuild and mono work just fine, the referenced libmono-native library exists in the location specified (not sure why it drops back a directory, then goes back into lib though?).
The text was updated successfully, but these errors were encountered: