-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
LLVM 16.0.0.rc4 #95
LLVM 16.0.0.rc4 #95
Conversation
…da-forge-pinning 2020.10.14.22.34.53
…da-forge-pinning 2020.10.14.22.34.53
…da-forge-pinning 2020.10.15.16.54.09
…da-forge-pinning 2020.10.15.16.54.09
automerged PR by conda-forge/automerge-action
unset CONDA_BUILD_SYSROOT during test phase if it doesn't exist
automerged PR by conda-forge/automerge-action
automerged PR by conda-forge/automerge-action
…da-forge-pinning 2020.11.16.18.10.02
remove comma, fix conda-forge#43
This is needed because r-base brings in the compiler for build platform when cross-compiling which is undesirable
Don't activate if the target_platform is unexpected
Fix condition
automerged PR by conda-forge/automerge-action
…da-forge-pinning 2021.01.15.13.32.18
LLVM 15.0.7
…onda-forge#96) automerged PR by conda-forge/automerge-action
…nda-forge-pinning 2023.03.15.21.36.18
…nda-forge-pinning 2023.03.15.21.36.18
Actually build LLVM 15
…nda-forge-pinning 2023.03.16.06.20.58
@conda-forge/core
|
I think the branch name needs to be |
Thanks, but that's not it. It's as Billy mentioned on matrix, we need to remove |
I might just succeed for once to build the whole compiler stack during the rc phase 🙃
Blockers for merging this PR and thus enabling the compilers in conda-forge (indentation denotes dependency; c.f. list from 15.x):
The PRs marked ** are not strictly speaking necessary for merging this PR, but for LLVM 16.x support in conda-forge.