Your message dated Tue, 03 Jun 2014 23:49:04 +0200
with message-id <[email protected]>
and subject line This has been fixed for some time.
has caused the Debian Bug report #744637,
regarding nbdkit: run dh-autoreconf to update config.{sub,guess} and
{libtool,aclocal}.m4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
744637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744637
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:nbdkit
Version: 1.1.3-2
User: [email protected]
Usertags: autoreconf
The package fails to build on ppc64el (powerpc64le-linux-gnu), because
the config.{guess,sub} files are out of date, and are not updated during
the build. If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.
- For dh, call dh --with autoreconf.
- For cdbs based build systems, include
/usr/share/cdbs/1/rules/autoreconf.mk
- For other rules files, call dh_autoreconf before calling
configure (in the build or configure target), and call
dh_autoreconf_clean before dh_clean in the clean target.
For combining autoreconf and autotools_dev, see bug #698765.
After the build on any architecture, and before a clean, a grep for
powerpc64le in the configure, aclocal.m4 and/or libtool.m4 file(s)
should print some lines. It is not enough to just update the
config.guess and config.sub files.
The full build log can be found at:
http://people.debian.org/~doko/logs/ppc64el-20140414/buildlog_ubuntu-trusty-ppc64el.nbdkit_1.1.3-2_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.
Please note that these builds were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.
See https://wiki.debian.org/qa.debian.org/FTBFS for a guide how to
address these.
[...]
configure: creating ./config.status
config.status: creating Makefile
config.status: creating docs/Makefile
config.status: creating include/Makefile
config.status: creating plugins/Makefile
config.status: creating plugins/example1/Makefile
config.status: creating plugins/example2/Makefile
config.status: creating plugins/example3/Makefile
config.status: creating plugins/file/Makefile
config.status: creating plugins/guestfs/Makefile
config.status: creating plugins/gzip/Makefile
config.status: creating plugins/libvirt/Makefile
config.status: creating plugins/vddk/Makefile
config.status: creating plugins/xz/Makefile
config.status: creating src/Makefile
config.status: creating tests/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
dh_auto_build -a
make[1]: Entering directory `/build/buildd/nbdkit-1.1.3'
make all-recursive
make[2]: Entering directory `/build/buildd/nbdkit-1.1.3'
Making all in docs
make[3]: Entering directory `/build/buildd/nbdkit-1.1.3/docs'
pod2man -u --stderr --section=1 --center=nbdkit --release=nbdkit --name=nbdkit
nbdkit.pod nbdkit.1
pod2man -u --stderr --section=3 --center=nbdkit --release=nbdkit
--name=nbdkit-plugin nbdkit-plugin.pod nbdkit-plugin.3
make[3]: Leaving directory `/build/buildd/nbdkit-1.1.3/docs'
Making all in plugins
make[3]: Entering directory `/build/buildd/nbdkit-1.1.3/plugins'
Making all in example1
make[4]: Entering directory `/build/buildd/nbdkit-1.1.3/plugins/example1'
/bin/bash ../../libtool --tag=CC --mode=compile gcc -std=gnu99
-DHAVE_CONFIG_H -I. -I../.. -I../../include -D_FORTIFY_SOURCE=2 -g -O3
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c
-o nbdkit_example1_plugin_la-example1.lo `test -f 'example1.c' || echo
'./'`example1.c
libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../include
-D_FORTIFY_SOURCE=2 -g -O3 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -c example1.c -o nbdkit_example1_plugin_la-example1.o
/bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O3
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security
-module -avoid-version -shared -Wl,-Bsymbolic-functions -Wl,-z,relro -o
nbdkit-example1-plugin.la -rpath /usr/lib/powerpc64le-linux-gnu/nbdkit/plugins
nbdkit_example1_plugin_la-example1.lo
libtool: link: can not build a shared library
libtool: link: See the libtool documentation for more information.
libtool: link: Fatal configuration error.
make[4]: *** [nbdkit-example1-plugin.la] Error 1
make[4]: Leaving directory `/build/buildd/nbdkit-1.1.3/plugins/example1'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/build/buildd/nbdkit-1.1.3/plugins'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/buildd/nbdkit-1.1.3'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd/nbdkit-1.1.3'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
control: fixed -1 1.1.4-1
Since 1.1.4-1, dh-autoreconf is used to build nbdkit, as suggested in
the bug report.
Cheers,
-Hilko
--- End Message ---
