Your message dated Mon, 12 Jun 2017 23:05:10 +0300
with message-id <20170612200509.b4jpacqqrkbymnon@localhost>
and subject line Closing obsolete autotools/autoreconf requests
has caused the Debian Bug report #727934,
regarding photoprint: 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.)
--
727934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727934
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:photoprint
Version: 0.4.2~pre2-2.1
Severity: normal
User: [email protected]
Usertags: arm64
The package fails to build on arm64 (aarch64-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 autotools_dev (yes, underscore).
- For other rules files, call dh_autotools-dev_updateconfig before
calling configure (in the build or configure target), and call
dh_autotools-dev_restoreconfig before calling 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
aarch64 in the config.sub file(s) should print some lines.
The full build log can be found at:
http://people.debian.org/~doko/logs/arm64-20131027/buildlog_ubuntu-trusty-arm64.photoprint_0.4.2~pre2-2.1ubuntu1_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.
Please note that these build were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.
[...]
rm -f config.log config.status
rm -f scripts/ltmain.sh
dh_clean
debian/rules build-arch
dh_testdir
libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `scripts'.
libtoolize: copying file `scripts/ltmain.sh'
libtoolize: You should add the contents of the following files to `aclocal.m4':
libtoolize: `/usr/share/aclocal/libtool.m4'
libtoolize: `/usr/share/aclocal/ltoptions.m4'
libtoolize: `/usr/share/aclocal/ltversion.m4'
libtoolize: `/usr/share/aclocal/ltsugar.m4'
libtoolize: `/usr/share/aclocal/lt~obsolete.m4'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf
./configure --prefix=/usr --disable-rpath --build aarch64-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/build/buildd/photoprint-0.4.2~pre2/scripts/missing: Unknown `--is-lightweight'
option
Try `/build/buildd/photoprint-0.4.2~pre2/scripts/missing --help' for more
information
configure: WARNING: 'missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for a sed that does not truncate output... /bin/sed
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking build system type... Invalid configuration `aarch64-linux-gnu':
machine `aarch64' not recognized
configure: error: /bin/bash scripts/config.sub aarch64-linux-gnu failed
make: *** [configure-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
This email closes autotools/autoreconf in packages that have
successfully been built on all current release architectures.
debhelper defaults to updating autotools files since January 2016,
which automatically fixed many of these bugs and makes explicit
updating for these packages obsolete.
debhelper compat 10 defaults to running autoreconf,
making manual adding of dh-autoreconf mostly obsolete.
Updating to compat 10 is a better solution than adding dh-autoreconf,
and compat < 10 is expected to become a lintian warning before buster.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--- End Message ---
