Processing commands for cont...@bugs.debian.org:
> found 840360 20160807-1
Bug #840360 [src:libiberty] Multiple security issues
Marked as found in versions libiberty/20160807-1.
> tags 840360 + upstream fixed-upstream
Bug #840360 [src:libiberty] Multiple security issues
Added tag(s) upstream and f
Source: libiberty
Severity: important
Tags: security
Several security issues have been reported in libiberty,
the security tracker has additional references:
https://security-tracker.debian.org/tracker/CVE-2016-6131
https://security-tracker.debian.org/tracker/CVE-2016-4493
https://security-tracker
LAST_UPDATED: Mon Oct 10 03:12:04 UTC 2016 (revision 240907)
Target: i686-kfreebsd-gnu
gcc version 6.2.0 20161010 (Debian 6.2.0-6)
Native configuration is i686-pc-kfreebsd-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/abi/abi-tag23.C -std=gnu++11 (test for warnings
LAST_UPDATED: Mon Oct 10 03:12:04 UTC 2016 (revision 240907)
Target: powerpc64le-linux-gnu
gcc version 6.2.0 20161010 (Debian 6.2.0-6)
Native configuration is powerpc64le-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: c-c++-common/asan/null-deref-1.c -O2
LAST_UPDATED: Mon Oct 10 03:12:04 UTC 2016 (revision 240907)
Target: x86_64-kfreebsd-gnu
gcc version 6.2.0 20161010 (Debian 6.2.0-6)
Native configuration is x86_64-pc-kfreebsd-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/abi/abi-tag23.C -std=gnu++11 (test for
LAST_UPDATED: Mon Oct 10 03:12:04 UTC 2016 (revision 240907)
Target: i686-linux-gnu
gcc version 6.2.0 20161010 (Debian 6.2.0-6)
Native configuration is i686-pc-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/abi/abi-tag23.C -std=gnu++11 (test for warnings, line
LAST_UPDATED: Mon Oct 10 03:12:04 UTC 2016 (revision 240907)
Target: x86_64-linux-gnu
gcc version 6.2.0 20161010 (Debian 6.2.0-6)
Native configuration is x86_64-pc-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/abi/abi-tag23.C -std=gnu++11 (test for warnings
Control: severity -1 important
The original build failure is solved by removing vendor and using system
libs.
On Wed, 5 Oct 2016 09:12:54 +0200 Emilio Pozuelo Monfort
wrote:
> Is gcc-6_6.1.1-11 (the one in testing) affected by this?
It seems so from the upstream bug
https://github.com/golang/go
Processing control commands:
> severity -1 important
Bug #839598 [gccgo-6] unable to build gitlab-workhorse with gccgo-6
Severity set to 'important' from 'serious'
--
839598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
9 matches
Mail list logo