Your message dated Thu, 10 Sep 2026 15:18:00 +0200
with message-id <E1x4efA-00000001S2o-14Hw@gelly>
and subject line Re: Bug#1132059 adios2: ftbfs with GCC-16
has caused the Debian Bug report #1132059,
regarding adios2: ftbfs with GCC-16
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1132059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1132059
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:adios2
Version: 2.11.0+dfsg1-6
Severity: important
Tags: sid forky ftbfs
User: [email protected]
Usertags: ftbfs-gcc-16

Hi,

adios2 fails to build in a test rebuild on at least amd64 and arm64 with
gcc-16/g++-16, but builds properly with gcc-15/g++-15. The severity of this
report will be raised before the forky release.

The full build log can be found at:
https://people.debian.org/~ema/gcc-16-rebuilds/output-1/adios2_arm64.build.xz

The last lines of the build log are at the end of this report.

To build with GCC 16, either set CC=gcc-16 CXX=g++-16 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures include unused (but set) variables, array subscripts
partly outside array bounds, and new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-16/porting_to.html

Please only close this issue after double-checking that the package can be
built correctly.

Please do not reassign this bug to another package. If a fix in another package
is required, then file a bug for the other package (or clone), and mark this
bug as blocked by the bug in the other package.

[...]


-- Detecting CXX compile features - done
-- Found MPI_C: /usr/bin/mpicc.openmpi (found version "3.1")
-- Found MPI_CXX: /usr/bin/mpic++.openmpi (found version "3.1")
-- Found MPI: TRUE (found version "3.1")
-- Found adios2: 
/build/reproducible-path/adios2-2.11.0+dfsg1/install-mpi/usr/lib/aarch64-linux-gnu/cmake/adios2/mpi/adios2-config.cmake
 (found version "2.11.0") found components: C CXX MPI
-- The Fortran compiler identification is unknown
--------------------------------------------------------------------------
The Open MPI wrapper compiler was unable to find the specified compiler
gfortran-15 in your PATH.

Note that this compiler was either specified at configure time or in
one of several possible environment variables.
--------------------------------------------------------------------------
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - failed
-- Check for working Fortran compiler: /usr/bin/mpifort.openmpi
-- Check for working Fortran compiler: /usr/bin/mpifort.openmpi - broken
CMake Error at /usr/share/cmake-4.3/Modules/CMakeTestFortranCompiler.cmake:59 
(message):
  The Fortran compiler

    "/usr/bin/mpifort.openmpi"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: '/tmp/tmp.5BzhWC32yk/CMakeFiles/CMakeScratch/TryCompile-nZVyQU'
    
    Run Build Command(s): /usr/bin/cmake -E env VERBOSE=1 /usr/bin/gmake -f 
Makefile cmTC_2888d/fast
    gmake[2]: Entering directory 
'/tmp/tmp.5BzhWC32yk/CMakeFiles/CMakeScratch/TryCompile-nZVyQU'
    /usr/bin/gmake  -f CMakeFiles/cmTC_2888d.dir/build.make 
CMakeFiles/cmTC_2888d.dir/build
    gmake[3]: Entering directory 
'/tmp/tmp.5BzhWC32yk/CMakeFiles/CMakeScratch/TryCompile-nZVyQU'
    Building Fortran object CMakeFiles/cmTC_2888d.dir/testFortranCompiler.f.o
    /usr/bin/mpifort.openmpi   -g -O2 
-ffile-prefix-map=/build/reproducible-path/adios2-2.11.0+dfsg1=. 
-fstack-protector-strong -fstack-clash-protection -mbranch-protection=standard 
-Wdate-time -D_FORTIFY_SOURCE=2  -c 
/tmp/tmp.5BzhWC32yk/CMakeFiles/CMakeScratch/TryCompile-nZVyQU/testFortranCompiler.f
 -o CMakeFiles/cmTC_2888d.dir/testFortranCompiler.f.o
    --------------------------------------------------------------------------
    The Open MPI wrapper compiler was unable to find the specified compiler
    gfortran-15 in your PATH.
    
    Note that this compiler was either specified at configure time or in
    one of several possible environment variables.
    --------------------------------------------------------------------------
    gmake[3]: *** [CMakeFiles/cmTC_2888d.dir/build.make:81: 
CMakeFiles/cmTC_2888d.dir/testFortranCompiler.f.o] Error 1
    gmake[3]: Leaving directory 
'/tmp/tmp.5BzhWC32yk/CMakeFiles/CMakeScratch/TryCompile-nZVyQU'
    gmake[2]: *** [Makefile:134: cmTC_2888d/fast] Error 2
    gmake[2]: Leaving directory 
'/tmp/tmp.5BzhWC32yk/CMakeFiles/CMakeScratch/TryCompile-nZVyQU'
    
    



  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:12 (enable_language)


-- Configuring incomplete, errors occurred!
Failed
CMake Error at cmake/install/post/cmake_install.cmake:49 (message):
  generate-adios2-config.sh returned 1, should be 0
Call Stack (most recent call first):
  cmake_install.cmake:81 (include)


FAILED: [code=1] CMakeFiles/install.util 
cd /build/reproducible-path/adios2-2.11.0+dfsg1/build-mpi && /usr/bin/cmake -P 
cmake_install.cmake
ninja: build stopped: subcommand failed.
dh_auto_install: error: cd build-mpi && 
DESTDIR=/build/reproducible-path/adios2-2.11.0\+dfsg1/install-mpi 
LC_ALL=C.UTF-8 ninja install returned exit code 1
make[1]: *** [debian/rules:133: install_mpi] Error 25
make[1]: Leaving directory '/build/reproducible-path/adios2-2.11.0+dfsg1'
make: *** [debian/rules:47: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2

--- End Message ---
--- Begin Message ---
Closing now, since the issue is fixed in openmpi 5.0.10-5

--- End Message ---
-- 
debian-science-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Reply via email to