arm64 host: apt install clang doesn't install the nightly toolchain #64790
Assignees
Labels
Comments
arsenm
added
infrastructure
|
@llvm/issue-subscribers-infrastructure |
|
Same for Ubuntu Jammy on ARM64: https://apt.llvm.org/jammy/dists/llvm-toolchain-jammy/main/binary-arm64/Packages does not offer an unversioned |
|
I will have a look to this, sorry |
real-or-random
added a commit
to real-or-random/secp256k1
that referenced
this issue
Aug 30, 2023
This also switches to a new strategy to make sure we're installing the most recent LLVM packages. Before this commit, we used the unversioned LLVM packages (e.g., `clang` instead of `clang-18`), which are supposed to provide the latest snapshot, but this is broken for arm64 [1]. Anyway, the new approach is cleaner because it does not require us to fiddle with the installed `clang` package by removing a symlink. [1] llvm/llvm-project#64790
real-or-random
added a commit
to real-or-random/secp256k1
that referenced
this issue
Sep 2, 2023
This commit switches to a new strategy to make sure we're installing the most recent LLVM packages. Before this commit, we used the unversioned LLVM packages (e.g., `clang` instead of `clang-18`), which are supposed to provide the latest snapshot, but this is broken for arm64 [1], which we want to add in a later PR. Anyway, the new approach is cleaner because it does not require us to fiddle with the installed `clang` package by removing a symlink. [1] llvm/llvm-project#64790
real-or-random
added a commit
to real-or-random/secp256k1
that referenced
this issue
Sep 3, 2023
This commit switches to a new strategy to make sure we're installing the most recent LLVM packages. Before this commit, we used the unversioned LLVM packages (e.g., `clang` instead of `clang-18`), which are supposed to provide the latest snapshot, but this is broken for arm64 [1], which we want to add in a later PR. Anyway, the new approach is cleaner because it does not require us to fiddle with the installed `clang` package by removing a symlink. [1] llvm/llvm-project#64790 Co-authored-by: Hennadii Stepanov <32963518+hebasto@users.noreply.github.com>
|
Hitting the same issue today, was confused for a while as to why |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
on arm64:
root@3cf1ebcf6277:/# apt install -t llvm-toolchain-bullseye clang
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
clang is already the newest version (1:11.0-51+nmu5).
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
on x86:
root@149a19ca001b:/# apt install -t llvm-toolchain-bullseye clang
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
clang is already the newest version (1:18.0-58exp120230727113808.19).
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Can this be a issue with the meta package?
I'm able to install the nighly toolchain if I specify clang-18 explicitly.
The text was updated successfully, but these errors were encountered: