Cannot compile, linking with cc failed: exit status: 1 (many undefined references) with 1.53.0
#87002
Comments
|
Transferred to rust-lang/rust as this is unlikely to be a cargo error (though it is possible). I am uncertain what could possibly cause that. You may be able to get more help on one of the user forums (like https://users.rust-lang.org/). Some information that would be helpful:
|
OS: Manjaro 21.0.7 Ornara
This happens every time (on certain projects)
No, I double checked with
I don't have a As for the nightly command:
I made a minimal setup to reproduce: Cargo.toml [package]
name = "actix-wont-compile"
version = "0.1.0"
edition = "2018"
[dependencies]
actix-multipart = "0.3" # I also tried "0.4.0-beta.5"
actix-web = "3" # I also tried "4.0.0-beta.8"
env_logger = "0.8"src/main.rs #[actix_web::main]
async fn main() -> std::io::Result<()> {
std::env::set_var("RUST_LOG", "info");
env_logger::init();
Ok(())
}Note that, I originally intended to report this to actix-web.
Yes I have deleted the target directory (before and after a clean re-install of rustup/cargo).
I used my package manager, that is
Using My nightly version is as follows: cargo +nightly -V
cargo 1.55.0-nightly (3ebb5f15a 2021-07-02) |
|
Still happening with |
|
We just encountered this in our CI. @lerouxrgd Any insights/updates on possible workarounds? |
|
Sadly the only workarounds are to downgrade to |
Thanks. Somehow for our CI system, updating our image helped (that means clean rust tools installed and everything built from scratch). |
|
This looks good now. |
Problem
After updating to
1.53.0I cannot compile most of my Rust projects, due to the error mentioned in the title.It looks like it doesn't happen on a different machine. So I tried to re-install latest rustup/cargo from scratch on my main machine but it still happens.
If I rollback to
rustup default 1.52.1then it works fine.In this case
cargo versiongivescargo 1.52.0 (69767412a 2021-04-21)Steps
1.53.0cargo buildouput
Notes
Output of
cargo version:cargo 1.53.0 (4369396ce 2021-04-27)The text was updated successfully, but these errors were encountered: