dolfin FTBFS on mips64el: ld error adding symbols: bad value
Can anyone help with the mips64el build of dolfin? It's failing when
building python extensions:
[ 95%] Building CXX object CMakeFiles/cpp.dir/src/MPICommWrapper.cpp.o
/usr/bin/c++ -DDOLFIN_VERSION=\"2019.2.0.dev0\" -DHAS_CHOLMOD
-DHAS_HDF5 -DHAS_MPI -DHAS_PETSC -DHAS_PYBIND11_MPI4PY
-DHAS_PYBIND11_PETSC4PY -DHAS_SCOTCH -DHAS_SLEPC -DHAS_UMFPACK
-DHAS_ZLIB -DNDEBUG -Dcpp_EXPORTS
-I/usr/lib/petscdir/petsc64-3.13/mips64el-linux-gnuabi64-real/lib/python3/dist-packages/petsc4py/include
-I/usr/lib/python3/dist-packages/mpi4py/include -isystem
/usr/include/python3.8 -isystem
/usr/lib/python3/dist-packages/ffc/backends/ufc -isystem
/usr/include/eigen3 -isystem /usr/include/hdf5/openmpi -isystem
/usr/lib/mips64el-linux-gnuabi64/openmpi/include/openmpi -isystem
/usr/lib/mips64el-linux-gnuabi64/openmpi/include -isystem
/usr/lib/petscdir/petsc64-3.13/mips64el-linux-gnuabi64-real/include
-isystem
/usr/lib/slepcdir/slepc64-3.13/mips64el-linux-gnuabi64-real/include -g
-O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-Wformat -Werror=format-security -isystem
/<<PKGBUILDDIR>>/debian/tmp64/usr/include
-DVERSION_INFO=\"2019.2.0.dev0\" -O3 -DNDEBUG -fPIC -fvisibility=hidden
-std=c++14 -flto -fno-fat-lto-objects -fvisibility=hidden -std=c++11 -o
CMakeFiles/cpp.dir/src/MPICommWrapper.cpp.o -c
"/<<PKGBUILDDIR>>/python/src/MPICommWrapper.cpp"
[100%] Linking CXX shared library
../lib.linux-mips64-3.8/dolfin/cpp.cpython-38-mips64el-linux-gnuabi64.so
/usr/bin/cmake -E cmake_link_script CMakeFiles/cpp.dir/link.txt
--verbose=1
/usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -isystem
/<<PKGBUILDDIR>>/debian/tmp64/usr/include
-DVERSION_INFO=\"2019.2.0.dev0\" -O3 -DNDEBUG -Wl,-z,relro -shared
-Wl,-soname,cpp.cpython-38-mips64el-linux-gnuabi64.so -o
../lib.linux-mips64-3.8/dolfin/cpp.cpython-38-mips64el-linux-gnuabi64.so
CMakeFiles/cpp.dir/src/dolfin.cpp.o
CMakeFiles/cpp.dir/src/parameter.cpp.o
CMakeFiles/cpp.dir/src/adaptivity.cpp.o CMakeFiles/cpp.dir/src/ale.cpp.o
CMakeFiles/cpp.dir/src/common.cpp.o CMakeFiles/cpp.dir/src/fem.cpp.o
CMakeFiles/cpp.dir/src/function.cpp.o
CMakeFiles/cpp.dir/src/generation.cpp.o
CMakeFiles/cpp.dir/src/geometry.cpp.o CMakeFiles/cpp.dir/src/graph.cpp.o
CMakeFiles/cpp.dir/src/log.cpp.o CMakeFiles/cpp.dir/src/math.cpp.o
CMakeFiles/cpp.dir/src/mesh.cpp.o
CMakeFiles/cpp.dir/src/multistage.cpp.o CMakeFiles/cpp.dir/src/ts.cpp.o
CMakeFiles/cpp.dir/src/io.cpp.o CMakeFiles/cpp.dir/src/la.cpp.o
CMakeFiles/cpp.dir/src/nls.cpp.o CMakeFiles/cpp.dir/src/refinement.cpp.o
CMakeFiles/cpp.dir/src/MPICommWrapper.cpp.o
-Wl,-rpath,"/<<PKGBUILDDIR>>/debian/tmp64/usr/lib/mips64el-linux-gnuabi64:/usr/lib/mips64el-linux-gnuabi64/hdf5/openmpi:/usr/lib/slepcdir/slepc64-3.13/mips64el-linux-gnuabi64-real/lib:/usr/lib/petscdir/petsc64-3.13/mips64el-linux-gnuabi64-real/lib:/usr/lib/mips64el-linux-gnuabi64/openmpi/lib"
-flto
"/<<PKGBUILDDIR>>/debian/tmp64/usr/lib/mips64el-linux-gnuabi64/libdolfin64.so.2019.2.0.dev0"
/usr/lib/mips64el-linux-gnuabi64/libboost_timer.so
/usr/lib/mips64el-linux-gnuabi64/libboost_chrono.so
/usr/lib/mips64el-linux-gnuabi64/hdf5/openmpi/libhdf5.so -lsz -lz -ldl
-lm
/usr/lib/slepcdir/slepc64-3.13/mips64el-linux-gnuabi64-real/lib/libslepc64_real.so
/usr/lib/petscdir/petsc64-3.13/mips64el-linux-gnuabi64-real/lib/libpetsc64_real.so
/usr/lib/mips64el-linux-gnuabi64/openmpi/lib/libmpi_cxx.so
/usr/lib/mips64el-linux-gnuabi64/openmpi/lib/libmpi.so
/usr/bin/ld:
/tmp/cpp.cpython-38-mips64el-linux-gnuabi64.so.AnBotY.ltrans29.ltrans.o:
.symtab local symbol at index 482 (>= sh_info of 99)
/usr/bin/ld:
/tmp/cpp.cpython-38-mips64el-linux-gnuabi64.so.AnBotY.ltrans29.ltrans.o:
error adding symbols: bad value
collect2: error: ld returned 1 exit status
Full build log at
https://buildd.debian.org/status/fetch.php?pkg=dolfin&arch=mips64el&ver=2019.2.0%7Egit20200218.027d9cc-14&stamp=1597824051&raw=0
(see https://buildd.debian.org/status/logs.php?pkg=dolfin&arch=mips64el
)
No other arch is failing like this. I have no idea what to do with an
error like this.
Drew
Reply to: