Your message dated Thu, 28 Mar 2019 11:33:49 +0100
with message-id <[email protected]>
and subject line Re: binutils: ftbfs with GCC-9
has caused the Debian Bug report #925640,
regarding binutils: ftbfs with GCC-9
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.)
--
925640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925640
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:binutils
Version: 2.31.1-16
Severity: normal
Tags: sid bullseye
User: [email protected]
Usertags: ftbfs-gcc-9
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/binutils_2.31.1-16_unstable_gcc9.log
The last lines of the build log are at the end of this report.
To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html
GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.
[...]
package: binutils-alpha-linux-gnu
version: 2.31.1-16
architecture: amd64
-
package: binutils-aarch64-linux-gnu
version: 2.31.1-16
architecture: amd64
-
package: binutils
version: 2.31.1-16
architecture: amd64
-
package: bash
version: 5.0-2
architecture: amd64
essential: true
-
package: base-passwd
version: 3.5.46
architecture: amd64
essential: true
-
package: base-files
version: 10.1
architecture: amd64
essential: true
-
package: autoconf
version: 2.69-11
architecture: all
background-packages: 59784
foreground-packages: 1
total-packages: 59785
broken-packages: 0
+------------------------------------------------------------------------------+
| Cleanup |
+------------------------------------------------------------------------------+
Purging /<<BUILDDIR>>
Not cleaning session: cloned chroot in use
E: Package build dependencies not satisfied; skipping
+------------------------------------------------------------------------------+
| Summary |
+------------------------------------------------------------------------------+
Build Architecture: amd64
Build Type: any
Build-Space: n/a
Build-Time: 0
Distribution: unstable
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: binutils_2.31.1-16
Machine Architecture: amd64
Package: binutils
Package-Time: 0
Source-Version: 2.31.1-16
Space: n/a
Status: given-back
Version: 2.31.1-16
--------------------------------------------------------------------------------
Finished at 2019-03-26T13:17:56Z
Build needed 00:00:00, no disk space
E: Package build dependencies not satisfied; skipping
DC-Status: Failed 52.31819875s
DC-Time-Estimation: 52.31819875 versus expected 1 (r/m: 51.31819875 ; m: 1.0)
--- End Message ---
--- Begin Message ---
false positive, because the GCC 9 in experimental dependes on binutils 2.32.
--- End Message ---
