Your message dated Sun, 27 Oct 2013 07:46:54 +1030
with message-id <[email protected]>
and subject line Re: Bug#727481: opus-tools: update config.{sub,guess} for the 
AArch64 port
has caused the Debian Bug report #727481,
regarding opus-tools: update config.{sub,guess} for the AArch64 port
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.)


-- 
727481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727481
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:opus-tools
Version: 0.1.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.

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.opus-tools_0.1.2-1_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 intltool-debian (0.35.0+20060710.1) ...
Setting up po-debconf (1.0.16+nmu2ubuntu1) ...
Setting up libogg-dev:arm64 (1.3.1-1) ...
Setting up libopus-dev (1.0.3-0ubuntu1) ...
Setting up pkg-config (0.26-1ubuntu4) ...
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.20130921ubuntu1) ...
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.2-1ubuntu2 g++-4.8_4.8.2-1ubuntu2 
binutils_2.23.90.20131017-1ubuntu1 libstdc++-4.8-dev_4.8.2-1ubuntu2 
libstdc++6_4.8.2-1ubuntu2
------------------------------------------------------------------------------
gpgv: Signature made Wed Jun 13 00:58:20 2012 UTC using DSA key ID 68021CE4
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./opus-tools_0.1.2-1.dsc
dpkg-source: info: extracting opus-tools in opus-tools-0.1.2
dpkg-source: info: unpacking opus-tools_0.1.2.orig.tar.gz
dpkg-source: info: applying opus-tools_0.1.2-1.diff.gz
dpkg-buildpackage: source package opus-tools
dpkg-buildpackage: source version 0.1.2-1
 dpkg-source --before-build opus-tools-0.1.2
dpkg-buildpackage: host architecture arm64
 /usr/bin/fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f *-stamp
rm -f -r objs
dh_clean
 debian/rules build-arch
dh_testdir
mkdir -p objs
cd objs &&      ../configure --host=aarch64-linux-gnu   \
                                     --build=aarch64-linux-gnu  \
                                     --prefix=/usr
checking git revision... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
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 to enable maintainer-specific portions of Makefiles... no
checking build system type... Invalid configuration `aarch64-linux-gnu': 
machine `aarch64' not recognized
configure: error: /bin/bash ../config.sub aarch64-linux-gnu failed
make: *** [objs/config.status] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

--- End Message ---
--- Begin Message ---
On Wed, Oct 23, 2013 at 11:13:27PM +0000, Matthias Klose wrote:
> Package: src:opus-tools
> Version: 0.1.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,
> 
> Please note that these build were done in an Ubuntu development,
> environment there may be a few false positives in these bug reports.

And this is very likely to be one of them :)

The version in Debian for some months now has new enough autotools,
and there shouldn't be anything else preventing this one from working
on aarch64 just fine.

  Ron

--- End Message ---

Reply via email to