Skip to content
Prev 11137 / 12125 Next

[R-pkg-devel] long user + system time with CRAN special checks clang 19

? Fri, 20 Dec 2024 11:30:04 +0300
Ivan Krylov via R-package-devel <r-package-devel at r-project.org> ?????:
That's because libtesseract.so is linked to a different C++ standard
library. Compare:
c++filt says it's:

tesseract::TessBaseAPI::GetVariableAsString(char const*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >*) const

The symbol actually exported by libtesseract.so is named differently:

$ nm -gDP /usr/lib/x86_64-linux-gnu/libtesseract.so.5 | grep GetVariableAsString
_ZNK9tesseract11TessBaseAPI19GetVariableAsStringEPKcPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE T a4f40 16

c++filt says:

tesseract::TessBaseAPI::GetVariableAsString(char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*) const

What should a package do when it's compiled by clang++ with the libc++
headers and library, but all system dependencies had been compiled with
g++ and linked with libstdc++? How to check packages using the clang
compiler without compiling the rest of the system from source using
clang? How do other C++ packages solve this problem?