I could fix the build on Tumbleweed by using clang-compatible LTO flags (-flto=thin). However, the build now requires llvm-gold (but only for Tumbleweed) and I don't know why that would be.

It seems like there is some sort of check script in the build that tests the compiler on some small nonsense program; this part then fails (only on Tumbleweed) with the message:

"The C compiler "/usr/bin/clang" is not able to compile a simple test program. It fails with the following output: [...]

/usr/bin/ld.gold: error: /usr/bin/../lib64/LLVMgold.so: could not load plugin library: /usr/bin/../lib64/LLVMgold.so: cannot open shared object file: No such file or directory "

so it requires llvm-gold. Why that part works on the older distributions and why one would need to test the compiler on a "simple program" as a part of building a package is anybody's guess. Surely, a bugged version of clang would be clang's problem and a misconfigured system would just fail building anyway?

Dmitriy Perlow (DarkSS) - over 4 years ago

Hello. Please submit a tw fix. Leap builds will became frozen so. Thanks.

Ferdinand Thiessen (susnux) - over 4 years ago

This happens because flto is ignored with older clang versions, but on tumbleweed the version recognizes the flto command and requires it to be valid.

So if you give a valid argument linktime optimization is used and this requires the llvm-gold plugin (see also: https://llvm.org/docs/GoldPlugin.html ). So just submit your changes (please note my other comment on your project).