Skip to content
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[E0635]: unknown feature stdsimd #200

Closed
ArunGust opened this issue Feb 6, 2024 · 19 comments
Closed

error[E0635]: unknown feature stdsimd #200

ArunGust opened this issue Feb 6, 2024 · 19 comments

Comments

@ArunGust
Copy link

ArunGust commented Feb 6, 2024

unknown feature stdsimd : Got below after updating rust to new version rustc 1.78.0-nightly (f067fd608 2024-02-05)

error[E0635]: unknown feature stdsimd
--> C:\SYSTEM\RUST\CARGO\registry\src\index.crates.io-6f17d22bba15001f\ahash-0.7.7\src/lib.rs:33:42
|
33 | #![cfg_attr(feature = "stdsimd", feature(stdsimd))]
| ^^^^^^^

For more information about this error, try rustc --explain E0635.
error: could not compile ahash (lib) due to 1 previous error

@tusharmath
Copy link

Facing similar issue.

@tmpfs
Copy link

tmpfs commented Feb 6, 2024

Same here on version 0.7.7, it's broken my crate's documentation build on docs.rs but works fine for me locally on Linux and MacOS, not sure why it's only broken in the docs.rs sandbox environment.

Here is the build log:

https://docs.rs/crate/sos-sdk/0.10.0/builds/1116456

@Kobzol
Copy link

Kobzol commented Feb 6, 2024

This is caused by rust-lang/rust#117372. This problem in ahash was already fixed in #183, which was released in 0.8.7 (it just isn't visible as a GitHub release).

@RalfJung
Copy link

RalfJung commented Feb 6, 2024

Fundamentally this is caused by logic in build.rs that auto-enables a nightly feature when it detects that it is built with a nightly rustc. Such logic is fragile and prone to errors as nightly features evolve before stabilization.

Crates should never automatically enable nightly features, this should generally be opt-in. If they try to do it automatically they need to be very careful and account for the fact that nightly features are not stable, and might look very different in future nightly versions.

I see aHash still does the same kind of auto-detection with the specialize feature. That's a similar issue just waiting to happen.

@humb1t
Copy link

humb1t commented Feb 6, 2024

Same for me

@mina86
Copy link

mina86 commented Feb 6, 2024

If you’re on 0.8 branch → update to 0.8.7. See #188.

However, I’m also picking up dependency on 0.7.7 through chain of older dependencies (borsh 0.9 → hashbrown 0.11 → ahash 0.7) which I can’t easily get rid of on my side. It’d be fantastic if we could get backport to 0.7 branch as well. I’ve commented that in #188.

@Kobzol
Copy link

Kobzol commented Feb 6, 2024

It seems that a lot of stuff depends on ahash < 0.8. It would be indeed useful if it was possible to put out a backported patch release for 0.7.

cratelyn added a commit to penumbra-zone/penumbra that referenced this issue Feb 6, 2024
conorsch pushed a commit to penumbra-zone/penumbra that referenced this issue Feb 6, 2024
conorsch pushed a commit to penumbra-zone/penumbra that referenced this issue Feb 6, 2024
@vikingSec
Copy link

vikingSec commented Feb 6, 2024

Seems like this is breaking trunk and leptos

I was just trying to get into learning leptos, so installing all of the right versions according to the docs and trying to install trunk and cargo-leptos both runs into this bug.

Console output:

> cargo install trunk
error[E0635]: unknown feature `stdsimd`
  --> /Users/medwards/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ahash-0.7.7/src/lib.rs:33:42
   |
33 | #![cfg_attr(feature = "stdsimd", feature(stdsimd))]
   |                                          ^^^^^^^

For more information about this error, try `rustc --explain E0635`.
error: could not compile `ahash` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile `trunk v0.18.7`, intermediate artifacts can be found at `/var/folders/9f/w50rg2wj193fh6jv5rt0lk1r0000gn/T/cargo-installif2CRL`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path. 

Not trying to brigade the comments, I'd work on a fix but you probably don't want a Rust noop running around your repo.

benluelo added a commit to unionlabs/union that referenced this issue Mar 18, 2024
also added a way to configure the channel when building a rust
toolchain, since we needed an older nightly version to build `libwasmvm`
(see tkaitchuck/aHash#200)
hasura-bot pushed a commit to hasura/graphql-engine that referenced this issue Mar 27, 2024
V3_GIT_ORIGIN_REV_ID: a36abced11359755423356f8a2311ae4514978de
goweiwen added a commit to goweiwen/Allium that referenced this issue May 12, 2024
tgross35 added a commit to tgross35/mic2 that referenced this issue May 30, 2024
eightfilms pushed a commit to eightfilms/noname that referenced this issue Jun 3, 2024
`ahash 0.7.7` uses the removed `stdsimd` feature causing the CI failure on `main`,
so this PR simply updates it to `0.7.8` with `cargo update -p ahash`.

See: tkaitchuck/aHash#200
eightfilms pushed a commit to eightfilms/noname that referenced this issue Jun 3, 2024
`ahash 0.7.7` uses the removed `stdsimd` feature causing the CI failure on `main`,
so this PR simply updates it to `0.7.8` with `cargo update -p ahash`.

See: tkaitchuck/aHash#200
eightfilms pushed a commit to eightfilms/noname that referenced this issue Jun 3, 2024
Fixes the `stdsimd` feature issue that is causing gh-pages action to fail.

See: tkaitchuck/aHash#200
HampusMat added a commit to HampusMat/Syrette that referenced this issue Jul 10, 2024
Older versions of ahash break with Rust 1.78
tkaitchuck/aHash#200
jonhoo added a commit to jonhoo/inferno that referenced this issue Jul 14, 2024
jonhoo added a commit to jonhoo/inferno that referenced this issue Jul 14, 2024
jackronaldi pushed a commit to lightning-signer/validating-lightning-signer that referenced this issue Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests