-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error on install: "subslice patterns are unstable" #323
Comments
The nightly version has not changed (see rust-toolchain). What system are you on? If you are comfortable using docker, you can pull down one of the provisioned images here and see if the build steps also fail in that environment - if they don't, there might be a problem with the host environment. |
I just had the same problem. |
Just had the same error, that got fixed by
|
This fix worked for me, I was able to successfully install c2rust. Thank
you!
…On Sat, Jan 30, 2021, 6:17 AM jperon ***@***.***> wrote:
Just had the same error, that got fixed by --locked. But, for
information, it raises two warnings:
warning: package `miow v0.3.5` in Cargo.lock is yanked in registry `crates.io`, consider running without --locked
warning: package `socket2 v0.3.15` in Cargo.lock is yanked in registry `crates.io`, consider running without --locked
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#323 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNCQX5IH5RHETZTORS2RY3S4PTD5ANCNFSM4WPQUGRA>
.
|
I'm unable to build even with
|
@osa1 this issue is about the problem with subslice patterns. Since your problem is another one, please open a separate issue for this. When you do, please include information about your build environment (macOS, Linux? If Linux, what distro, what c++ compiler are you using?). Off the top of my head, it looks like a problem with your toolchain but it is hard to say without more information. |
@elichai Ohhh, thank you! I would never guess that's the reason. |
@nobuyuki As @thedataking said, that's unrelated to the current issue. No need to mix up different things in the same thread, as it pings everyone who's only interested in the current bug - please create a new issue instead. |
Closing now that we're able to build on stable and newer nightlies. |
Hi,
I recently tried to install c2rust using the README instructions. I installed the nightly-2019-12-05 toolchain, and ran
cargo +nightly-2019-12-05 install c2rust
. Unfortunately, I kept getting the following build error in several places.However, when I compile on the latest version I get past this error. However, I get a different one:
Is it possible that the targeted version of Nightly has changed without updating the README? Is there anything else I should try to install c2rust successfully?
The text was updated successfully, but these errors were encountered: