I think a build with an older boost worked:
--- a/debian/control
+++ b/debian/control
@@ -19,8 +19,8 @@ Build-Depends:
docbook-xsl,
elinks,
flex,
- libboost-dev,
- libboost-system-dev,
+ libboost1.74-dev,
+ libboost-system1.74-dev,
liblog4cplus-dev,
libpq-dev,
libssl-dev,
Locally I don't get a segfault anymore. I'm now waiting for a DEP8 run on ppc64el to confirm.
That being said, I don't know yet if that's a viable solution, i.e., I don't know what the lifecycle of lib boost versions is in the archive. Maybe this 1.74 is about to be removed, or is in universe, I haven't checked any of that yet.
The other tip I got recently was to try a build with less optimizations, specifically, -O2 instead of -O3. I remember other ppc64el-specific bugs caused by -O3 in the past. I'll try that next, with the current libboost version instead of the older 1.74 one.
I think a build with an older boost worked: system- dev, system1. 74-dev,
--- a/debian/control
+++ b/debian/control
@@ -19,8 +19,8 @@ Build-Depends:
docbook-xsl,
elinks,
flex,
- libboost-dev,
- libboost-
+ libboost1.74-dev,
+ libboost-
liblog4cplus-dev,
libpq-dev,
libssl-dev,
Locally I don't get a segfault anymore. I'm now waiting for a DEP8 run on ppc64el to confirm.
That being said, I don't know yet if that's a viable solution, i.e., I don't know what the lifecycle of lib boost versions is in the archive. Maybe this 1.74 is about to be removed, or is in universe, I haven't checked any of that yet.
The other tip I got recently was to try a build with less optimizations, specifically, -O2 instead of -O3. I remember other ppc64el-specific bugs caused by -O3 in the past. I'll try that next, with the current libboost version instead of the older 1.74 one.