You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is likely a symptom of this terrible, terrible bug: #3660
The problem is that there are two sets of libraries installed, and we rely on the assumption that they are identical when configuring the $PATH environment variable, but that assumption has turned out not to be true for unknown reasons.
One possible terrible, terrible workaround is to add something like C:\Program Files (x86)\rust\bin\rustc\i686-pc-mingw\bin (verify that path on your own install) to the front of $PATH, but only when running the executable (not when running the compiler). That should dynamically load the library with the correct symbol. Alternately, you could just copy the files in that directory to C:\Program Files (x86)\rust\bin, which would make the two sets of libraries the same. It's a mess, sadly.
I'm not sure what the state of Rust syntax highlighting on GitHub is, but here is the issue: #4341.
@cynede - let me know if what @brson suggested works for you, and if it does, I'll close this as a duplicate of #3660. If it doesn't, we'll leave it open for now.
Allow `unused_self` lint at the function level
Another approach of rust-lang#5062.
Fixesrust-lang#5053
changelog: Allow `unused_self` lint at the function level
OS: Windows 7 32 bit, using MinGW version suggested by wiki (because last one just fails)
Trying to compile example from website.
description:
this code works:
but when I add
like
it fails with error :
The procedure entry point ... rand... extension... not found in the .... dll
btw: why does rust code highlighting on github look like plain text?
The text was updated successfully, but these errors were encountered: