-
Notifications
You must be signed in to change notification settings - Fork 27
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
error[E0432]: unresolved import platform
#57
Comments
Hi @i18n-now, can you please share the output of |
I am also running into this probably, 3.1.0, compiling on AMD Ryzen 7:
with compile failures:
|
I believe I caused this (see #53), oops. This doesn't make a whole lot of sense, since both of your systems support both |
v3.1.0 will work just fine if used with the |
Yeah I just saw this issue rust-lang/rust#80633 and
Maybe, but runtime feature detection has drawbacks. In the meantime it's best to address this regression even if the solution isn't perfect |
I've tried doing build-time feature detection. It's not perfect in the current state but it works nicely on my side. You can try it by referencing the branch: gxhash = { git = "https://github.com/ogxd/gxhash.git", branch = "build-time-feature-detection" } Please let me know if that works for you (or doesn't). |
Also experiencing this issue on an Intel i5-1035G4, using Linux Mint 21.2. Same errors as others have sent. |
After trying the
|
Oops my bad, I just fixed that |
I'm not sure if the solution I proposed above is the correct way to address this. It introduces issues with cross-compilation. I agree with @notsatvrn
I gave runtime feature detection a try with |
Issue addressed with #62, which is simply about adding a check at build-time with a message for better DX to tell the user to enable required target features. Please let me know if this solution works for you (or if it does not) I would have preferred the crate to compile for required target features by itself, but rust does not currently allow this without compromises (such as inlining issues). See this issue for more details: #61 |
The text was updated successfully, but these errors were encountered: