Your message dated Tue, 16 Apr 2024 03:04:21 +0000
with message-id <[email protected]>
and subject line Bug#1069021: Removed package(s) from unstable
has caused the Debian Bug report #744434,
regarding gcc-msp430: 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.)
--
744434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744434
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:gcc-msp430
Version: 4.6.3~mspgcc-20120406-5
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.gcc-msp430_4.6.3~mspgcc-20120406-5_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.
[...]
patching file gcc/testsuite/gcc.target/msp430/sf3201686.c
patching file gcc/testsuite/gcc.target/msp430/sf3207853.c
patching file gcc/testsuite/gcc.target/msp430/sf3237005_1.c
patching file gcc/testsuite/gcc.target/msp430/sf3237005_11.c
patching file gcc/testsuite/gcc.target/msp430/sf3237005_2.c
patching file gcc/testsuite/gcc.target/msp430/sf3237005_3.c
patching file gcc/testsuite/gcc.target/msp430/sf3237005_4.c
patching file gcc/testsuite/gcc.target/msp430/sf3237005_5.c
patching file gcc/testsuite/gcc.target/msp430/sf3237005_6.c
patching file gcc/testsuite/gcc.target/msp430/sf3237005_7.c
patching file gcc/testsuite/gcc.target/msp430/sf3237005_check.c
patching file gcc/testsuite/gcc.target/msp430/sf3257192_1.c
patching file gcc/testsuite/gcc.target/msp430/sf3261372.c
patching file gcc/testsuite/gcc.target/msp430/sf3273856.c
patching file gcc/testsuite/gcc.target/msp430/sf3290923.c
patching file gcc/testsuite/gcc.target/msp430/sf3296698.c
patching file gcc/testsuite/gcc.target/msp430/sf3300205.c
patching file gcc/testsuite/gcc.target/msp430/sf3383371_1.c
patching file gcc/testsuite/gcc.target/msp430/sf3383371_2.c
patching file gcc/testsuite/gcc.target/msp430/sf3397068.c
patching file gcc/testsuite/gcc.target/msp430/sf3423822_1.c
patching file gcc/testsuite/gcc.target/msp430/sf3426468.c
patching file gcc/testsuite/gcc.target/msp430/sf3428439.c
patching file gcc/testsuite/gcc.target/msp430/sf3433730.c
patching file gcc/testsuite/gcc.target/msp430/sf3474171.c
patching file gcc/testsuite/gcc.target/msp430/sf3474171_1.c
patching file gcc/testsuite/gcc.target/msp430/vararg-1.c
patching file gcc/testsuite/gcc.target/msp430/volpeep_mem.c
patching file gcc/testsuite/gcc.target/msp430/volpeep_reg.c
patching file gcc/testsuite/gcc.target/msp430/volpeep_volmem.c
patching file gcc/testsuite/gcc.target/msp430/vwa1.c
patching file gcc/testsuite/gcc.target/msp430/vwa2.c
patching file gcc/testsuite/gcc.target/msp430/vwa3.c
patching file gcc/testsuite/gcc.target/msp430/vwa4.c
patching file gcc/testsuite/gcc.target/msp430/vwa5.c
patching file gcc/testsuite/gcc.target/msp430/vwa_error.c
patching file gcc/testsuite/gcc.target/msp430/vwa_regression.c
patching file gcc/tree-flow.h
patching file gcc/tree-ssa-dom.c
patching file gcc/tree-ssa-forwprop.c
patching file libgcc/config.host
touch patch-stamp
dh_testdir
mkdir -p build-result
sed -i 's/BUILD_INFO=info/BUILD_INFO=/' ./gcc-4.6.3/configure
cd build-result &&
/build/buildd/gcc-msp430-4.6.3~mspgcc-20120406/./gcc-4.6.3/configure -v
--enable-languages=c,c++ --prefix=/usr --with-system-zlib
--infodir=\${prefix}/share/info --mandir=\${prefix}/share/man
--bindir=\${prefix}/bin --libexecdir=\${prefix}/lib --libdir=\${prefix}/lib
--build=aarch64-linux-gnu --host=aarch64-linux-gnu MAKEINFO=missing
--target=msp430
checking build system type... Invalid configuration `aarch64-linux-gnu':
machine `aarch64' not recognized
configure: error: /bin/bash
/build/buildd/gcc-msp430-4.6.3~mspgcc-20120406/./gcc-4.6.3/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 ---
Version: 4.6.3~mspgcc-20120406-7.1+rm
Dear submitter,
as the package gcc-msp430 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1069021
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
