FTBFS while packaging for openSUSE/Factory

[mcepl]

When trying to package espresso 4.2.2 (from the tarball on GitHub) with multiple versions of Python (from 3.11 to 3.13) and cmake 3.31.5, I get this error:

[   12s] CMake Error at /usr/lib64/cmake/boost_mpi-1.87.0/libboost_mpi-variant-shared.cmake:70 (message):
[   12s]   Target Boost::mpi already has an imported location
[   12s]   '/usr/lib64/libboost_mpi.so.1.87.0', which is being overwritten with
[   12s]   '/usr/lib64/libboost_mpi.so.1.87.0'
[   12s] Call Stack (most recent call first):
[   12s]   /usr/lib64/cmake/boost_mpi-1.87.0/boost_mpi-config.cmake:43 (include)
[   12s]   /usr/lib64/cmake/Boost-1.87.0/BoostConfig.cmake:141 (find_package)
[   12s]   /usr/lib64/cmake/Boost-1.87.0/BoostConfig.cmake:262 (boost_find_component)
[   12s]   CMakeLists.txt:358 (find_package)

My cmake command is 3.31.5 and it is executed with these options:

/usr/bin/cmake \
/home/abuild/rpmbuild/BUILD/python-espressomd-4.2.2-build/espresso/. \
'-GUnix Makefiles' -DCMAKE_INSTALL_PREFIX:PATH=/usr \
-DCMAKE_INSTALL_BINDIR:PATH=bin -DCMAKE_INSTALL_SBINDIR:PATH=sbin \
-DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec \
-DCMAKE_INSTALL_SYSCONFDIR:PATH=etc \
-DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=/var/lib \
-DCMAKE_INSTALL_LOCALSTATEDIR:PATH=var \
-DCMAKE_INSTALL_RUNSTATEDIR:PATH=run -DCMAKE_INSTALL_LIBDIR:PATH=lib64 \
-DCMAKE_INSTALL_INCLUDEDIR:PATH=include \
-DCMAKE_INSTALL_DATAROOTDIR:PATH=share \
-DCMAKE_INSTALL_DOCDIR:PATH=share/doc/packages/python-espressomd \
-DCMAKE_INSTALL_MANDIR:PATH=share/man \
-DCMAKE_INSTALL_INFODIR:PATH=share/info \
-DINCLUDE_INSTALL_DIR:PATH=/usr/include \
-DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc \
-DSHARE_INSTALL_PREFIX:PATH=/usr/share -DCMAKE_BUILD_TYPE=RelWithDebInfo \
'-DCMAKE_C_FLAGS=-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 \
-fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables \
-fstack-clash-protection -Werror=return-type -g' '-DCMAKE_CXX_FLAGS=-O2 \
-Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong \
-funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection \
-Werror=return-type -g' '-DCMAKE_Fortran_FLAGS=-O2 -Wall \
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong \
-funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection \
-Werror=return-type -g' '-DCMAKE_EXE_LINKER_FLAGS= -Wl,--as-needed \
-Wl,--no-undefined -Wl,-z,now' '-DCMAKE_MODULE_LINKER_FLAGS= \
-Wl,--as-needed' '-DCMAKE_SHARED_LINKER_FLAGS= -Wl,--as-needed \
-Wl,--no-undefined -Wl,-z,now' -DLIB_SUFFIX=64 \
-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DBUILD_SHARED_LIBS:BOOL=ON \
-DBUILD_STATIC_LIBS:BOOL=OFF -DCMAKE_COLOR_MAKEFILE:BOOL=OFF \
-DCMAKE_INSTALL_DO_STRIP:BOOL=OFF \
-DCMAKE_MODULES_INSTALL_DIR=/usr/lib64/cmake/python-espressomd -Wno-dev \
'-DCMAKE_SHARED_LINKER_FLAGS=-Wl,--as-needed -Wl,-z,now' \
-DCMAKE_SKIP_RPATH=ON -DLIBDIR=/usr/lib64 \
-DPYTHON_EXECUTABLE=/usr/bin/python3.12 \
-DPYTHON_INCLUDE_DIRS=/usr/include/python3.12

Any idea what should I do? What do I do wrong?

Complete build log with all details of packages used and steps taken to reproduce.

[jngrad]

Thank you for bringing our attention to this issue.

After some tinkering in an openSUSE docker image, my impression is that something's wrong in either Boost or openSUSE. Here is a minimal working example to reproduce the issue without ESPResSo:

cmake_minimum_required(VERSION 3.25.1)
cmake_policy(VERSION 3.25.1)
project(ProjectName)

if(POLICY CMP0167)
  # use BoostConfig.cmake shipped with Boost 1.70+ instead of the one in CMake
  cmake_policy(SET CMP0167 NEW)
endif()

find_package(Boost 1.81.0 REQUIRED mpi serialization filesystem system)

Running this MWE in Tumbleweed version 20250301:

mkdir build
cd build
cmake ..

Output:

-- The C compiler identification is GNU 14.2.1
-- The CXX compiler identification is GNU 14.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at /usr/lib64/cmake/boost_mpi-1.87.0/libboost_mpi-variant-shared.cmake:70 (message):
  Target Boost::mpi already has an imported location
  '/usr/lib64/libboost_mpi.so.1.87.0', which is being overwritten with
  '/usr/lib64/libboost_mpi.so.1.87.0'
Call Stack (most recent call first):
  /usr/lib64/cmake/boost_mpi-1.87.0/boost_mpi-config.cmake:43 (include)
  /usr/lib64/cmake/Boost-1.87.0/BoostConfig.cmake:141 (find_package)
  /usr/lib64/cmake/Boost-1.87.0/BoostConfig.cmake:262 (boost_find_component)
  venv/lib/python3.11/site-packages/cmake/data/share/cmake-3.25/Modules/FindBoost.cmake:594 (find_package)
  CMakeLists.txt:10 (find_package)


-- Found Boost: /usr/lib64/cmake/Boost-1.87.0/BoostConfig.cmake (found suitable version "1.87.0", minimum required is "1.81.0") found components: mpi serialization filesystem system 
-- Configuring incomplete, errors occurred!

Reproducible with CMake versions 3.31.5 (from OP), 3.31.6, 3.30.0, 3.29.0, 3.25.2.

[jngrad]

Note: the fatal error isn't triggered when removing mpi from the list of components for FindBoost. This can help narrow down the source of the issue. In addition, the overwriting path is equal to the overwritten path, so one could probably patch boost_mpi-1.87.0/libboost_mpi-variant-shared.cmake to skip this fatal error when both paths are identical. However, I'm not very familiar with this file and it could be that this fatal error is meant to also detect e.g. double calls to a CMake function (which would have additional side effects beyond overwriting this one path). I'm also unsure if this CMake file originates from Boost or from the packaging team.

[simotek]

It looks like we have both libboost_mpi-variant-shared.cmake and libboost_mpi-variant-shared-py3.11.cmake removing the later from the buildroot fixes the issue. So at a guess maybe we want one file or the other file in a system not both at the same time.

[jngrad]

Bug report: Bugzilla 1239592