Tom Stellard (current LLVM release manager) just opened an RFC about handling the increasingly fragile standalone builds for LLVM subprojects. This affects us pretty directly, because we'd like to build subprojects (not least because llvmdev & clangdev already take ~4h each in CI), and we've been impacted by the deterioration of these builds (e.g. for LLVM 14, the llvmdev & compiler-rt feedstocks had to switch from subproject sources to full sources, and then still ran into troubles).
I already made a comment but wanted to let people know, in case anyone wants to chime in about this on the LLVM discourse (supports sign-in with github), or perhaps just follow that discussion.
CC @conda-forge/llvmdev @conda-forge/clangdev @conda-forge/openmp @conda-forge/libcxx @conda-forge/lld @conda-forge/mlir @conda-forge/compiler-rt @conda-forge/flang
Tom Stellard (current LLVM release manager) just opened an RFC about handling the increasingly fragile standalone builds for LLVM subprojects. This affects us pretty directly, because we'd like to build subprojects (not least because llvmdev & clangdev already take ~4h each in CI), and we've been impacted by the deterioration of these builds (e.g. for LLVM 14, the
llvmdev
&compiler-rt
feedstocks had to switch from subproject sources to full sources, and then still ran into troubles).I already made a comment but wanted to let people know, in case anyone wants to chime in about this on the LLVM discourse (supports sign-in with github), or perhaps just follow that discussion.
CC @conda-forge/llvmdev @conda-forge/clangdev @conda-forge/openmp @conda-forge/libcxx @conda-forge/lld @conda-forge/mlir @conda-forge/compiler-rt @conda-forge/flang