Open danpetry opened 10 months ago
ping, any possibility of attention here :) ?
Hi, Unfortunately, we can't do anything on our side. It looks like the bug is coming from their version of Clang called Apple Clang (I'm assuming since you are running an old version). Feel free to check if it's the case.
We're using conda clang 14 from Anaconda main channel. This is seen while building llvm 17 for conda packaging for the same channel. So I guess the same applies - it's probably due to an older version of clang being used to compile? When building a new version of the llvm-project tools, what previous version range of clang is recommended/supported?
I did not know conda clang was a thing. For recommended/supported versions, the latest major stable version is your best bet. Try to do the same thing with the latest version that you can use, and check if the problem has been solved.
It's also weird to use Clang 14 with LLVM 17. It should be the same major version, at least.
sure. But when building new llvm/clang, clang is required. to break the circular dependency, an older version is needed, or is there something I'm missing?
the current version of clang in the conda distro is 14, so that's what I'm using. Once llvm and clang 17 is built and packaged, it'll be possible to go back and recompile both with clang 17. I'm just wondering if you have any recommendations for distro maintainers building newer versions of clang. We could use that version of clang from another distro, but what if you're the first one building it? Just wondering if there's any recommendations on an approach here. To clarify, I'm compiling llvm 17 with clang 14, rather than mixing versions in the same toolchain.
You do not need specifically Clang to build any component of the project, you need to have a compiler that support the C++17 standard at least, some other subprojects needs a newer version. We have a documentation page about how to distribute llvm and other subprojects Building a distribution. It looks like an incompatibility with a system library, but I am not quite if it's caused by the library of Big Sur or the conda version is weird. Clang 14 is not too old yet to compile LLVM currently. Maybe you need to try with Apple Clang (even if it's lagging behind a couple of major releases).
ok, thanks for the info. I'll have a look at that page
Hi, have you resolved the issue?
Hi Tony, thanks for the heads-up, i haven't managed to look at this in depth yet but I'll update the ticket when I do.
I'm seeing crashes in the following unit tests, with the following stack traces, on macOS Big Sur, but not Ventura. MacOSX11.1 SDK and clang 14.0.6 was used to compile:
Is this a platform or toolchain issue, or a bug? Please let me know if you need any further info.