Problem with building 1.85.0

From: Ted Lyngmo (ted_at_[hidden])
Date: 2024-05-13 21:00:46

Hi!

First, I'm not sure if this is the right place for this. 
https://svn.boost.org/trac/boost seems to be down so I'm not sure where 
to turn.

When I try building 1.85 on Fedora 40 with g++ (GCC) 14.1.1 20240507 
(Red Hat 14.1.1-1) I run into a problem.

I'm preparing the build like this:

git co master && \
git pull -r && \
git co boost-1.85.0 && \
git submodule update --recursive && \
./bootstrap.sh --with-libraries=all --with-icu \
   -with-python-version=3.12.3 --prefix=/home/ted/local && \
echo 'using mpi ;' >> project-config.jam

Then building like this:
./b2 -j8 install

It however ends like this:
...
...updated 18621 targets...

...skipped 30 targets...
 
<p/home/ted/local/lib/cmake/boost_fiber-1.85.0>libboost_fiber-variant-shared.cmake
 
<p/home/ted/local/lib/cmake/boost_filesystem-1.85.0>libboost_filesystem-variant-shared.cmake
 
<p/home/ted/local/lib/cmake/boost_filesystem-1.85.0>libboost_filesystem-variant-static.cmake
 
<p/home/ted/local/lib/cmake/boost_log-1.85.0>libboost_log-variant-shared.cmake
 
<p/home/ted/local/lib/cmake/boost_log_setup-1.85.0>libboost_log_setup-variant-shared.cmake
 
<p/home/ted/local/lib/cmake/boost_wave-1.85.0>libboost_wave-variant-shared.cmake
    <p/home/ted/local/lib>libboost_fiber.so
    <p/home/ted/local/lib>libboost_fiber.so.1.85.0
    <p/home/ted/local/lib>libboost_filesystem.a
    <p/home/ted/local/lib>libboost_filesystem.so
    <p/home/ted/local/lib>libboost_filesystem.so.1.85.0
    <p/home/ted/local/lib>libboost_log.so
    <p/home/ted/local/lib>libboost_log.so.1.85.0
    <p/home/ted/local/lib>libboost_log_setup.so
    <p/home/ted/local/lib>libboost_log_setup.so.1.85.0
    <p/home/ted/local/lib>libboost_wave.so
    <p/home/ted/local/lib>libboost_wave.so.1.85.0
 
<pbin.v2/libs/fiber/build/gcc-14/release/threading-multi/visibility-hidden>libboost_fiber-variant-shared.cmake
 
<pbin.v2/libs/fiber/build/gcc-14/release/threading-multi/visibility-hidden>libboost_fiber.so.1.85.0
 
<pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem-variant-static.cmake
 
<pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a
 
<pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a(clean)
 
<pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem-variant-shared.cmake
 
<pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem.so.1.85.0
 
<pbin.v2/libs/log/build/gcc-14/release/threading-multi/visibility-hidden>libboost_log-variant-shared.cmake
 
<pbin.v2/libs/log/build/gcc-14/release/threading-multi/visibility-hidden>libboost_log.so.1.85.0
 
<pbin.v2/libs/log/build/gcc-14/release/threading-multi/visibility-hidden>libboost_log_setup-variant-shared.cmake
 
<pbin.v2/libs/log/build/gcc-14/release/threading-multi/visibility-hidden>libboost_log_setup.so.1.85.0
 
<pbin.v2/libs/wave/build/gcc-14/release/threading-multi/visibility-hidden>libboost_wave-variant-shared.cmake
 
<pbin.v2/libs/wave/build/gcc-14/release/threading-multi/visibility-hidden>libboost_wave.so.1.85.0

...failed updating 6 targets...
    gcc.compile.c++ 
bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/directory.o
    gcc.compile.c++ 
bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/operations.o
    gcc.compile.c++ 
bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/unique_path.o
    gcc.compile.c++ 
bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/directory.o
    gcc.compile.c++ 
bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/operations.o
    gcc.compile.c++ 
bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/unique_path.o

Building boost-1.84.0, or earlier, the same way doesn't show any signs 
of problems. Is my bootstrapping done in the wrong way? I've used the 
same way for a long time, but I might just have been lucky that it has 
worked :)

Br,
Ted