[Debichem-devel] Bug#1008380: macromoleculebuilder: FTBFS: DensityMap.cpp:476:64: error: ‘gemmi::GridSetup’ has not been declared

[Lucas Nussbaum]

Source: macromoleculebuilder
Version: 3.5+dfsg-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /usr/bin/c++ -DBuildNtC -DLEPTON_BUILDING_STATIC_LIBRARY -DLepton_USAGE -DMMBlib_EXPORTS -DUSE_MMB_CONSTEXPR -DUSE_OPENMM -isystem /<<PKGBUILDDIR>>/include -isystem /usr/include/simbody -isystem /usr/include/openmm -isystem /usr/include/openmm/reference -isystem /include -isystem /<<PKGBUILDDIR>>/3rdparty/Lepton1.3/include -D BuildNtC -D USE_OPENMM -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -O0 -fvisibility=hidden -O3 -DNDEBUG -fPIC -DMMB_BUILDING_SHARED_LIBRARY -std=c++14 -MD -MT CMakeFiles/MMBlib.dir/src/CifOutput.cpp.o -MF CMakeFiles/MMBlib.dir/src/CifOutput.cpp.o.d -o CMakeFiles/MMBlib.dir/src/CifOutput.cpp.o -c /<<PKGBUILDDIR>>/src/CifOutput.cpp
> In file included from /usr/include/gemmi/to_mmcif.hpp:80,
>                  from /<<PKGBUILDDIR>>/src/CifOutput.cpp:10:
> /usr/include/gemmi/sprintf.hpp:26:4: warning: #warning "Using system stb_sprintf.h, not the bundled one. It may not work." [-Wcpp]
>    26 | #  warning "Using system stb_sprintf.h, not the bundled one. It may not work."
>       |    ^~~~~~~
> /<<PKGBUILDDIR>>/src/DensityMap.cpp: In member function ‘void DensityMap::loadParametersAndDensity_CCP4MAP()’:
> /<<PKGBUILDDIR>>/src/DensityMap.cpp:476:64: error: ‘gemmi::GridSetup’ has not been declared
>   476 |     map.setup                                         ( gemmi::GridSetup::ReorderOnly, NAN );
>       |                                                                ^~~~~~~~~
> [ 68%] Building CXX object CMakeFiles/MMBlib.dir/src/ProgressWriter.cpp.o
> /usr/bin/c++ -DBuildNtC -DLEPTON_BUILDING_STATIC_LIBRARY -DLepton_USAGE -DMMBlib_EXPORTS -DUSE_MMB_CONSTEXPR -DUSE_OPENMM -isystem /<<PKGBUILDDIR>>/include -isystem /usr/include/simbody -isystem /usr/include/openmm -isystem /usr/include/openmm/reference -isystem /include -isystem /<<PKGBUILDDIR>>/3rdparty/Lepton1.3/include -D BuildNtC -D USE_OPENMM -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -O0 -fvisibility=hidden -O3 -DNDEBUG -fPIC -DMMB_BUILDING_SHARED_LIBRARY -std=c++14 -MD -MT CMakeFiles/MMBlib.dir/src/ProgressWriter.cpp.o -MF CMakeFiles/MMBlib.dir/src/ProgressWriter.cpp.o.d -o CMakeFiles/MMBlib.dir/src/ProgressWriter.cpp.o -c /<<PKGBUILDDIR>>/src/ProgressWriter.cpp
> [ 71%] Building CXX object CMakeFiles/MMBlib.dir/src/NTC_PARAMETER_READER.cpp.o
> /usr/bin/c++ -DBuildNtC -DLEPTON_BUILDING_STATIC_LIBRARY -DLepton_USAGE -DMMBlib_EXPORTS -DUSE_MMB_CONSTEXPR -DUSE_OPENMM -isystem /<<PKGBUILDDIR>>/include -isystem /usr/include/simbody -isystem /usr/include/openmm -isystem /usr/include/openmm/reference -isystem /include -isystem /<<PKGBUILDDIR>>/3rdparty/Lepton1.3/include -D BuildNtC -D USE_OPENMM -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -O0 -fvisibility=hidden -O3 -DNDEBUG -fPIC -DMMB_BUILDING_SHARED_LIBRARY -std=c++14 -MD -MT CMakeFiles/MMBlib.dir/src/NTC_PARAMETER_READER.cpp.o -MF CMakeFiles/MMBlib.dir/src/NTC_PARAMETER_READER.cpp.o.d -o CMakeFiles/MMBlib.dir/src/NTC_PARAMETER_READER.cpp.o -c /<<PKGBUILDDIR>>/src/NTC_PARAMETER_READER.cpp
> make[3]: *** [CMakeFiles/MMBlib.dir/build.make:345: CMakeFiles/MMBlib.dir/src/DensityMap.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/macromoleculebuilder_3.5+dfsg-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.