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

conflict on updating to today's nightly with llvm-tools #4019

Closed
2 tasks done
kaspar030 opened this issue Sep 13, 2024 · 9 comments
Closed
2 tasks done

conflict on updating to today's nightly with llvm-tools #4019

kaspar030 opened this issue Sep 13, 2024 · 9 comments
Labels

Comments

@kaspar030
Copy link

Verification

Problem

Can't update toolchain, fails with error: failed to install component: 'rustc-x86_64-unknown-linux-gnu', detected conflict: 'lib/rustlib/x86_64-unknown-linux-gnu/bin/llc'.

Steps

  1. have llvm-tools installed for nightly
  2. run rustup update

Possible Solution(s)

No response

Notes

No response

Rustup version

rustup --version
rustup 1.27.1 (54dd3d00f 2024-04-24)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.81.0 (eeb90cda1 2024-09-04)`

Installed toolchains

<details>


Default host: x86_64-unknown-linux-gnu
rustup home:  /home/kaspar/.rustup

installed toolchains
--------------------

stable-x86_64-unknown-linux-gnu (default)
nightly-2022-07-04-x86_64-unknown-linux-gnu
nightly-2022-10-22-x86_64-unknown-linux-gnu
nightly-2022-11-01-x86_64-unknown-linux-gnu
nightly-2022-11-22-x86_64-unknown-linux-gnu
nightly-2023-03-25-x86_64-unknown-linux-gnu
nightly-2023-05-18-x86_64-unknown-linux-gnu
nightly-2023-06-02-x86_64-unknown-linux-gnu
nightly-2023-06-28-x86_64-unknown-linux-gnu
nightly-2023-08-19-x86_64-unknown-linux-gnu
nightly-2023-10-02-x86_64-unknown-linux-gnu
nightly-2023-11-01-x86_64-unknown-linux-gnu
nightly-2024-03-11-x86_64-unknown-linux-gnu
nightly-2024-05-20-x86_64-unknown-linux-gnu
nightly-2024-05-31-x86_64-unknown-linux-gnu
nightly-2024-09-09-x86_64-unknown-linux-gnu
nightly-x86_64-unknown-linux-gnu
1.65.0-x86_64-unknown-linux-gnu
1.72.1-x86_64-unknown-linux-gnu
1.77.0-x86_64-unknown-linux-gnu
1.75-x86_64-unknown-linux-gnu
1.77-x86_64-unknown-linux-gnu
1.78-x86_64-unknown-linux-gnu
1.79-x86_64-unknown-linux-gnu
1.80-x86_64-unknown-linux-gnu
esp

installed targets for active toolchain
--------------------------------------

aarch64-linux-android
arm-unknown-linux-gnueabihf
arm-unknown-linux-musleabihf
armv7-linux-androideabi
armv7-unknown-linux-musleabihf
i686-linux-android
i686-unknown-linux-gnu
riscv32imac-unknown-none-elf
thumbv6m-none-eabi
thumbv7em-none-eabi
thumbv7em-none-eabihf
thumbv7m-none-eabi
wasm32-unknown-unknown
x86_64-apple-darwin
x86_64-linux-android
x86_64-pc-windows-gnu
x86_64-unknown-linux-gnu
x86_64-unknown-linux-musl

active toolchain
----------------

stable-x86_64-unknown-linux-gnu (default)
rustc 1.81.0 (eeb90cda1 2024-09-04)
```

OS version

current arch, also happens on the github Ubuntu CI workers.
@kaspar030 kaspar030 added the bug label Sep 13, 2024
@djc
Copy link
Contributor

djc commented Sep 13, 2024

I think this would be due to #988?

@larseggert
Copy link

We're seeing the same issue: https://github.com/mozilla/neqo/actions/runs/10844489766/job/30095214032#step:3:103

@kaspar030
Copy link
Author

I think this would be due to #988?

I don't think so, this started happening only recently on my CI. By pinning an older nightly version, this seems to be fixed.

larseggert added a commit to larseggert/neqo that referenced this issue Sep 13, 2024
@djc
Copy link
Contributor

djc commented Sep 13, 2024

Okay, can someone describe a reproduction scenario?

@kaspar030
Copy link
Author

kaspar030 commented Sep 13, 2024

Okay, can someone describe a reproduction scenario?

This "works" for me:

  • start a docker container with docker run -ti --rm ubuntu
  • inside docker container, run these commands:
$ apt-get update
$ apt-get install curl
$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
$ . "$HOME/.cargo/env"
$ rustup toolchain install nightly
$ rustup +nightly component add llvm-tools

@djc
Copy link
Contributor

djc commented Sep 13, 2024

Okay, great, thanks! I think this is an issue with the upstream toolchains. I opened a Zulip topic and am now looking at recent rust-lang/rust PRs to see if something there is relevant here.

@jclmnop
Copy link

jclmnop commented Sep 13, 2024

+1

Our github runners (Ubuntu 22.04.4) are now experiencing this exact same issue with the latest nightly. Yesterday's version was fine.

@djc
Copy link
Contributor

djc commented Sep 13, 2024

Okay, looks like this is getting fixed here:

rust-lang/rust bug is here:

@djc djc closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2024
@kaspar030
Copy link
Author

Thanks a bunch!

larseggert added a commit to mozilla/neqo that referenced this issue Sep 13, 2024
Zalathar added a commit to Zalathar/rust that referenced this issue Sep 14, 2024
…bzol

add llvm-bitcode-linker and llvm-tools bins to ci-rustc's sysroot

rust-lang#130040 is [reverted](rust-lang#130292) because adding component binaries directly to the dist tarball of the compiler caused conflicts (see rust-lang#130291 and rust-lang/rustup#4019). This PR solves the original problem without touching the dist tarball.

r? Kobzol
rust-timer added a commit to rust-lang-ci/rust that referenced this issue Sep 14, 2024
Rollup merge of rust-lang#130302 - onur-ozkan:130040-with-fixes, r=Kobzol

add llvm-bitcode-linker and llvm-tools bins to ci-rustc's sysroot

rust-lang#130040 is [reverted](rust-lang#130292) because adding component binaries directly to the dist tarball of the compiler caused conflicts (see rust-lang#130291 and rust-lang/rustup#4019). This PR solves the original problem without touching the dist tarball.

r? Kobzol
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants