• Bug#1103363: openvdb: FTBFS in testing/arm64: make[3]: *** [openvdb_cmd

    From Jochen Sprickerhof@21:1/5 to All on Wed May 14 10:30:01 2025
    Control: severity -1 normal
    Control: tags -1 moreinfo

    Hi Lucas,

    * Lucas Nussbaum <lucas@debian.org> [2025-04-16 20:44]:
    Source: openvdb
    Version: 10.0.1-2.3
    Severity: serious
    Justification: FTBFS
    Tags: trixie sid ftbfs
    User: lucas@debian.org
    Usertags: ftbfs-20250416 ftbfs-trixie

    Hi,

    During a rebuild of all packages in testing (trixie), your package failed
    to build on arm64.


    Relevant part (hopefully):
    make[3]: Entering directory '/build/reproducible-path/openvdb-10.0.1/obj-aarch64-linux-gnu'
    [ 42%] Building CXX object openvdb_cmd/vdb_tool/CMakeFiles/vdb_tool_test.dir/src/unittest.cpp.o
    cd /build/reproducible-path/openvdb-10.0.1/obj-aarch64-linux-gnu/openvdb_cmd/vdb_tool && /usr/bin/c++ -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_IOSTREAMS_NO_LIB -DNANOVDB_USE_BLOSC -DNANOVDB_USE_INTRINSICS -DNANOVDB_USE_OPENVDB -DNANOVDB_USE_TBB -DNANOVDB_
    USE_ZIP -DOPENVDB_DLL -DOPENVDB_USE_DELAYED_LOADING -DOPENVDB_USE_LOG4CPLUS -DVDB_TOOL_USE_EXR -DVDB_TOOL_USE_JPG -DVDB_TOOL_USE_NANO -DVDB_TOOL_USE_PNG -I/build/reproducible-path/openvdb-10.0.1/openvdb_cmd/vdb_tool/vdb_tool_common -I/build/reproducible-
    path/openvdb-10.0.1/openvdb_cmd/vdb_tool -I/build/reproducible-path/openvdb-10.0.1/openvdb_cmd/vdb_tool/include -I/build/reproducible-path/openvdb-10.0.1/nanovdb/nanovdb/.. -I/build/reproducible-path/openvdb-10.0.1/openvdb/openvdb/.. -I/build/
    reproducible-path/openvdb-10.0.1/obj-aarch64-linux-gnu/openvdb/openvdb -I/build/reproducible-path/openvdb-10.0.1/obj-aarch64-linux-gnu/openvdb/openvdb/openvdb -isystem /usr/include/Imath -isystem /usr/include/OpenEXR -g -O2 -ffile-prefix-map=/build/
    reproducible-path/openvdb-10.0.1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wno-psabi -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -Wno-invalid-offsetof -pthread -lpthread -DGTEST_HAS_
    PTHREAD=1 -MD -MT openvdb_cmd/vdb_tool/CMakeFiles/vdb_tool_test.dir/src/unittest.cpp.o -MF CMakeFiles/vdb_tool_test.dir/src/unittest.cpp.o.d -o CMakeFiles/vdb_tool_test.dir/src/unittest.cpp.o -c /build/reproducible-path/openvdb-10.0.1/openvdb_cmd/vdb_
    tool/src/unittest.cpp
    c++: fatal error: Killed signal terminated program cc1plus
    compilation terminated.
    make[3]: *** [openvdb_cmd/vdb_tool/CMakeFiles/vdb_tool.dir/build.make:82: openvdb_cmd/vdb_tool/CMakeFiles/vdb_tool.dir/src/main.cpp.o] Error 1


    The full build log is available from: >http://qa-logs.debian.net/2025/04/16/openvdb_10.0.1-2.3_testing-arm64.log

    All bugs filed during this archive rebuild are listed at: >https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250416;users=lucas@debian.org
    or: >https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250416&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

    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 mark 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.

    * Gregor Riepl <onitake@gmail.com> [2025-04-27 00:45]:
    c++: fatal error: Killed signal terminated program cc1plus

    The full build log is available from: >>http://qa-logs.debian.net/2025/04/16/openvdb_10.0.1-2.3_testing-arm64.log >This doesn't looks like an FTBFS to me - more like the build machine ran out of memory.

    openvdb requires a serious amount of RAM to compile, even when the number of parallel processes is limited (as is done in debian/rules).

    Could you try rerunning the QA build on a machine with more guaranteed memory available?

    I agree with this and changed the bug data.
    Lucas: can you do the test?

    Cheers Jochen

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmgkUzYACgkQW//cwljm lDPCWA//bqFpp7uP3drAKh/Ru2dQWA5WWi6rKO0IWWTKxMPj2KQtCWCPwovMsTtZ tdo1awiJycIH80TBKB/wQTwAEpwxTVnIJ5Gx07ZMGwgcZNOU1BgOz8ZoWgonqzjc 1bXD+pfSmmnWRBHEffR4dSXUItLGazqTxd3WEdfneS9AF1795TBavj4ax5RX/xaT DxEBi44KkWYCfvk3WjyWqLIvZXEH19ssJnup3OOgGF8X1RTgGyWEVfecptx8hKx3 GT/hQQsdPpFC7bjTXbvj/6RkcN1iU5W6EwuuMUmf4LsdzFcYV3QFokackZOytJmz eLao93OSS8y6jU8f/vVw92dG1ca86T5EB6msqgxzOPwIzmtmncTP+/JSRNC7Iame fXf/LpRpKPwFl61V+v2lnQJ+s/+z5LdXIsN/8ytkHG+sV30SxiD3UqSMy9zZoA7+ MDEYQHPaw+xRsSoIhIKXwjeooXBC8+faPSFTVfXpyqMeRWyeniMJbBks9DkOt9gv WFvZd7gWxL1QEtY2o8u45mNTeE8JCpxK1SpeipSbQyc0LwjrJ9c3D19Tcsdhz363 /sCwkcvk/DbHEIq18L1PvvJ3mwjRVwoCbHROEQXBkmVgonPmr15gsHnINbrvvPO0 aeLntQH07qP0AWKzVSk9KQGIpkdh00PkWA0MoHQmn6ZJguH/+tE=
    =jQyw
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)