On 12 Jul 2026 15:41, Andrey Semashev wrote:
On 12 Jul 2026 14:26, Matthijs Möhlmann via Boost wrote:
On 12/07/2026 00:25, Sam Darwin via Boost wrote:
- The default Clang on Debian 13 (Trixie) is Clang 19. What happens with Clang 19?
- Is the operating system outside the container and inside, identical? (the same release of Debian 13?) What if you run the test on Ubuntu 22 and 24 containers? Of course it should work on Debian also, but this shows comparisons.
The result is the same with the default compiler (clang 19).
The operating system and the container is identical (both Debian 13 (Trixie).
Docker image: ubuntu:22.04 (Clang 14): same error. Docker image: ubuntu:24.04 (Clang 18): same error. Docker image: ubuntu:26.04 (Clang 21): same error.
When looking at the error message: error: Unable to find file or target named error: '/boost/boost_1_92_0/libs/config/checks//cxx11_variadic_templates' error: referred to from project at error: '/boost/boost_1_92_0/libs/charconv/build' error: could not resolve project reference '/boost/boost_1_92_0/libs/ config/checks'
It says: `config/checks//cxx11_variadic_templates`.
There is a double '//' there which indicates to me that some variable is replaced with an empty string?
The double // separates the path and the target name, this is expected. Could you check the contents of /boost/boost_1_92_0/libs/config/checks/Jamfile.v2? It should contain the following line:
obj cxx11_variadic_templates : test_case.cpp /boost/config//boost_config : <define>TEST_BOOST_NO_CXX11_VARIADIC_TEMPLATES ;
That's the target that is reportedly missing. If it's there (as expected) then that seems like a b2 issue.
One other thing to check is see if there is any permissions or disk storage issue. I know the build is supposed to be run under root within the container, but maybe there's some container-specific issue happening. Check that extracting the tar file succeeds and that the extracted tree is complete and readable (e.g. can you cat the Jamfile.v2 I mentioned in the build script?). Also, it would be nice to verify the checksum of the downloaded .tar.bz2 just in case.
One other note is that your b2 command line should probably include toolset=clang (with no dashes). I'm not sure if b2 honors CC and CXX environment variables, but in any case, toolset=xyz is the proper way of selecting the compiler. This is why you set up user-config.jam after all. Though I don't expect it to be related to the missing target issue.
One other thing to try is rename the build directory inside the container. E.g. instead of `mkdir /boost`, do `mkdir -p /build/boost` or something.