Source: esys-particle
Version: 2.3.5+dfsg2-12
Severity: important
Hi Maintainer
esys-particle will FTBFS when boost-defaults is upgraded. These
failures were found in Ubuntu, which is ahead of Debian with boost.
I've copied what I hope is the relevant parts of the logs below.
Regards
Graham
Failure with boost 1.88:
libtool: compile: mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include
-I/usr/include -Wdate-time -D_FORTIFY_SOURCE=3 -Wall -g -O2
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -flto=auto -ffat-lto-objects
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection
-fdebug-prefix-map=/<<PKGBUILDDIR>>=/usr/src/esys-particle-2.3.5+dfsg2-11
-std=c++14 -c StringUtil.cpp -o libFoundation_la-StringUtil.o
>/dev/null 2>&1
PathSearcher.cpp:18:10: fatal error: boost/filesystem/convenience.hpp:
No such file or directory
18 | #include <boost/filesystem/convenience.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Failure with boost 1.90:
configure:5269: checking whether the C compiler works
configure:5291: mpicc -Wall -g -O2
-Werror=implicit-function-declaration -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-flto=auto -ffat-lto-objects -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection
-fdebug-prefix-map=/<<PKGBUILDDIR>>=/usr/src/esys-particle-2.3.5+dfsg2-12build1
-Wdate-time -D_FORTIFY_SOURCE=3 -lboost_system
-Wl,-Bsymbolic-functions
-Wl,--package-metadata=%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22esys-particle%22%2C%22version%22:%222.3.5+dfsg2-12build1%22%2C%22architecture%22:%22amd64%22%7D
-flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now
-Wl,-rpath,/usr/lib/python3/dist-packages/esys/lsm/util:/usr/lib/python3/dist-packages/esys/lsm
conftest.c >&5
/usr/bin/x86_64-linux-gnu-ld.bfd: cannot find -lboost_system: No such
file or directory
collect2: error: ld returned 1 exit status
