When running ./scripts/cli/start_cli_testnet.sh, the script failed:
failed to run custom build command for backtrace-sys v0.1.28
then fixed this with brew doctor related commands
```mkdir /tmp/includes
brew doctor 2>&1 | grep "/usr/local/include/" | awk '{$1=$1;print}' | xargs -I _ mv _ /tmp/includes
but now have this:
error: internal compiler error: src/librustc_mir/transform/generator.rs:714: Broken MIR: generator contains type std::option::Option
--> network/src/connectivity_manager/mod.rs:119:44
|
119 | async fn check_connectivity(&mut self) {
| ____________________________________________^
120 | | // Ensure we are only connected to eligible peers.
121 | | let stale_connections: Vec<_> = self
122 | | .connected
... |
180 | | }
181 | | }
| |_____^
thread 'rustc' panicked at 'Box
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.
error: aborting due to previous error
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: rustc 1.37.0-nightly (b25ee6449 2019-06-17) running on x86_64-apple-darwin
note: compiler flags: -C debuginfo=2 -C incremental --crate-type lib
note: some of the compiler flags provided by cargo are hidden
error: Could not compile network.
warning: build failed, waiting for other jobs to finish...
error: build failed
```
CLI Client Build
latest version cloned from GitHub
rustc 1.37.0-nightly (b25ee6449 2019-06-17)
MacOs Mojave 10.14.5
You obviously need to report this to https://github.com/rust-lang/rust/
@Kixunil sorry, how is this "obvious"?
The message itself says it:
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
The link points to that repository, not this one.
@Kixunil are you still experiencing this problem? Also did you follow up on @rollsmorr comment and report it on the Rust github?
I haven't been able to repro this. If the problem still persists please reopen the issue.