The BOOST_STACKTRACE_HAS_BACKTRACE check doesn't seem to work with clang

[bgemmill]

When configuring cmake on ubuntu 24.04 with clang, the check for libbacktrace doesn't seem to work, even when libbacktrace is installed in the default location.

For reference, gcc puts libbacktrace here:
/usr/lib/gcc/x86_64-linux-gnu/13/include/backtrace.h

Configuring with clang, we see:

[build] -- Performing Test BOOST_STACKTRACE_HAS_BACKTRACE
[build] -- Performing Test BOOST_STACKTRACE_HAS_BACKTRACE - Failed

This can be corrected by explicitly telling the library where the header resides (the extra escapes are to pass the literal quotes all the way in to the header file as a define):

-DCMAKE_CXX_FLAGS="-DBOOST_STACKTRACE_BACKTRACE_INCLUDE_FILE=\\\"/usr/lib/gcc/x86_64-linux-gnu/13/include/backtrace.h\\\""

Can the cmake check of BOOST_STACKTRACE_HAS_BACKTRACE be modified to look at the gcc install location?

[pdimov]

Even if the check is modified to look somewhere not in the include path, the library would still not compile without passing -DBOOST_STACKTRACE_BACKTRACE_INCLUDE_FILE:

stacktrace/include/boost/stacktrace/detail/libbacktrace_impls.hpp

Lines 20 to 24 in 22982db

	#ifdef BOOST_STACKTRACE_BACKTRACE_INCLUDE_FILE
	# include BOOST_STACKTRACE_BACKTRACE_INCLUDE_FILE
	#else
	# include <backtrace.h>
	#endif

so what would be the point of modifying the check?

Does CMake's FindBacktrace module work on this configuration?

https://cmake.org/cmake/help/latest/module/FindBacktrace.html

Maybe the library needs to use that.

[bgemmill]

CMake's FindBacktrace does work, but detects this backtrace:

[cmake] -- Backtrace_HEADER execinfo.h
[cmake] -- Backtrace_INCLUDE_DIR /usr/include

Rather than the desired backtrace, and that looks like a different implementation.

@apolukhin does the backtrace in execinfo.h correspond to any of these?

[apolukhin]

@apolukhin does the backtrace in execinfo.h correspond to any of these?

Unfortunately no. It is an inconvenient interface that uses the desired functions under the hood