Hi,
I tried to refresh hmmer2 packaging to recent packaging standards (and
drop pvm (as suggested when I was asking about a bug in pvm). Inside the
last release I used the weak approach:
* Stick to debhelper 10 (in compat level 11 dh_auto_configure
passes --runstatedir=/run to ./configure. This causes FTBFS.)
but I think now it is time to deal with
dh_auto_configure -- --enable-threads --enable-lfs # --enable-pvm
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --enable-threads
--enable-lfs
configure: error: unrecognized option: --runstatedir=/run
Try `./configure --help' for more information.
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --enable-threads
--enable-lfs returned exit code 1
Any volunteer to teach the outdated configure script dealing with
--runstatedir option somehow (probably simply ignoring it).
Kind regards
Andreas.
--
http://fam-tille.de
