Source: libverto
Version: 0.3.1-1
Severity: normal
Tags: ftbfs

Hi,

yesterday a new version of dash got uploaded which enabled LINENO
support. As a result, autoconf will choose dash instead of bash for
configure and libverto fails to build from source due to bashisms in
configure.ac. The change has already been reverted in dash in unstable
and a dash version with LINENO support enabled was uploaded to
experimental instead. Please fix the bashisms in configure.ac. Sadly I
was unable to come up with a patch because I couldn't figure out how to
add an additional patch without errors from dpkg-source. But basically
the necessary changes involve changing the == operator to =.

Thanks!

cheers, josch


checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
./configure: 13402: test: xauto: unexpected operator
./configure: 13407: test: xyes: unexpected operator
./configure: 13412: test: xauto: unexpected operator
./configure: 13417: test: xauto: unexpected operator
./configure: 13431: test: xauto: unexpected operator
./configure: 13438: test: xyes: unexpected operator
./configure: 13445: test: xauto: unexpected operator
./configure: 13452: test: xauto: unexpected operator
checking for glib-2.0... yes
./configure: 13537: test: xauto: unexpected operator
checking for ev.h... yes
checking for ev_loop_new in -lev... yes
./configure: 13594: test: xyes: unexpected operator
checking for libevent >= 2.0... no
./configure: 13671: test: xno: unexpected operator
checking for tevent... no
./configure: 13748: test: xno: unexpected operator
./configure: 13753: test: x: unexpected operator
./configure: 13761: test: x: unexpected operator
./configure: 13769: test: x: unexpected operator
./configure: 13777: test: x: unexpected operator
./configure: 13785: test: x: unexpected operator
./configure: 13793: test: x: unexpected operator
./configure: 13801: test: x: unexpected operator
./configure: 13809: test: x: unexpected operator

Reply via email to