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

Compiling error: there is no argument named ... #7

Closed
Ecoleaf1 opened this issue Apr 10, 2022 · 4 comments
Closed

Compiling error: there is no argument named ... #7

Ecoleaf1 opened this issue Apr 10, 2022 · 4 comments

Comments

@Ecoleaf1
Copy link

Ecoleaf1 commented Apr 10, 2022

Compiling with cargo install bore-cli prints out a few there is no argument named errors. This is running on a fresh ubuntu (version 20.04) within a container, with only Rust installed.

root@96d3d25c45a9:/# cargo install bore-cli
    Updating crates.io index
  Installing bore-cli v0.2.1
   Compiling libc v0.2.122
   Compiling proc-macro2 v1.0.37
   Compiling version_check v0.9.4
   Compiling unicode-xid v0.2.2
   Compiling autocfg v1.1.0
   Compiling cfg-if v1.0.0
   Compiling syn v1.0.91
   Compiling typenum v1.15.0
   Compiling memchr v2.4.1
   Compiling log v0.4.16
   Compiling lazy_static v1.4.0
   Compiling smallvec v1.8.0
   Compiling parking_lot_core v0.9.2
   Compiling serde_derive v1.0.136
   Compiling scopeguard v1.1.0
   Compiling cc v1.0.73
   Compiling serde v1.0.136
   Compiling subtle v2.4.1
   Compiling adler v1.0.2
   Compiling once_cell v1.10.0
   Compiling gimli v0.26.1
   Compiling serde_json v1.0.79
   Compiling hashbrown v0.11.2
   Compiling heck v0.4.0
   Compiling anyhow v1.0.56
   Compiling pin-project-lite v0.2.8
   Compiling rustc-demangle v0.1.21
   Compiling termcolor v1.1.3
   Compiling textwrap v0.15.0
   Compiling ansi_term v0.12.1
   Compiling bytes v1.1.0
   Compiling ryu v1.0.9
   Compiling strsim v0.10.0
   Compiling bitflags v1.3.2
   Compiling itoa v1.0.1
   Compiling cpufeatures v0.2.2
   Compiling hex v0.4.3
   Compiling tracing-core v0.1.24
   Compiling sharded-slab v0.1.4
   Compiling thread_local v1.1.4
   Compiling generic-array v0.14.5
   Compiling proc-macro-error-attr v1.0.4
   Compiling proc-macro-error v1.0.4
   Compiling lock_api v0.4.7
   Compiling miniz_oxide v0.4.4
   Compiling indexmap v1.8.1
   Compiling backtrace v0.3.64
   Compiling tracing-log v0.1.2
   Compiling tracing-subscriber v0.3.11
   Compiling object v0.27.1
   Compiling os_str_bytes v6.0.0
   Compiling quote v1.0.17
   Compiling num_cpus v1.13.1
   Compiling getrandom v0.2.6
   Compiling socket2 v0.4.4
   Compiling mio v0.8.2
   Compiling atty v0.2.14
   Compiling signal-hook-registry v1.4.0
   Compiling parking_lot v0.12.0
   Compiling addr2line v0.17.0
   Compiling dashmap v5.2.0
   Compiling block-buffer v0.10.2
   Compiling crypto-common v0.1.3
   Compiling digest v0.10.3
   Compiling sha2 v0.10.2
   Compiling hmac v0.12.1
   Compiling tracing-attributes v0.1.20
   Compiling clap_derive v3.1.7
   Compiling tokio-macros v1.7.0
   Compiling tokio v1.17.0
   Compiling tracing v0.1.33
   Compiling clap v3.1.8
   Compiling uuid v0.8.2
   Compiling bore-cli v0.2.1
error: there is no argument named `message`
  --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.1/src/client.rs:47:73
   |
47 |             Some(ServerMessage::Error(message)) => bail!("server error: {message}"),
   |                                                                         ^^^^^^^^^

error: there is no argument named `to`
  --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.1/src/client.rs:55:29
   |
55 |         info!("listening at {to}:{remote_port}");
   |                             ^^^^

error: there is no argument named `remote_port`
  --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.1/src/client.rs:55:34
   |
55 |         info!("listening at {to}:{remote_port}");
   |                                  ^^^^^^^^^^^^^

error: there is no argument named `to`
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.1/src/client.rs:120:52
    |
120 |     .with_context(|| format!("could not connect to {to}:{port}"))
    |                                                    ^^^^

error: there is no argument named `port`
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.1/src/client.rs:120:57
    |
120 |     .with_context(|| format!("could not connect to {to}:{port}"))
    |                                                         ^^^^^^

error: could not compile `bore-cli` due to 5 previous errors
warning: build failed, waiting for other jobs to finish...
error: failed to compile `bore-cli v0.2.1`, intermediate artifacts can be found at `/tmp/cargo-installwbzfEn`

Caused by:
  build failed
@erfan-khadem
Copy link

erfan-khadem commented Apr 10, 2022

How did you install Rust? Is it up to date?
I compiled (both from git repo manually and cargo install) using both rustc 1.62.0-nightly (e745b4ddb 2022-04-07) and rustc 1.60.0 (7737e0b5c 2022-04-04) and it seems to work on my machine (Arch).

Maybe you are running some version < 1.58? Because that is when Format Strings were introduced.

@AlbanMinassian
Copy link

same problem before rustup update. no build error after rustup update :-)
thank @er888kh

@Ecoleaf1
Copy link
Author

Cheers @er888kh and @AlbanMinassian! Turns out the default ubuntu repository was outdated, updating to 1.60.0 fixes my problem (removing rust in the default repository, then installing Rust via https://rustup.rs/).

@ekzhang
Copy link
Owner

ekzhang commented Apr 10, 2022

Thanks for reaching out about this! Indeed, this format string syntax is a feature introduced in Rust 1.58.0, so you'll need at least Rust 1.58 to build bore. In general I've only tested compilation on the latest stable version of Rust (1.60).

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

4 participants