Bug#864448: bowtie FTBFS on mips64el: /usr/bin/ld: .gnu.hash is incompatible with the MIPS ABI

Adrian Bunk <[email protected]>
Newsgroups gmane.linux.debian.ports.mips
Message-ID <149694828130.16660.15630139627259839324.reportbug__15048.1147262783$1496948601$gmane$org@localhost>
Source: bowtie
Version: 1.2.0+dfsg-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=bowtie&arch=mips64el&ver=1.2.0%2Bdfsg-1&stamp=1496936597&raw=0

...
make[2]: Entering directory '/«BUILDDIR»/bowtie-1.2.0+dfsg'
g++ -w -O3 -DCOMPILER_OPTIONS="\"-O3  -Wl,--hash-style=both -DWITH_TBB -DNO_SPINLOCK -DWITH_QUEUELOCK=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=.=. -fstack-protector-strong -Wformat -Werror=format-security  -g -O2 -fdebug-prefix-map=.=. -fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -Wl,-z,now\""  -Wl,--hash-style=both -DWITH_TBB -DNO_SPINLOCK -DWITH_QUEUELOCK=1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/«BUILDDIR»/bowtie-1.2.0+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security  -g -O2 -fdebug-prefix-map=/«BUILDDIR»/bowtie-1.2.0+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -Wl,-z,now  \
	-fno-strict-aliasing -DBOWTIE_VERSION="\"`cat VERSION`\"" -DBUILD_HOST="\"Debian-reproducible\"" -DBUILD_TIME="\"`dpkg-parsechangelog --show-field Date`\"" -DCOMPILER_VERSION="\"`g++ -w -v 2>&1 | tail -1 | sed 's/ *(.*//'`\"" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE  -DPREFETCH_LOCALITY=2 -DBOWTIE_MM -DBOWTIE_SHARED_MEM -DNDEBUG -Wall \
	-I /usr/include/seqan \
	-o bowtie-build-s ebwt_build.cpp \
	ccnt_lut.cpp ref_read.cpp alphabet.cpp shmem.cpp edit.cpp ebwt.cpp  bowtie_build_main.cpp \
	-lpthread -ltbb -ltbbmalloc_proxy 
/usr/bin/ld: .gnu.hash is incompatible with the MIPS ABI
collect2: error: ld returned 1 exit status
Makefile:258: recipe for target 'bowtie-build-s' failed
make[2]: *** [bowtie-build-s] Error 1
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.