Tom,

Sad news.  The build fails for me in unstable as is (using an updated
pbuilder chroot).  I log these to file and what I see is

cd /build/tiledb-2.6.2/obj-x86_64-linux-gnu/tiledb/tiledb && /usr/bin/cc 
-DFMT_LOCALE -DFMT_SHARED -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL 
-DSPDLOG_FMT_EXTERNAL=1 -DSPDLOG_SHARED_LIB -DTILEDB_CORE_OBJECTS_EXPORTS 
-DTILEDB_SERIALIZATION -DTILEDB_STATS -D_FILE_OFFSET_BITS=64 
-I/build/tiledb-2.6.2/tiledb/.. -I/build/tiledb-2.6.2/tiledb/../tiledb/sm/c_api 
-I/build/tiledb-2.6.2/tiledb/../external/include 
-I/build/tiledb-2.6.2/tiledb/../external/include/bitshuffle 
-I/build/tiledb-2.6.2/tiledb/../external/include/blosc 
-I/build/tiledb-2.6.2/external/blosc/include 
-I/build/tiledb-2.6.2/obj-x86_64-linux-gnu/tiledb/tiledb/.. 
-I/build/tiledb-2.6.2/tiledb/../tiledb/sm/cpp_api 
-I/build/tiledb-2.6.2/obj-x86_64-linux-gnu/tiledb/tiledb -g -O2 
-ffile-prefix-map=/build/tiledb-2.6.2=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -Wall -Wextra -mavx2 -w -DPTHREAD_AVAILABLE -MD -MT 
tiledb/CMakeFiles/TILEDB_CORE_OBJECTS.dir/__/external/blosc/src/shuffle-avx2.c.o
 -MF 
CMakeFiles/TILEDB_CORE_OBJECTS.dir/__/external/blosc/src/shuffle-avx2.c.o.d -o 
CMakeFiles/TILEDB_CORE_OBJECTS.dir/__/external/blosc/src/shuffle-avx2.c.o -c 
/build/tiledb-2.6.2/external/blosc/src/shuffle-avx2.c
[ 96%] Building CXX object 
tiledb/CMakeFiles/TILEDB_CORE_OBJECTS.dir/sm/serialization/posix/tiledb-rest.capnp.c++.o
cd /build/tiledb-2.6.2/obj-x86_64-linux-gnu/tiledb/tiledb && /usr/bin/c++ 
-DFMT_LOCALE -DFMT_SHARED -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL 
-DSPDLOG_FMT_EXTERNAL=1 -DSPDLOG_SHARED_LIB -DTILEDB_CORE_OBJECTS_EXPORTS 
-DTILEDB_SERIALIZATION -DTILEDB_STATS -D_FILE_OFFSET_BITS=64 
-I/build/tiledb-2.6.2/tiledb/.. -I/build/tiledb-2.6.2/tiledb/../tiledb/sm/c_api 
-I/build/tiledb-2.6.2/tiledb/../external/include 
-I/build/tiledb-2.6.2/tiledb/../external/include/bitshuffle 
-I/build/tiledb-2.6.2/tiledb/../external/include/blosc 
-I/build/tiledb-2.6.2/external/blosc/include 
-I/build/tiledb-2.6.2/obj-x86_64-linux-gnu/tiledb/tiledb/.. 
-I/build/tiledb-2.6.2/tiledb/../tiledb/sm/cpp_api 
-I/build/tiledb-2.6.2/obj-x86_64-linux-gnu/tiledb/tiledb -g -O2 
-ffile-prefix-map=/build/tiledb-2.6.2=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -Wall -Wextra -Wno-literal-suffix -mavx2 -std=c++17 -MD -MT 
tiledb/CMakeFiles/TILEDB_CORE_OBJECTS.dir/sm/serialization/posix/tiledb-rest.capnp.c++.o
 -MF 
CMakeFiles/TILEDB_CORE_OBJECTS.dir/sm/serialization/posix/tiledb-rest.capnp.c++.o.d
 -o 
CMakeFiles/TILEDB_CORE_OBJECTS.dir/sm/serialization/posix/tiledb-rest.capnp.c++.o
 -c /build/tiledb-2.6.2/tiledb/sm/serialization/posix/tiledb-rest.capnp.c++
make[7]: Leaving directory '/build/tiledb-2.6.2/obj-x86_64-linux-gnu/tiledb'
[ 96%] Built target TILEDB_CORE_OBJECTS
make[6]: Leaving directory '/build/tiledb-2.6.2/obj-x86_64-linux-gnu/tiledb'
make[5]: *** [Makefile:146: all] Error 2
make[5]: Leaving directory '/build/tiledb-2.6.2/obj-x86_64-linux-gnu/tiledb'
make[4]: *** [CMakeFiles/tiledb.dir/build.make:89: 
tiledb-prefix/src/tiledb-stamp/tiledb-build] Error 2
make[4]: Leaving directory '/build/tiledb-2.6.2/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:90: CMakeFiles/tiledb.dir/all] Error 2
make[3]: Leaving directory '/build/tiledb-2.6.2/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:94: all] Error 2
make[2]: Leaving directory '/build/tiledb-2.6.2/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j12 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:47: override_dh_auto_build] Error 25
make[1]: Leaving directory '/build/tiledb-2.6.2'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

which makes no sense to me as I see no error.

I would appreciate some help here.

Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Reply via email to