Repository navigation
Issues installing 0.4.0 with binstall #691
Closed
DavidAntliff
started this conversation in
General
Replies: 3 comments 2 replies
|
True. But its a bit different. Binstall sees our Cargo.toml first then determines if it should install or not install rustowlc. As we move fast (and dont have a dev branch sadly) it breaks. On the rustc side, expected as we are using rustc internals which are unstable. Try with RUSTC_BOOTSTRAP=1. |
1 reply
|
Under windows you tend to see something like this cargo binstall rustowl
INFO resolve: Resolving package: 'rustowl'
WARN resolve: Error while downloading and extracting from fetcher github.com: I/O Error: The filename, directory name, or volume label syntax is incorrect. (os error 123)
ERROR Fatal error:
\x1b[31m×\x1b[0m For crate rustowl: Fallback to cargo-install is disabled
\x1b[31m ╰─▶ \x1b[0mFallback to cargo-install is disabledSince there's been some issues getting the winget package through
|
1 reply
|
Also you can build from rustowl git easily, I have updated to 1.98.1 compiler. Still binstall fails (needs a new release) but there are better options.... |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I am a human, but what follows is an AI-generated report based on my personal experiences, as I don't think I could have explained it better myself, and I don't understand the inner workings of
binstall/ crates.io well enough to debug this manually.If it is preferred that I file this as an issue, I'm happy to do so, just let me know.
It's quite likely that this is an issue exacerbated by my environment, so let me know if there's something I should try instead.
v0.4.0: binstall fails (
rustowlcmissing from release archive), and thecargo installfallback also failscargo install-update rustowl(which shells out tocargo-binstall) fails on v0.4.0:The v0.4.0 release assets contain only
rustowl-<target>andrustowl-<target>.tar.gz— norustowlc. The published manifest still declaresrustowlcas a non-optional bin target, so binstall requires it in the archive and aborts. This affects the install method the README recommends for the Neovim plugin (build = 'cargo binstall rustowl').cargo install rustowl@=0.4.0buildsrustowlfine but fails onrustowlc, which linksrustc_private:Adding
rust-src rustc-dev llvm-tools-previewis not sufficient. On current stable,rustowlcfails with E0554 (#![feature(rustc_private)]is not usable on the stable channel) plus API-drift errors —rustc_data_structures::stable_hasheris nowstable_hashandStableHashingContextis nowStableHashCtxt.The crates.io package doesn't include
rust-toolchain.toml, socargo installbuildsrustowlcagainst whatever the user's default toolchain is, which breaks as soon as rustc internals move past the supported version (1.95 for 0.4.0). With binstall also broken on 0.4.0, there is currently no working install path from crates.io — only the prebuilt release binary.Environment
All reactions