Now I should look into wether the curses CMake patch was necessary at all.
It wasn't necessary.
so far (from meta-pkgs/bulk-test-llvm):
- creduce: won't build, broken due to incompatibility
- firefox102/esr: something's broken, no idea what yet. Maybe wasm
related, incompatible to something I had to update maybe?
It's firefox, it's big, I'll look into this last.
- pocl: incompatible, broken
- py-llvmlite: incompatible, broken.
- zig: incompatible, broken, will add a note (next release at the end
of May will support 16)
- cvise: had to be updated I think.
- opencl-clang: updated it, will commit it with the llvm update
- build without issues:
- clang, include-what-you-use, polly, libcxx, libcxxabi, libunwind
- lld, lldb, openmp
The majority of the software did build already, I'm just waiting on
the rest, the optimistic scenario is that the firefox102 issue is easy
to fix and I can do the llvm update this weekend of at the start of
next week.
I wonder if maybe we should consider keeping older versions of llvm
around (multiversioning it is not a fun project), so that we can just
leave software which would be broken until next release or patches on
the llvm version which is compatible.
Yes please :)
Thomas