Your message dated Sun, 13 Apr 2014 18:07:54 +0000
with message-id <[email protected]>
and subject line closing erroneously filed bug report
has caused the Debian Bug report #744424,
regarding dcbd: 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.)
--
744424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744424
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:dcbd
Version: 0.9.19-0
User: [email protected]
Usertags: autoreconf
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 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
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-20140414/buildlog_ubuntu-trusty-arm64.dcbd_0.9.19-0ubuntu1_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.
[...]
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 3458764513820540925
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for pkg-config... no
checking for LIBCONFIG... configure: creating ./config.status
config.status: creating Makefile
config.status: creating include/version.h
config.status: creating dcbd.spec
config.status: creating dcbd.pc
config.status: executing depfiles commands
=== configuring in libconfig-1.3.1 (/build/buildd/dcbd-0.9.19/libconfig-1.3.1)
configure: running /bin/bash ./configure '--prefix=/usr' '--build'
'aarch64-linux-gnu' '--mandir=${prefix}/share/man'
'--infodir=${prefix}/share/info' 'CFLAGS=' 'LDFLAGS=-Wl,-z,defs'
'build_alias=aarch64-linux-gnu' --cache-file=/dev/null --srcdir=.
checking build system type... Invalid configuration `aarch64-linux-gnu':
machine `aarch64' not recognized
configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed
configure: error: ./configure failed for libconfig-1.3.1
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Closing erroneously filed bug report, the package is not part of Debian.
Sorry for the noise.
--- End Message ---
