bug: `kit update` error [SOLVED]
Closed this issue · 2 comments
dr-frmr commented
Describe the bug
Getting a strange error trying to run kit update
.
kit update
ERROR src/build/mod.rs:33: error: Command `cargo ["install", "--git", "https://github.com/kinode-dao/kit", "--branch", "master", "--color=always"]` failed with exit code 101
stdout:
stderr: Updating git repository `https://github.com/kinode-dao/kit`
Installing kit v0.3.1 (https://github.com/kinode-dao/kit?branch=master#b5612955)
Updating crates.io index
Updating git repository `https://github.com/kinode-dao/process_lib.git`
Updating git repository `https://github.com/alloy-rs/alloy.git`
Updating git repository `https://github.com/bytecodealliance/wit-bindgen`
Downloading crates ...
Downloaded either v1.11.0
Downloaded anyhow v1.0.82
Downloaded quote v1.0.36
Downloaded strsim v0.11.1
Downloaded time-macros v0.2.18
Downloaded rmp v0.8.14
Downloaded rmp-serde v1.2.0
Downloaded jobserver v0.1.30
Downloaded getrandom v0.2.14
Downloaded serde_derive v1.0.198
Downloaded proc-macro2 v1.0.81
Downloaded serde v1.0.198
Downloaded cc v1.0.94
Downloaded backtrace v0.3.71
Downloaded time v0.3.36
Downloaded serde_json v1.0.116
Downloaded winnow v0.6.6
Downloaded syn v2.0.60
Downloaded h2 v0.3.26
Downloaded encoding_rs v0.8.34
Compiling proc-macro2 v1.0.81
Compiling unicode-ident v1.0.12
Compiling libc v0.2.153
Compiling serde v1.0.198
Compiling cfg-if v1.0.0
Compiling pkg-config v0.3.30
Compiling version_check v0.9.4
Compiling itoa v1.0.11
Compiling autocfg v1.2.0
Compiling pin-project-lite v0.2.14
Compiling once_cell v1.19.0
Compiling log v0.4.21
Compiling typenum v1.17.0
Compiling anyhow v1.0.82
Compiling semver v1.0.22
Compiling vcpkg v0.2.15
Compiling tracing-core v0.1.32
Compiling serde_json v1.0.116
Compiling ryu v1.0.17
Compiling generic-array v0.14.7
Compiling slab v0.4.9
Compiling futures-core v0.3.30
Compiling bitflags v2.5.0
Compiling hashbrown v0.14.3
Compiling memchr v2.7.2
Compiling fnv v1.0.7
error[E0658]: use of unstable library feature 'proc_macro_byte_character'
--> /Users/benj/.cargo/registry/src/index.crates.io-6f17d22bba15001f/proc-macro2-1.0.81/src/wrapper.rs:871:21
|
871 | proc_macro::Literal::byte_character(byte)
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #115268 <https://github.com/rust-lang/rust/issues/115268> for more information
= help: add `#![feature(proc_macro_byte_character)]` to the crate attributes to enable
= note: this compiler was built on 2024-03-27; consider upgrading it if it is out of date
error[E0658]: use of unstable library feature 'proc_macro_c_str_literals'
--> /Users/benj/.cargo/registry/src/index.crates.io-6f17d22bba15001f/proc-macro2-1.0.81/src/wrapper.rs:898:21
|
898 | proc_macro::Literal::c_string(string)
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #119750 <https://github.com/rust-lang/rust/issues/119750> for more information
= help: add `#![feature(proc_macro_c_str_literals)]` to the crate attributes to enable
= note: this compiler was built on 2024-03-27; consider upgrading it if it is out of date
Compiling equivalent v1.0.1
Compiling lazy_static v1.4.0
For more information about this error, try `rustc --explain E0658`.
error: could not compile `proc-macro2` (lib) due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
error: failed to compile `kit v0.3.1 (https://github.com/kinode-dao/kit?branch=master#b5612955)`, intermediate artifacts can be found at `/var/folders/wg/rgvtftcs7hl7ynmzkxcm77sh0000gn/T/cargo-installgIQoDN`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
ERROR src/update/mod.rs:8: error: Command `cargo ["install", "--git", "https://github.com/kinode-dao/kit", "--branch", "master", "--color=always"]` failed with exit code 101
Desktop (please complete the following information):
- OS: macOS
- Kinode version 0.6.2
- kit version ?
dr-frmr commented
Weirdly I can build the repo just fine.
dr-frmr commented
Turns out this is solved for me just by updating my compiler.
Let's leave this open for a bit to provide help if anyone hits the same thing: just run rustup update
.