Bug#744583: gnome-vfsmm2.6: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4

Matthias Klose doko at debian.org
Sun Apr 13 16:50:46 UTC 2014


Package: src:gnome-vfsmm2.6
Version: 2.26.0-1
User: debian-devel at lists.debian.org
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.gnome-vfsmm2.6_2.26.0-1build1_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.

[...]
make[3]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/monitor'
Making install in directory_visit
make[3]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/directory_visit'
make[4]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/directory_visit'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/directory_visit'
make[3]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/directory_visit'
Making install in mime_type_list
make[3]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/mime_type_list'
make[4]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/mime_type_list'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/mime_type_list'
make[3]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/mime_type_list'
Making install in transfer
make[3]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/transfer'
make[4]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/transfer'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/transfer'
make[3]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/transfer'
Making install in async
make[3]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/async'
make[4]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/async'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/async'
make[3]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples/async'
make[3]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples'
make[4]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples'
make[3]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples'
make[2]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0/examples'
make[2]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0'
*** Everything completed ***
make[3]: Entering directory `/build/buildd/gnome-vfsmm2.6-2.26.0'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0'
make[2]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0'
make[1]: Leaving directory `/build/buildd/gnome-vfsmm2.6-2.26.0'
touch debian/stamp-makefile-install
chrpath -d debian/tmp/usr/lib/*.so*
open: No such file or directory
elf_open: Invalid argument
make: *** [common-install-impl] Error 1
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary-arch gave error exit status 2




More information about the pkg-gnome-maintainers mailing list