[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#727457: marked as done (mgp: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4)

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 #727457,
regarding mgp: 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 owner@bugs.debian.org
immediately.)


-- 
727457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727457
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:mgp
Version: 1.13a+upstream20090219-6
Severity: normal
User: debian-arm@lists.debian.org
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.

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-20131023/logs/buildlog_ubuntu-trusty-arm64.mgp_1.13a+upstream20090219-6_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.

[...]
Setting up x11proto-record-dev (1.14.2-1) ...
Setting up libxtst-dev:arm64 (2:1.2.2-1) ...
Setting up sharutils (1:4.11.1-1ubuntu2) ...
Setting up xutils-dev (1:7.7~1ubuntu5) ...
Setting up python3 (3.3.2-14ubuntu1) ...
running python rtupdate hooks for python3.3...
running python post-rtupdate hooks for python3.3...
Setting up dh-python (1.20131003-1) ...
Setting up apparmor-easyprof (2.8.0-0ubuntu31) ...
Setting up dh-apparmor (2.8.0-0ubuntu31) ...
Setting up debhelper (9.20130630ubuntu1) ...
Setting up devscripts (2.13.4) ...
Processing triggers for libc-bin ...
Checking correctness of source dependencies...
Toolchain package versions: libc6-dev_2.17-93ubuntu4 make_3.81-8.2ubuntu3 dpkg-dev_1.16.12ubuntu1 gcc-4.8_4.8.1-10ubuntu8 g++-4.8_4.8.1-10ubuntu8 binutils_2.23.52.20130913-0ubuntu1 libstdc++-4.8-dev_4.8.1-10ubuntu8 libstdc++6_4.8.1-10ubuntu8
------------------------------------------------------------------------------
dpkg-source: warning: -sn is not a valid option for Dpkg::Source::Package::V3::quilt
gpgv: Signature made Mon Oct  1 12:37:39 2012 UTC using RSA key ID 7D86500B
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./mgp_1.13a+upstream20090219-6.dsc
dpkg-source: info: extracting mgp in mgp-1.13a+upstream20090219
dpkg-source: info: unpacking mgp_1.13a+upstream20090219.orig.tar.gz
dpkg-source: info: unpacking mgp_1.13a+upstream20090219-6.debian.tar.gz
dpkg-source: info: applying 01_mgpnet_in.diff
dpkg-source: info: applying 04_tex2ps_bashism.diff
dpkg-source: info: applying 05_rakugaki_cursor.diff
dpkg-source: info: applying 568339.patch
dpkg-buildpackage: source package mgp
dpkg-buildpackage: source version 1.13a+upstream20090219-6
 dpkg-source --before-build mgp-1.13a+upstream20090219
dpkg-buildpackage: host architecture arm64
 /usr/bin/fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp install-stamp
[ ! -f Makefile ] || make distclean
rm -f `find . -name "*~"`
rm -rf debian/mgp debian/files* core debian/substvars
rm -f Makefile Imakefile *._man
dh_clean
dpkg-buildpackage: warning: debian/rules must be updated to support the 'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be missing)
 debian/rules build
dh_testdir
./configure --prefix=/usr  --enable-locale --enable-freetype --enable-freetype-charset16 --enable-xft2 --disable-vflib --enable-gif aarch64-linux-gnu
configure: WARNING: you should use --build, --host, --target
checking whether make sets $(MAKE)... yes
checking build system type... Invalid configuration `aarch64-linux-gnu': machine `aarch64' not recognized
configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed
make: *** [build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build 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 ---
Reply to: