Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 835757 gdc-6 6.2.0-1
Bug #835757 [src:appstream-generator] appstream-generator: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): undefined reference 
to symbol 'dlclose@@GLIBC_2.2.5'
Bug reassigned from package 'src:appstream-generator' to 'gdc-6'.
No longer marked as found in versions appstream-generator/0.4.0-1.
Ignoring request to alter fixed versions of bug #835757 to the same values 
previously set
Bug #835757 [gdc-6] appstream-generator: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): undefined reference 
to symbol 'dlclose@@GLIBC_2.2.5'
Marked as found in versions gcc-6/6.2.0-1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
835757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#835847: marked as done (gcc-6: rework the patch of gdc cross install directory patch with 6.2.0)

[Debian Bug Tracking System]

Your message dated Wed, 31 Aug 2016 13:20:22 +
with message-id 
and subject line Bug#835847: fixed in gcc-6 6.2.0-2
has caused the Debian Bug report #835847,
regarding gcc-6: rework the patch of gdc cross install directory patch with 
6.2.0
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 ow...@bugs.debian.org
immediately.)


-- 
835847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-6
Version: 6.2.0-1

Hi, 6.2 changes the way to set gdc install directory.
We need rework this patch.

-- 
YunQiang Su
diff --git a/debian/patches/gdc-cross-install-location.diff 
b/debian/patches/gdc-cross-install-location.diff
index 21d4e92..c4dd439 100644
--- a/debian/patches/gdc-cross-install-location.diff
+++ b/debian/patches/gdc-cross-install-location.diff
@@ -1,13 +1,13 @@
-Index: b/src/libphobos/configure.ac
+Index: b/src/libphobos/m4/druntime.m4
 ===
 a/src/libphobos/configure.ac
-+++ b/src/libphobos/configure.ac
-@@ -167,7 +167,7 @@ AC_SUBST(phobos_toolexecdir)
- AC_SUBST(phobos_toolexeclibdir)
+--- a/src/libphobos/m4/druntime.m4
 b/src/libphobos/m4/druntime.m4
+@@ -78,7 +78,7 @@ AC_DEFUN([DRUNTIME_INSTALL_DIRECTORIES],
+   AC_SUBST(toolexeclibdir)
  
- # Default case for install directory for D sources files.
--gdc_include_dir='${libdir}/gcc/${target_alias}'/${d_gcc_ver}/include/d
-+gdc_include_dir='${libdir}/gcc-cross/${target_alias}'/${d_gcc_ver}/include/d
- AC_SUBST(gdc_include_dir)
+   # Default case for install directory for D sources files.
+-  gdc_include_dir='${libdir}/gcc/${target_alias}'/${d_gcc_ver}/include/d
++  gdc_include_dir='${libdir}/gcc-cross/${target_alias}'/${d_gcc_ver}/include/d
+   AC_SUBST(gdc_include_dir)
+ ])
  
- dnl Checks for header files.
--- End Message ---
--- Begin Message ---
Source: gcc-6
Source-Version: 6.2.0-2

We believe that the bug you reported is fixed in the latest version of
gcc-6, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 31 Aug 2016 12:28:38 +0200
Source: gcc-6
Binary: gcc-6-base libgcc1 libgcc1-dbg libgcc2 libgcc2-dbg libgcc-6-dev libgcc4 
libgcc4-dbg lib64gcc1 lib64gcc1-dbg lib64gcc-6-dev lib32gcc1 lib32gcc1-dbg 
lib32gcc-6-dev libn32gcc1 libn32gcc1-dbg libn32gcc-6-dev libx32gcc1 
libx32gcc1-dbg libx32gcc-6-dev gcc-6 gcc-6-multilib gcc-6-test-results 
gcc-6-plugin-dev gcc-6-hppa64-linux-gnu cpp-6 gcc-6-locales g++-6 
g++-6-multilib libgomp1 libgomp1-dbg lib32gomp1 lib32gomp1-dbg lib64gomp1 
lib64gomp1-dbg libn32gomp1 libn32gomp1-dbg libx32gomp1 libx32gomp1-dbg libitm1 
libitm1-dbg lib32itm1 lib32itm1-dbg lib64itm1 lib64itm1-dbg libx32itm1 
libx32itm1-dbg libatomic1 libatomic1-dbg lib32atomic1 lib32atomic1-dbg 
lib64atomic1 lib64atomic1-dbg libn32atomic1 libn32atomic1-dbg libx32atomic1 
libx32atomic1-dbg libasan3 libasan3-dbg lib32asan3 lib32asan3-dbg lib64asan3 
lib64asan3-dbg libx32asan3 libx32asan3-dbg liblsan0 liblsan0-dbg lib32lsan0 
lib32lsan0-dbg libx32lsan0 libx32lsan0-dbg libtsan0 libtsan0-dbg libubsan0 
libubsan0-dbg lib32ubsan0
 lib32ubsan0-dbg lib64ubsan0 lib64ubsan0-dbg libx32ubsan0 libx32ubsan0-dbg 
libcilkrts5 libcilkrts5-dbg lib32cilkrts5 lib32cilkrts5-dbg lib64cilkrts5 
lib64cilkrts5-dbg libx32cilkrts5 libx32cilkrts5-dbg libmpx2 libmpx2-dbg 
lib32mpx2 lib32mpx2-dbg lib64mpx2 lib64mpx2-dbg libquadmath0 libquadmath0-dbg 
lib32quadmath0 lib32quadmath0-dbg lib64quadmath0 lib64quadmath0-dbg 
libx32quadmath0 libx32quadmath0-dbg libcc1-0 libgccjit0 libgccjit0-dbg 
libgccjit-6-doc libgccjit-6-dev gobjc++-6 gobjc++-6-multilib gobjc-6 
gobjc-6-multilib libobjc-6-dev lib64objc-6-dev lib32objc-6-dev libn32objc-6-dev 
libx32objc-6-dev libobjc4 libobjc4-dbg lib64objc4 lib64objc4-dbg lib32objc4 
lib32objc4-dbg libn32objc4 libn32objc4-dbg libx32objc4 libx32objc4-dbg 
gfortran-6 gfortran-6-multilib libgfortran-6-dev lib64gfortran-6-dev 
lib32gfortran-6-dev l

Processed (with 1 error): merge duplicate gdc-6 bugs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 835255 835757
Bug #835255 [gdc-6] gdc-6: std.datetime: undefined reference to 
dlopen/dlsym/dlclose
Unable to merge bugs because:
blocks of #835757 is '' not '835281 835727'
Failed to merge 835255: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
835255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835255
835757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#834492: marked as done (clang-3.9: "non-virtual thunk" abi_tag mangling is different from g++)

[Debian Bug Tracking System]

Your message dated Sun, 4 Sep 2016 13:46:35 +0200
with message-id <86abefe7-ff14-92a5-2098-518e208b4...@debian.org>
and subject line Fixed in 6.2.0-2
has caused the Debian Bug report #834492,
regarding clang-3.9: "non-virtual thunk" abi_tag mangling is different from g++
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 ow...@bugs.debian.org
immediately.)


-- 
834492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clang-3.9
Version: 1:3.9~+rc1-1~exp1
Severity: important

Dear Maintainer,

The new mangling behavior of clang++ for GCC abi_tag attribute seems to be
different from the g++ one on some edge cases.

Consider the following code:
$ cat classes.hpp
#include 

struct Mother
{
  virtual ~Mother() {};
  int bar;
};

struct Father
{
  virtual std::string get_foo()  = 0;
};

class Derived:
  public Mother,
  public Father
{
public:
  std::string get_foo();
};

$ cat classes.cpp
#include "classes.hpp"

std::string Derived::get_foo() { return ""; }

$ cat main.cpp
#include "classes.hpp"

struct Final:
  public Derived
{
};

int main()
{
  Final().get_foo();
}

When compiling the classes with clang++ and trying to link the executable with
g++ one gets the following link error:
$ clang++-3.9 -c classes.cpp && g++-5 main.cpp classes.o
/tmp/cchpctTt.o:main.cpp:vtable for Final : erreur : référence à « non-
virtual thunk to Derived::get_foo() » non définie
collect2: error: ld returned 1 exit status

And it seems this symbol is mangled differently by clang++ and g++:
$ clang++-3.9 -c classes.cpp && nm -C classes.o | grep get_foo
 T Derived::get_foo[abi:cxx11]()
0070 T non-virtual thunk to Derived::get_foo[abi:cxx11]()

$ g++-5 -c classes.cpp && nm -C classes.o | grep get_foo
 T Derived::get_foo[abi:cxx11]()
0065 T non-virtual thunk to Derived::get_foo()



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'stable-updates'), (800, 'stable'), (700, 
'unstable'), (90, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages clang-3.9 depends on:
ii  binutils 2.26.1-1
ii  libc62.23-4
ii  libc6-dev2.23-4
ii  libclang-common-3.9-dev  1:3.9~+rc1-1~exp1
ii  libclang1-3.91:3.9~+rc1-1~exp1
ii  libgcc-6-dev 6.1.1-10
ii  libgcc1  1:6.1.1-10
ii  libllvm3.9   1:3.9~+rc1-1~exp1
ii  libobjc-6-dev6.1.1-10
ii  libstdc++-6-dev  6.1.1-10
ii  libstdc++6   6.1.1-10

Versions of packages clang-3.9 recommends:
ii  llvm-3.9-dev  1:3.9~+rc1-1~exp1
ii  python2.7.11-2

Versions of packages clang-3.9 suggests:
pn  clang-3.9-doc  
pn  gnustep
pn  gnustep-devel  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 6.2.0-2--- End Message ---

Bug#835255: marked as done (gdc-6: std.datetime: undefined reference to dlopen/dlsym/dlclose)

[Debian Bug Tracking System]

Your message dated Sun, 04 Sep 2016 16:41:49 +
with message-id 
and subject line Bug#835255: fixed in gcc-6 6.2.0-3
has caused the Debian Bug report #835255,
regarding gdc-6: std.datetime: undefined reference to dlopen/dlsym/dlclose
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 ow...@bugs.debian.org
immediately.)


-- 
835255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdc-6
Version: 6.2.0-1
Severity: normal

Hi. In this release, programs that reference std.datetime fail to
build, with error messages referencing curl and libdl. I don't know
what's going on here, but it seems there's something badly broken in
libphobos.

$ cat date.d
import std.datetime;
void main () { }

$ gdc -o date date.d
/usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): In function 
`_D3std3net4curl7CurlAPI19_sharedStaticDtor18FZv':
/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3682:
 undefined reference to `dlclose'
/usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): In function 
`_D3std3net4curl7CurlAPI7loadAPIFZPv':
/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3630:
 undefined reference to `dlopen'
/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3636:
 undefined reference to `dlsym'
/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3662:
 undefined reference to `dlsym'
/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3662:
 undefined reference to `dlsym'
/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3662:
 undefined reference to `dlsym'
/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3662:
 undefined reference to `dlsym'
/usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o):/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3662:
 more undefined references to `dlsym' follow
/usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): In function 
`_D3std3net4curl7CurlAPI7loadAPIFZPv':
/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3639:
 undefined reference to `dlclose'
/build/gcc-6-JZuWWC/gcc-6-6.2.0/build/x86_64-linux-gnu/libphobos/src/../../../../src/libphobos/src/std/net/curl.d:3651:
 undefined reference to `dlopen'
collect2: error: ld returned 1 exit status



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdc-6 depends on:
ii  g++-66.2.0-1
ii  gcc-6-base   6.2.0-1
ii  libc62.23-4
ii  libgmp10 2:6.1.1+dfsg-1
ii  libisl15 0.17.1-1
ii  libmpc3  1.0.3-1
ii  libmpfr4 3.1.4-2
ii  libphobos-6-dev  6.2.0-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

gdc-6 recommends no packages.

gdc-6 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gcc-6
Source-Version: 6.2.0-3

We believe that the bug you reported is fixed in the latest version of
gcc-6, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Sep 2016 12:38:47 +0200
Source: gcc-6
Binary: gcc

Bug#835757: marked as done (appstream-generator: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5')

[Debian Bug Tracking System]

Your message dated Sun, 04 Sep 2016 16:41:49 +
with message-id 
and subject line Bug#835757: fixed in gcc-6 6.2.0-3
has caused the Debian Bug report #835757,
regarding appstream-generator: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): undefined reference 
to symbol 'dlclose@@GLIBC_2.2.5'
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 ow...@bugs.debian.org
immediately.)


-- 
835757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appstream-generator
Version: 0.4.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # stupid hack since dub can't work with local repos in system locations 
> properly at
> # time...
> mkdir /tmp/dub-repo
> mkdir /tmp/fakehome
> cp -dr /usr/include/d/mustache-d /tmp/dub-repo
> HOME=/tmp/fakehome dub add-local /tmp/dub-repo/mustache-d 0.1.1
> Registered package: mustache-d (version: 0.1.1)
> HOME=/tmp/fakehome dub -v --skip-registry=standard build --parallel
> Refreshing local packages (refresh existing: true)...
> Looking for local package map at /var/lib/dub/packages/local-packages.json
> Looking for local package map at 
> /tmp/fakehome/.dub/packages/local-packages.json
> Try to load local package map at 
> /tmp/fakehome/.dub/packages/local-packages.json
> Note: Failed to determine version of package mustache-d at .. Assuming 
> ~master.
> Note: Failed to determine version of package appstream-generator at .. 
> Assuming ~master.
> Refreshing local packages (refresh existing: false)...
> Looking for local package map at /var/lib/dub/packages/local-packages.json
> Looking for local package map at 
> /tmp/fakehome/.dub/packages/local-packages.json
> Try to load local package map at 
> /tmp/fakehome/.dub/packages/local-packages.json
>   Version selection for dependency mustache-d (mustache-d) of 
> appstream-generator is missing.
>   Missing dependency mustache-d ~>0.1.1 of appstream-generator
> Refreshing local packages (refresh existing: false)...
> Looking for local package map at /var/lib/dub/packages/local-packages.json
> Looking for local package map at 
> /tmp/fakehome/.dub/packages/local-packages.json
> Try to load local package map at 
> /tmp/fakehome/.dub/packages/local-packages.json
>   Version selection for dependency mustache-d (mustache-d) of 
> appstream-generator is missing.
>   Missing dependency mustache-d ~>0.1.1 of appstream-generator
> Checking for missing dependencies.
> Search for versions of mustache-d (0 package suppliers)
> Return for mustache-d: [0.1.1]
> Refreshing local packages (refresh existing: false)...
> Looking for local package map at /var/lib/dub/packages/local-packages.json
> Looking for local package map at 
> /tmp/fakehome/.dub/packages/local-packages.json
> Try to load local package map at 
> /tmp/fakehome/.dub/packages/local-packages.json
>   Found dependency mustache-d 0.1.1
> Checking for upgrades.
> Search for versions of mustache-d (0 package suppliers)
> Return for mustache-d: [0.1.1]
> Caching upgrade results...
> Generating using build
> Generate target appstream-generator (executable /<>/build 
> appstream-generator)
> Generate target mustache-d (staticLibrary /tmp/dub-repo/mustache-d mustache-d)
> Using custom build type 'debug'.
> Using custom build type 'debug'.
> Performing "debug" build using gdc for x86_64.
> Target 
> '/tmp/dub-repo/mustache-d/.dub/build/library-debug-linux.posix-x86_64-gdc_2068-61DE1B2339FCB68F4AB34296DBC6D5F4/libmustache-d.a'
>  doesn't exist, need rebuild.
> mustache-d 0.1.1: building configuration "library"...
> gdc -c -o 
> ../../../tmp/dub-repo/mustache-d/.dub/build/library-debug-linux.posix-x86_64-gdc_2068-61DE1B2339FCB68F4AB34296DBC6D5F4/libmustache-d.a
>  -fdebug -g -Werror -Wall -Wno-deprecated -fversion=Have_mustache_d 
> -I../../../tmp/dub-repo/mustache-d/src 
> ../../../tmp/dub-repo/mustache-d/src/mustache.d
> Copying target from 
> /tmp/dub-repo/mustache-d/.dub/build/library-debug-linux.posix-x86_64-gdc_2068-61DE1B2339FCB68F4AB34296DBC6D5F4/libmustache-d.a
>  to /tmp/dub-repo/musta

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 835767 gdc-6
Bug #835767 [src:dub] dub: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): undefined reference 
to symbol 'dlclose@@GLIBC_2.2.5'
Bug reassigned from package 'src:dub' to 'gdc-6'.
No longer marked as found in versions dub/1.0.0-1.
Ignoring request to alter fixed versions of bug #835767 to the same values 
previously set
> forcemerge 835255 835767
Bug #835255 {Done: Matthias Klose } [gdc-6] gdc-6: 
std.datetime: undefined reference to dlopen/dlsym/dlclose
Bug #835255 {Done: Matthias Klose } [gdc-6] gdc-6: 
std.datetime: undefined reference to dlopen/dlsym/dlclose
Added tag(s) sid and stretch.
Bug #835767 [gdc-6] dub: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): undefined reference 
to symbol 'dlclose@@GLIBC_2.2.5'
835281 was blocked by: 835255
835281 was not blocking any bugs.
Added blocking bug(s) of 835281: 835767
835727 was blocked by: 835255
835727 was not blocking any bugs.
Added blocking bug(s) of 835727: 835767
Marked Bug as done
Marked as fixed in versions gcc-6/6.2.0-3.
Marked as found in versions gcc-6/6.2.0-1.
Merged 835255 835767
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
835255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835255
835281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835281
835727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835727
835767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package gcc-5

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package gcc-5
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #800543 (http://bugs.debian.org/800543)
> # Bug title: gcc-5: miscompilation at -O3
> #  * http://gcc.gnu.org/PR68436
> #  * remote status changed: UNCONFIRMED -> RESOLVED
> #  * remote resolution changed: (?) -> INVALID
> #  * closed upstream
> tags 800543 + fixed-upstream
Bug #800543 [gcc-5] gcc-5: miscompilation at -O3
Added tag(s) fixed-upstream.
> usertags 800543 - status-UNCONFIRMED
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 800543 + status-RESOLVED resolution-INVALID
There were no usertags set.
Usertags are now: status-RESOLVED resolution-INVALID.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
800543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#833829: libgcc-6-dev: Missing crtfastmath.o on kfreebsd-*

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libgcc-6-dev: Missing crtfastmath.o on kfreebsd-*
Bug #833829 [libgcc-6-dev] libgcc-6-dev: Missing crtfastmath.o
Changed Bug title to 'libgcc-6-dev: Missing crtfastmath.o on kfreebsd-*' from 
'libgcc-6-dev: Missing crtfastmath.o'.
> affects -1 + src:vlc
Bug #833829 [libgcc-6-dev] libgcc-6-dev: Missing crtfastmath.o on kfreebsd-*
Added indication that 833829 affects src:vlc

-- 
833829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Please update gcc-doc to stretch’s compiler now, kthx!

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 794778 important
Bug #794778 [gcc-doc] Should update to gcc-6-doc packages
Severity set to 'important' from 'normal'
> forcemerge 833505 794778
Bug #833505 [gcc-doc] gcc-doc: please update to gcc-6-doc
Bug #794778 [gcc-doc] Should update to gcc-6-doc packages
Merged 794778 833505
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
794778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794778
833505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 825320

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 825320 + patch
Bug #825320 [src:gcc-doc-defaults] gcc-doc-defaults: FTBFS in sid: error in 
'Version' field string '5:': nothing after colon in version number
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
825320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 833829

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 833829 + src:mpd
Bug #833829 [libgcc-6-dev] libgcc-6-dev: Missing crtfastmath.o on kfreebsd-*
Added indication that 833829 affects src:mpd
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#835148: marked as done (gcc-6: please enable PIE hardening flags by default on amd64 ppc64el and s390x)

[Debian Bug Tracking System]

Your message dated Fri, 16 Sep 2016 10:16:42 +
with message-id 
and subject line Bug#835148: fixed in open-coarrays 1.7.0-2
has caused the Debian Bug report #835148,
regarding gcc-6: please enable PIE hardening flags by default on amd64 ppc64el 
and s390x
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 ow...@bugs.debian.org
immediately.)


-- 
835148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-6
Version: 6.1.1-12
Severity: wishlist
Tags: patch

Dear Matthias,

As a continuation of the discussions [1][2] on debian-devel I'm
attaching the simple patch that implements enabling the PIE
hardening flags for a subset of the architectures.

I'm open to changing the subset, it matches the set selected in Ubuntu
as a start, but porters may have different preferences [2].

I'm continuing with a full archive rebuild to see the amount of packages
to be updated for the change in the default flags.

The same patch applies to gcc-5, too, if it does not get removed
from the archive before the patch is accepted for gcc-6.

Cheers,
Balint

[1] https://lists.debian.org/debian-devel/2016/05/msg00228.html
[2] https://lists.debian.org/debian-devel/2016/08/msg00324.html

>From 096fba7df4a9d699015c5f5457be7fdd21cde33e Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Sun, 3 Jul 2016 21:09:36 +0200
Subject: [PATCH] Enable PIE on Debian for amd64, ppc64el and s390x

---
 debian/rules.defs | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/debian/rules.defs b/debian/rules.defs
index 47a067d..443eba4 100644
--- a/debian/rules.defs
+++ b/debian/rules.defs
@@ -1222,16 +1222,19 @@ endif
 
 # pie by default 
 with_pie :=
+pie_archs := amd64 ppc64el s390x
 ifeq ($(distribution),Ubuntu)
   ifeq (,$(filter $(distrelease),lucid precise trusty utopic vivid wily))
 pie_archs = s390x
+  else
+pie_archs =
   endif
   ifeq (,$(filter $(distrelease),lucid precise trusty utopic vivid wily xenial))
 pie_archs += amd64 ppc64el
   endif
-  ifneq (,$(filter $(DEB_TARGET_ARCH),$(pie_archs)))
-with_pie := yes
-  endif
+endif
+ifneq (,$(filter $(DEB_TARGET_ARCH),$(pie_archs)))
+  with_pie := yes
 endif
 
 # gold 
-- 
2.1.4

--- End Message ---
--- Begin Message ---
Source: open-coarrays
Source-Version: 1.7.0-2

We believe that the bug you reported is fixed in the latest version of
open-coarrays, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated open-coarrays 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Sep 2016 16:04:04 +0100
Source: open-coarrays
Binary: libcoarrays-dev libcoarrays0d open-coarrays-bin
Architecture: source amd64
Version: 1.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libcoarrays-dev - Co-Array Fortran libraries for gfortran - development files
 libcoarrays0d - Co-Array Fortran libraries for gfortran
 open-coarrays-bin - Executables for running Co-Array Fortran programs
Closes: 835148
Changes:
 open-coarrays (1.7.0-2) unstable; urgency=medium
 .
   * Set debhelper dependency to >= 10.
   * Don't link against static lib in navier_stokes test, breaks -fPIE,
 bindow. Closes: #835148
   * disable alpha, powerpc tests again. Still buggy.
Checksums-Sha1:
 c9c3da8177b6ecf292fb249395accace75bba37b 1939 open-coarrays_1.7.0-2.dsc
 72b830ba55cc25429cf8b0f405f800c876afc71a 6404 
open-coarrays_1.7.0-2.debian.tar.xz
 b962f42c575d249f6cce9f6796c77bd728321ce6 44484 
libcoarrays-dev_1.7.0-2_amd64.deb
 9a5f8a4fc79cff8fb80444502585586efaa140ce 47002 
libcoarrays0d-dbgsym_1.7.0-2_amd64.deb
 4959895910a5bce9eea40b7909a3413b3efa18a7 22214 libcoarrays0d_1.7.0-2_amd64.deb
 f997d387cfa5e9bd2153e425bfab08b0c30d10b4 7408 
open-coarrays-bin_1.7.0-2_amd64.deb
Checksums-Sha256:
 9bedfe7a692a4ca2864ab2d1e4d08cc3c49bc8f64ed58d9d2f1be1ba1cfca763 1939 
open-coarrays_1.7.0-2.dsc
 0ca9ab622346ba0c8c1d6ed04a9624dfc21fcd5d5639c1219

Processed (with 1 error): your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> repoen 835148
Unknown command or malformed arguments to command.
> notfixed 835148 open-coarrays/1.7.0-2
Bug #835148 {Done: Alastair McKinstry } [gcc-6] gcc-6: 
please enable PIE hardening flags by default on amd64 ppc64el and s390x
No longer marked as fixed in versions open-coarrays/1.7.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
835148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 835148
Bug #835148 {Done: Alastair McKinstry } [gcc-6] gcc-6: 
please enable PIE hardening flags by default on amd64 ppc64el and s390x
Bug reopened
Ignoring request to alter fixed versions of bug #835148 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
835148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#182360: marked as done ([Fixed in 5.2] GNAT.OS_Lib.Close ignores return value)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #182360,
regarding [Fixed in 5.2] GNAT.OS_Lib.Close ignores return value
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 ow...@bugs.debian.org
immediately.)


-- 
182360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=182360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat
Version: 3.14p-3
Severity: normal

GNAT.OS_Lib.Close is defined as:
   procedure Close (FD : File_Descriptor);
   pragma Import (C, Close, "close");

However the C function imported returns an int which is 0 on success and
-1 if an error has occurred. Since GNAT.OS_Lib.Close ignores this return value
any error will not be detected.

According to the Linux Man page close(2):
   Not checking the return value of close  is  a  common  but
   nevertheless   serious  programming  error.   File  system
   implementations which use techniques  as  ``write-behind''
   to  increase  performance may lead to write(2) succeeding,
   although the data has not been  written  yet.   The  error
   status  may be reported at a later write operation, but it
   is guaranteed to be reported on  closing  the  file.   Not
   checking  the  return value when closing the file may lead
   to silent loss of data.  This can especially  be  observed
   with NFS and disk quotas.

I would have expected that if the C close call returned -1 then 
GNAT.OS_Lib.Close would either raise an exception or return an error
(either as an out parameter or as a return value).

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux maxwell 2.4.20 #1 Sat Jan 18 13:48:50 GMT 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages gnat depends on:
ii  libc6 2.2.5-11.2 GNU C Library: Shared libraries an


--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#611248: marked as done ([armel] unexpected symbols added for shared library)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #611248,
regarding [armel] unexpected symbols added for shared library
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 ow...@bugs.debian.org
immediately.)


-- 
611248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.4
Version: 4.4.5-3
Severity: normal

On the way to have polyorb on armel architecture I have some problems already 
related in [1].
I have tracked the problem down to the generation of libpolyorb-giop.so.
The shared lib generation include a -lgnarl-4.4 in the command line.
If I remove it the symbol problem is solved for this library.
If I run exactly the same command on amd64 architecture with the -lgnarl-4.4 
option I get a libpolyorb-giop.so without the symbols.
May be it's a problem in ld, but at this level I don't know how to distinguish 
between gnat and ld.

[1] http://lists.debian.org/debian-ada/2011/01/msg0.html

-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armel (armv5tel)

Kernel: Linux 2.6.32-5-kirkwood
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnat-4.4 depends on:
ii  gcc-4.4   4.4.5-8The GNU C compiler
ii  gnat-4.4-base 4.4.5-3The GNU Compiler Collection (gnat 
ii  libc6 2.11.2-9   Embedded GNU C Library: Shared lib
ii  libc6-dev 2.11.2-9   Embedded GNU C Library: Developmen
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libgmp3c2 2:4.3.2+dfsg-1 Multiprecision arithmetic library
ii  libgnat-4.4   4.4.5-3Runtime library for GNU Ada applic
ii  libgnatprj4.4 4.4.5-3GNU Ada Project Manager
ii  libgnatvsn4.4 4.4.5-3GNU Ada compiler version library
ii  libmpfr4  3.0.0-2multiple precision floating-point 

gnat-4.4 recommends no packages.

Versions of packages gnat-4.4 suggests:
pn  ada-reference-manual   (no description available)
pn  gnat-4.4-doc   (no description available)
pn  gnat-gps   (no description available)
pn  gprbuild   (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#569343: marked as done (OpenToken tests fail with AUnit dynamic library, but not with source)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #569343,
regarding OpenToken tests fail with AUnit dynamic library, but not with source
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 ow...@bugs.debian.org
immediately.)


-- 
569343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.4
Version: 4.4.3-1
Severity: normal

When OpenToken tests are linked with the AUnit dynamic library, the
tests fail in odd ways. However, when the OpenToken tests bypass the
AUnit dynamic library, and just include the AUnit sources in the
project, the OpenToken tests work properly.

Packages installed in an unstable chroot:

libaunit-dbg (2009-1)
libaunit4-dev (2009-1)
libaunit4 (2009-1)
gnat-4.4 (4.4.3-1)

This version of AUnit is not in the unstable distribution yet; get
aunit-gpl-2009-src.tar.gz from http://libre.adacore.com/libre/, debian
files from the www.ada-france.org mtn repository, branch org.debian.libaunit,
version 56a45e506ad847f93bc1231ad082a22b40cc1d33
stephen_leak...@stephe-leake.org 2010-01-25T00:07:01

Upstream OpenToken source from www.ada-france.org mtn repository,
branch org.opentoken, version 3ed79d3980cbd71e619d92cb2d340eab9288bc22
stephen_leak...@stephe-leake.org 2010-02-10T16:46:41

OpenToken is checked out as /home/Projects/opentoken/opentoken.main

To build with the AUnit sources:

stephe@Shevek$ cd /home/Projects/opentoken/opentoken.main/Build/linux_release
stephe@Shevek$ schroot -- gnatmake -P opentoken_test.gpr test_all_harness
stephe@Shevek$ schroot -- ./test_all_harness.exe
I: [sid chroot] Running command: “./test_all_harness.exe”


   Total Tests Run: 19

   Successful Tests: 19
  OpenToken.Recognizer.CSV_Field.Test : Nominal
  Lookahead_Test : Lookahead
  Lookahead_Test : Lookahead_Push_Back
  Lookahead_Test : Lookahead_Lexemes
  Lookahead_Test : Mismatched_Tokens
  Test_Accept_Index : Nominal
  Test_Backtrack : Enumerated_Lookahead
  Test_Backtrack : Sequence_Lookahead
  Test_Backtrack : Selection_Backtrack
  Test_Backtrack : Sequence_Backtrack
  Test_LR0_Kernels : Nominal
  Test_LR_Expecting : Nominal
  Test_List_Actions : List_Action
  Test_List_Stack : List_Stack
  test_multi_parse_lalr.adb : Nominal
  Test_Selection_Actions : Selection_Action
  Test_Sequence_Actions : Sequence_Action
  Test_Statement_Actions : Nominal
  Test_Token_Identifier_Real_String : Nominal

   Failed Assertions: 0


   Unexpected Errors: 0


To build with the AUnit dynamic library, use the attached project
file:

stephe@Shevek$ schroot -- gnatclean -P opentoken_test.gpr
stephe@Shevek$ schroot -- gnatmake -P opentoken_test_bug.gpr test_all_harness

stephe@Shevek$ schroot -- ./test_all_harness.exe
I: [sid chroot] Running command: “./test_all_harness.exe”


   Total Tests Run: 19

   Successful Tests: 19
  OpenToken.Recognizer.CSV_Field.Test : Nominal
  Lookahead_Test : Lookahead
  Lookahead_Test : Lookahead_Push_Back
  Lookahead_Test : Lookahead_Lexemes
  Lookahead_Test : Mismatched_Tokens
  Test_Accept_Index : Nominal
  Test_Backtrack : Enumerated_Lookahead
  Test_Backtrack : Sequence_Lookahead
  Test_Backtrack : Selection_Backtrack
  Test_Backtrack : Sequence_Backtrack
  Test_LR0_Kernels : Nominal
  Test_LR_Expecting : Nominal
  Test_List_Actions : List_Action
  Test_List_Stack : List_Stack
  test_multi_parse_lalr.adb : Nominal
  Test_Selection_Actions : Selection_Action
  Test_Sequence_Actions : Sequence_Action
  Test_Statement_Actions : Nominal
  Test_Token_Identifier_Real_String : Nominal

   Failed Assertions: 0


   Unexpected Errors: 0


Time:
Execution terminated by unhandled exception
Exception name: CONSTRAINT_ERROR
Message: 64-bit arithmetic overflow
Call stack traceback locations:
0xb7dfde42 0xb7dfecae 0xb7ef63ef 0x81055cf 0x804e99d 0xb7aabb53


Changing the OpenToken test source code slightly in an effort to
isolate the problem produces other more mysterious errors.

Removing various compiler options from AUnit and OpenToken did not help.

Earlier versions of libaunit-dev (1.03-3) and OpenToken (3.1a-1) did
not have this problem. AUnit has changed significantly; it may be that
some construct in the latest AUnit is triggering a bug in gnat or ld.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'uns

Bug#559447: marked as done (extends keyword in project files seems to be broken)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #559447,
regarding extends keyword in project files seems to be broken
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 ow...@bugs.debian.org
immediately.)


-- 
559447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.4
Version: 4.4.2-3
Severity: important


extends key word in gnat projects seems to have problems when
including other projects files.
A test case is joined to this bug report :
proj.gpr with xmlada.gpr
so input_sources.{ads|adb|ali|o} are known
proj_bis.gpr do a with of proj.gpr
so input_sources.{ads|adb|ali|o} are known
proj_ter.gpr extends proj.gpr
so input_sources.{ads|adb|ali|o} should be known
which is the case with gnat gpl 2009 and not with gnat-4.4

This bug was found when trying to use projects file in polyorb/gnat-4.4 
using extends. If the extends is removed then the code compile but then DSA
seems to be broken.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc64)

Kernel: Linux 2.6.30-2-powerpc64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnat-4.4 depends on:
ii  gcc-4.4   4.4.2-3The GNU C compiler
ii  gnat-4.4-base 4.4.2-3The GNU Compiler Collection (gnat 
ii  libc6 2.10.2-2   GNU C Library: Shared libraries
ii  libc6-dev 2.10.2-2   GNU C Library: Development Librari
ii  libgcc1   1:4.4.2-3  GCC support library
ii  libgmp3c2 2:4.3.1+dfsg-3 Multiprecision arithmetic library
ii  libgnat-4.4   4.4.2-3Runtime library for GNU Ada applic
ii  libgnatprj4.4 4.4.2-3GNU Ada Project Manager
ii  libgnatvsn4.4 4.4.2-3GNU Ada compiler version library
ii  libmpfr1ldbl  2.4.2-1multiple precision floating-point 

gnat-4.4 recommends no packages.

Versions of packages gnat-4.4 suggests:
pn  ada-reference-manual   (no description available)
pn  gnat-4.4-doc   (no description available)

-- no debconf information


test_extends_facility.tgz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#251265: marked as done ([Fixed in 5] Bug box in Case_Statement_to_gnu, at ada/gcc-interface/trans.c:2198, on legal Ada 83 program)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #251265,
regarding [Fixed in 5] Bug box in Case_Statement_to_gnu, at 
ada/gcc-interface/trans.c:2198, on legal Ada 83 program
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 ow...@bugs.debian.org
immediately.)


-- 
251265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat
Version: 3.15p-9
Severity: normal

pragma Ada_83;
procedure Test_106(x: integer) is
begin
   case x is
  when integer'last +1 => null;
  when 0   => null; -- line 5
  when others  => null;
   end case;
end Test_106;

$ gnatmake -q -O1 test_106
+===GNAT BUG DETECTED==+
| 3.15p  (20020523) (i486-pc-linux-gnu) Gigi abort, Code=316   |
| Error detected at test_106.adb:4:9   |
| Please submit bug report by email to rep...@gnat.com.|
| Use a subject line meaningful to you and us to track the bug.|
| (include your customer number #nnn in the subject line). |
| Include the entire contents of this bug box in the report.   |
| Include the exact gnatgcc or gnatmake command that you entered.  |
| Also include sources listed below in gnatchop format |
| (concatenated together with no headers between files).   |
| (use plain ASCII or MIME attachment, or FTP to your customer directory). |
| See README.GNATPRO for full info on procedure for submitting bugs.   |
+==+

Please include these source files with error report

test_106.adb

test_106.adb:5:25: warning: value not in range of type "Standard.Integer"
test_106.adb:5:25: warning: "Constraint_Error" will be raised at run time
compilation abandoned
gnatmake: "test_106.adb" compilation error


+===GNAT BUG DETECTED==+
| 3.4.0 (Debian) (i486-pc-linux-gnu) Gigi abort, Code=316  |
| Error detected at test_106.adb:4:9   |
| Please submit a bug report; see http://gcc.gnu.org/bugs.html.|
| Include the entire contents of this bug box in the report.   |
| Include the exact gcc-3.4 or gnatmake command that you entered.  |
| Also include sources listed below in gnatchop format |
| (concatenated together with no headers between files).   |
+==+

Please include these source files with error report
Note that list may not be accurate in some cases, 
so please double check that the problem can still 
be reproduced with the set of files listed.

test_106.adb

compilation abandoned
gnatmake: "test_106.adb" compilation error



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8

Versions of packages gnat depends on:
ii  libc6   2.3.2.ds1-12 GNU C Library: Shared libraries an
ii  libgnat-3.15p-1 3.15p-9  The GNU Ada 95 compiler runtime li

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#247564: marked as done ([Fixed in 5] Bug box on legal program in gnat_to_gnu_entity, at ada/gcc-interface/decl.c)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #247564,
regarding [Fixed in 5] Bug box on legal program in gnat_to_gnu_entity, at 
ada/gcc-interface/decl.c
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 ow...@bugs.debian.org
immediately.)


-- 
247564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat
Version: 3.15p-9
Severity: normal

procedure Test_70 is

   package pak2 is
  type t2(b2: boolean) is private;
   private
  type t2(b2: boolean) is null record;
   end pak2;

   package pak1 is
  type T1(b1 : boolean) is private;
   private
  type T1(b1 : boolean) is new pak2.t2(b1);
   end pak1;

   x: pak1.t1(false);
   b: boolean;
begin
   b := x.b1;
end Test_70;


+===GNAT BUG DETECTED==+
| 3.15p  (20020523) (i486-pc-linux-gnu) Gigi abort, Code=103   |
| Error detected at test_70.adb:18:9   |
| Please submit bug report by email to rep...@gnat.com.|
| Use a subject line meaningful to you and us to track the bug.|
| (include your customer number #nnn in the subject line). |
| Include the entire contents of this bug box in the report.   |
| Include the exact gnatgcc or gnatmake command that you entered.  |
| Also include sources listed below in gnatchop format |
| (concatenated together with no headers between files).   |
| (use plain ASCII or MIME attachment, or FTP to your customer directory). |
| See README.GNATPRO for full info on procedure for submitting bugs.   |
+==+

Please include these source files with error report

test_70.adb

compilation abandoned
gnatmake: "test_70.adb" compilation error




+===GNAT BUG DETECTED==+
| 3.15p  (20020523) (i686-pc-linux-gnu) Gigi abort, Code=103   |
| Error detected at test69.ada:18:9|
| Please submit bug report by email to rep...@gnat.com.|
| Use a subject line meaningful to you and us to track the bug.|
| (include your customer number #nnn in the subject line). |
| Include the entire contents of this bug box in the report.   |
| Include the exact gcc or gnatmake command that you entered.  |
| Also include sources listed below in gnatchop format |
| (concatenated together with no headers between files).   |
| (use plain ASCII or MIME attachment, or FTP to your customer directory). |
| See README.GNATPRO for full info on procedure for submitting bugs.   |
+==+

+===GNAT BUG DETECTED==+
| Pro 5.01a (20030718) (i686-pc-linux-gnu) Gigi abort, Code=103|
| Error detected at test69.ada:18:9|
| Please submit bug report by email to rep...@gnat.com.|
| Use a subject line meaningful to you and us to track the bug.|
| (include your customer number #nnn in the subject line). |
| Include the entire contents of this bug box in the report.   |
| Include the exact gcc or gnatmake command that you entered.  |
| Also include sources listed below in gnatchop format |
| (concatenated together with no headers between files).   |
| (use plain ASCII or MIME attachment, or FTP to your customer directory). |
| See README.GNATPRO for full info on procedure for submitting bugs.   |
+==+




-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.25-1-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8

Versions of packages gnat depends on:
ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libgnat-3.15p-1 3.15p-9  The GNU Ada 95 compiler runtime li

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 has just been removed fro

Bug#746689: marked as done (libgnatvsn should have a proper configure.ac and Makefile.in)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #746689,
regarding libgnatvsn should have a proper configure.ac and Makefile.in
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 ow...@bugs.debian.org
immediately.)


-- 
746689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.9

Please use some proper configury in libgnatvsn, especially honoring  CC, CFLAGS
set by the toplevel Makefile.
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#812587: marked as done (gnat: Fail to reconize types with an unrejected static size attribute as compile time known size type.)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #812587,
regarding gnat: Fail to reconize types with an unrejected static size attribute 
as compile time known size type.
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 ow...@bugs.debian.org
immediately.)


-- 
812587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat
Version: 4.9
Severity: normal
Tags: upstream

Dear Maintainer,

As said in the bug title gnat fail to reconize some compile time known size
type as it in some circumstances.

Please see below a minimal test case striped down form a real case :

procedure Foo is

   type Unbiased_T is range 0 .. 4
 with Size => 3;

   pragma Warnings
 (Off, "size clause forces biased representation for ""Biased_T""");

   type Biased_T is range 1 .. 4
 with Size => 2;

   pragma Warnings
 (On,  "size clause forces biased representation for ""Biased_T""");

   type Biased_Or_Unbiased_T (Biased : Boolean) is
  record
 case Biased is
when True  => Biased_Value   : Biased_T;
when False => Unbiased_Value : Unbiased_T;
 end case;
  end record
 with Unchecked_Union,
  Convention => Ada,
  Size   => 3;
   for Biased_Or_Unbiased_T use
  record
 Biased_Value   at 0 range 1 .. 2;
 Unbiased_Value at 0 range 0 .. 2;
  end record;

   type Hardware_Register_T
 (Value_1_Is_Biased : Boolean;
  Value_2_Is_Biased : Boolean) is
  record
 Value_1 : Biased_Or_Unbiased_T (Value_2_Is_Biased);
 Value_2 : Biased_Or_Unbiased_T (Value_2_Is_Biased);
  end record
 with Size  => 8,
  Volatile;
   for Hardware_Register_T use
  record
 Value_1   at 0 range 0 .. 2;
 Value_2   at 0 range 3 .. 5;
 Value_1_Is_Biased at 0 range 6 .. 6;
 Value_2_Is_Biased at 0 range 7 .. 7;
  end record;

begin

   null;

end Foo;


When invoking gnatmake as this :

gnatmake foo.adb

I get this output :

gcc-4.9 -c foo.adb
foo.adb:38:11: size clause not allowed for variable length type
foo.adb:42:28: component clause not allowed for variable length component
foo.adb:43:28: component clause not allowed for variable length component
gnatmake: "foo.adb" compilation error 


But none of the types here are variable length.

By some little investigation I have found that all of the 3 reported errors
cames from the same place in the compiler code.

The function Size_Known_At_Compile_Time return False and should return True
in the file freeze.adb at line 2832 and line 5228.

I expected at least any type with a static unrejected size attribute or clause
to be considered having a Size_Known_At_Compile_Time.

The function Size_Known_At_Compile_Time itself defined in einfo.adb line 2892
just return a flag which seem to only be manipulated by the procedure
Set_Size_Known_At_Compile_Time also define in einfo.adb at line 5655.

I suspect a call to the procedure Set_Size_Known_At_Compile_Time should be
added somwhere in freese.adb when there is a size clause or attribute for a
type but there I am at my limit in my understanding of the compiler code.


I suspect this bug to be present in all architecture and I can at least
confirme it on gnat-4.9 for x86 and powerpc, gnat-4.6 on x86 and
avr-ada gnat-4.7.

In the hope this bug report will help.

Henri GEIST


-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnat depends on:
ii  gnat-4.9  4.9.2-1

Versions of packages gnat recommends:
ii  ada-reference-manual-2012  1:2012.2-3
ii  gnat-gps   5.3dfsg-1

gnat suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that w

Bug#818774: marked as done (gnat-4.9: non-standard gcc/g++ used for build (gcc-4.9))

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #818774,
regarding gnat-4.9: non-standard gcc/g++ used for build (gcc-4.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 ow...@bugs.debian.org
immediately.)


-- 
818774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.9
Version: 4.9.3-3
Severity: important
Tags: sid stretch
User: debian-gcc@lists.debian.org
Usertags: non-standard-compiler, gcc-4.9, gcc-4.9-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-5/g++-5.

Please keep this report open until the package uses the default
compiler version (or gcc-5) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.

The severity of this report is likely to be raised before the release,
so that the gcc-4.9 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#825621: marked as done (gnat-4.9: empty Build-Depends-Indep field)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #825621,
regarding gnat-4.9: empty Build-Depends-Indep field
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 ow...@bugs.debian.org
immediately.)


-- 
825621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.9
Version: 4.9.3-3
Severity: important

Hi,

In gnat-4.9's debian/control file there is an empty field:

Build-Depends-Indep:  

Is this intentional?  Perhaps it should not be there at all.
I can't see that this is prohibited by policy, but it seems to be a
problem for `apt-get build-dep ./` :

Note, using directory './' to get the build dependencies
Reading package lists...
E: Problem parsing dependency: Build-Depends-Indep
E: Unable to get build-dependency information for ./

(This could also be a bug in apt-get, or in the policy).

Thanks.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#780031: marked as done ([Fixed in 5] result attribute fails in postcondition of generic functions)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #780031,
regarding [Fixed in 5] result attribute fails in postcondition of generic 
functions
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 ow...@bugs.debian.org
immediately.)


-- 
780031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.9
Version: 4.9.1-4
Severity: minor
Tags: upstream

Hello.
The following source produces an error message.
generic_f.ads:2:48: "Result" attribute can only appear in postcondition of 
function
It compiles when "generic" or the postcondition is removed.

generic
function Generic_F return Integer
   with Post => Generic_F'Result = 0;

function Generic_F return Integer is
begin
   return 0;
end Generic_F;
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#748297: marked as done (the libgnatprj and libgnatvsn patches should be upstreamed or dropped)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #748297,
regarding the libgnatprj and libgnatvsn patches should be upstreamed or dropped
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 ow...@bugs.debian.org
immediately.)


-- 
748297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.9
Version: 4.9.0-1
Severity: important
Tags: sid jessie

Building the gnatprj and gnatvsn libraries is done with a rather hackish local
patch, which doesn't integrate at all with the current GCC packaging.  Worst
things are not using the just built toolchain for the package builds, not
existing ability to cross builds, and flaky architecture support.  I think these
patches are not in the shape to be included for the next debian release, so
pretty please update these and contact upstream to include those, probably only
enabling these with configure options.
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#830436: marked as done (gnat-4.9: FTBFS: b_gnatb.adb:86: undefined reference to `__gnat_runtime_finalize')

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #830436,
regarding gnat-4.9: FTBFS: b_gnatb.adb:86: undefined reference to 
`__gnat_runtime_finalize'
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 ow...@bugs.debian.org
immediately.)


-- 
830436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnat-4.9
Version: 4.9.3-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> x86_64-linux-gnu-g++ -g -DIN_GCC -fno-exceptions -fno-rtti 
> -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings 
> -Wcast-qual -Wno-format -Wmissing-format-attribute -pedantic -Wno-long-long 
> -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H 
> -static-libstdc++ -static-libgcc  -o gnatbind ada/b_gnatb.o ada/a-clrefi.o 
> ada/a-comlin.o ada/a-elchha.o ada/a-except.o ada/ada.o ada/adaint.o 
> ada/ali-util.o ada/ali.o ada/alloc.o ada/argv.o ada/aspects.o ada/atree.o 
> ada/bcheck.o ada/binde.o ada/binderr.o ada/bindgen.o ada/bindusg.o 
> ada/butil.o ada/casing.o ada/cio.o ada/csets.o ada/cstreams.o ada/debug.o 
> ada/einfo.o ada/elists.o ada/env.o ada/err_vars.o ada/errout.o ada/erroutc.o 
> ada/exit.o ada/final.o ada/fmap.o ada/fname-uf.o ada/fname.o ada/g-byorma.o 
> ada/g-hesora.o ada/g-htable.o ada/gnat.o ada/gnatbind.o ada/gnatvsn.o 
> ada/hostparm.o ada/init.o ada/initialize.o ada/interfac.o ada/krunch.o 
> ada/lib.o ada/link.o ada/namet.o ada/nlists.o ada/opt.o ada/osint-b.o 
> ada/osint.o ada/output.o ada/raise.o ada/restrict.o ada/rident.o 
> ada/s-addope.o ada/s-assert.o ada/s-carun8.o ada/s-casuti.o ada/s-conca2.o 
> ada/s-conca3.o ada/s-conca4.o ada/s-conca5.o ada/s-conca6.o ada/s-conca7.o 
> ada/s-conca8.o ada/s-conca9.o ada/s-crc32.o ada/s-crtl.o ada/s-excdeb.o 
> ada/s-except.o ada/s-exctab.o ada/s-htable.o ada/s-imenne.o ada/s-imgenu.o 
> ada/s-mastop.o ada/s-memory.o ada/s-os_lib.o ada/s-parame.o ada/s-restri.o 
> ada/s-secsta.o ada/s-soflin.o ada/s-sopco3.o ada/s-sopco4.o ada/s-sopco5.o 
> ada/s-stache.o ada/s-stalib.o ada/s-stoele.o ada/s-strhas.o ada/s-string.o 
> ada/s-strops.o ada/s-traent.o ada/s-unstyp.o ada/s-utf_32.o ada/s-wchcnv.o 
> ada/s-wchcon.o ada/s-wchjis.o ada/scans.o ada/scil_ll.o ada/scng.o 
> ada/sdefault.o ada/seh_init.o ada/sem_aux.o ada/sinfo.o ada/sinput-c.o 
> ada/sinput.o ada/snames.o ada/stand.o ada/stringt.o ada/style.o ada/styleg.o 
> ada/stylesw.o ada/switch-b.o ada/switch.o ada/system.o ada/table.o 
> ada/targext.o ada/targparm.o ada/tree_io.o ada/types.o ada/uintp.o 
> ada/uname.o ada/urealp.o ada/widechar.o ggc-none.o libcommon-target.a 
> libcommon.a ../libcpp/libcpp.a   ../libbacktrace/.libs/libbacktrace.a 
> ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a   -g
> /«PKGBUILDDIR»/build/./gcc/xgcc -B/«PKGBUILDDIR»/build/./gcc/ -dumpspecs > 
> tmp-specs
> mv tmp-specs specs
> : > tmp-libgcc.mvars
> echo GCC_CFLAGS = '-g -O2 -DIN_GCC-W -Wall -Wno-narrowing -Wwrite-strings 
> -Wcast-qual -Wno-format -Wstrict-prototypes -Wmissing-prototypes 
> -Wold-style-definition  -isystem ./include ' >> tmp-libgcc.mvars
> echo INHIBIT_LIBC_CFLAGS = '' >> tmp-libgcc.mvars
> echo TARGET_SYSTEM_ROOT = '/' >> tmp-libgcc.mvars
> mv tmp-libgcc.mvars libgcc.mvars
> if /«PKGBUILDDIR»/build/./gcc/xgcc -B/«PKGBUILDDIR»/build/./gcc/ 
> -print-sysroot-headers-suffix > /dev/null 2>&1; then \
>   set -e; for ml in `/«PKGBUILDDIR»/build/./gcc/xgcc 
> -B/«PKGBUILDDIR»/build/./gcc/ -print-multi-lib`; do \
> multi_dir=`echo ${ml} | sed -e 's/;.*$//'`; \
> flags=`echo ${ml} | sed -e 's/^[^;]*;//' -e 's/@/ -/g'`; \
> sfx=`/«PKGBUILDDIR»/build/./gcc/xgcc -B/«PKGBUILDDIR»/build/./gcc/ 
> ${flags} -print-sysroot-headers-suffix`; \
> if [ "${multi_dir}" = "." ]; \
>   then multi_dir=""; \
> else \
>   multi_dir=/${multi_dir}; \
> fi; \
> echo "${sfx};${multi_dir}"; \
>   done; \
> else \
>   echo ";"; \
> fi > tmp-fixinc_list
> /bin/bash ../../src/gcc/../move-if-change tmp-fixin

Bug#833677: marked as done (gnat-4.9: last call to the put procedure incorrectly appends a newline character to the string)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #833677,
regarding gnat-4.9: last call to the put procedure incorrectly appends a 
newline character to the string
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 ow...@bugs.debian.org
immediately.)


-- 
833677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.9
Version: 4.9.2-1
Severity: normal

Dear Maintainer,

I have a use case where I need an Ada program to emit a single string
to stdout _without_ a trailing newline character.  According to Ada
documentation I have read, the put procedure (as opposed to put_line) is the 
one to use for
this case.  Nevertheless, the trailing newline character is still emitted.

Here is example code to demonstrate this issue

irwin@raven> cat test_ada_eol.adb
with Ada.Text_IO; use Ada.Text_IO;

procedure test_ada_eol is
begin
put("Hello");
end test_ada_eol;

After compiling test_ada_eol.adb with gnatmake, execution of the result yields
the following (unexpected) result

irwin@raven> ./test_ada_eol |od -a
000   H   e   l   l   o  nl
006

where the trailing nl is unexpected.  If I duplicate that put call
in test_ada_eol.adb, the result is

irwin@raven> ./test_ada_eol |od -a
000   H   e   l   l   o   H   e   l   l   o  nl
013

i.e., the first put does not emit a trailing nl to stdout as expected
from the documentation of the put procedure, but the last call to put
(incorrectly) appends nl.

-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnat-4.9 depends on:
ii  gcc-4.94.9.2-10
ii  gnat-4.9-base  4.9.2-1
ii  libc6  2.19-18+deb8u4
ii  libc6-dev  2.19-18+deb8u4
ii  libcloog-isl4  0.18.2-1+b2
ii  libgcc11:4.9.2-10
ii  libgmp10   2:6.0.0+dfsg-6
ii  libgnat-4.94.9.2-1
ii  libgnatprj4.9  4.9.2-1
ii  libgnatvsn4.9  4.9.2-1
ii  libisl10   0.12.2-2
ii  libmpc31.0.2-1
ii  libmpfr4   3.1.2-2
ii  multiarch-support  2.19-18+deb8u4
ii  zlib1g 1:1.2.8.dfsg-2+b1

gnat-4.9 recommends no packages.

Versions of packages gnat-4.9 suggests:
ii  ada-reference-manual-2012  1:2012.2-3
ii  gnat-4.9-doc   4.9.1-3
pn  gnat-4.9-sjlj  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#783877: marked as done ([Fixed in 5] Bug box on raise in Dynamic_Predicate)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #783877,
regarding [Fixed in 5] Bug box on raise in Dynamic_Predicate
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 ow...@bugs.debian.org
immediately.)


-- 
783877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.9
Version: 4.9.2-1
Severity: normal

gcc-4.9 -c -gnata -gnato -fstack-check -gnat12 -gnatyO -gnatv -gnati1 -gnatf 
-gnatn array_subtypes.ads

GNAT 4.9.2
Copyright 1992-2014, Free Software Foundation, Inc.
+===GNAT BUG DETECTED==+
| 4.9.2 (x86_64-linux-gnu) GCC error:  |
| in save_gnu_tree, at ada/gcc-interface/utils.c:294   |
| Error detected at array_subtypes.ads:5:17|
| Please submit a bug report; see http://gcc.gnu.org/bugs.html.|
| Use a subject line meaningful to you and us to track the bug.|
| Include the entire contents of this bug box in the report.   |
| Include the exact gcc-4.9 or gnatmake command that you entered.  |
| Also include sources listed below in gnatchop format |
| (concatenated together with no headers between files).   |
+==+

Please include these source files with error report
Note that list may not be accurate in some cases,
so please double check that the problem can still
be reproduced with the set of files listed.
Consider also -gnatd.n switch (see debug.adb).

array_subtypes.ads


Compiling: array_subtypes.ads (source file time stamp: 2015-04-30 18:07:17)
 10 lines: No errors
compilation abandoned
gnatmake: "array_subtypes.ads" compilation error

package Array_Subtypes is
   subtype Digit_Character is Character range '0' .. '9';
   subtype Digit_String is String
 with Dynamic_Predicate
=> (for all C of Digit_String => C in Digit_Character
or else raise Constraint_Error
  with "'" & Digit_String & "' contains non-digit " &
   "characters.");
end Array_Subtypes;

The bug also exists in GNAT GPL 2014, but not in the internal Adacore
GNAT wavefront release.  (It has been reported to
.)

-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fo_FO.ISO-8859-1, LC_CTYPE=fo_FO.ISO-8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages gnat-4.9 depends on:
ii  gcc-4.94.9.2-10
ii  gnat-4.9-base  4.9.2-1
ii  libc6  2.19-18
ii  libc6-dev  2.19-18
ii  libcloog-isl4  0.18.2-1+b2
ii  libgcc11:4.9.2-10
ii  libgmp10   2:6.0.0+dfsg-6
ii  libgnat-4.94.9.2-1
ii  libgnatprj4.9  4.9.2-1
ii  libgnatvsn4.9  4.9.2-1
ii  libisl10   0.12.2-2
ii  libmpc31.0.2-1
ii  libmpfr4   3.1.2-2
ii  multiarch-support  2.19-18
ii  zlib1g 1:1.2.8.dfsg-2+b1

gnat-4.9 recommends no packages.

Versions of packages gnat-4.9 suggests:
ii  ada-reference-manual-2012  1:2012.2-3
ii  gnat-4.9-doc   4.9.1-3
pn  gnat-4.9-sjlj  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#748298: marked as done (please drop the sjlj support)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 09:54:11 +
with message-id 
and subject line Bug#838315: Removed package(s) from unstable
has caused the Debian Bug report #748298,
regarding please drop the sjlj support
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 ow...@bugs.debian.org
immediately.)


-- 
748298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-4.9
Version: 4.9.0-1
Severity: important
Tags: sid jessie

Building the gnat libraries for both the zcx and sjlj exception support is not
needed anymore for Debian, and the local patches are done in a rather hackish
way which prevents cross-building of the compiler.  Please drop these patches,
or bring these patches upstream.
--- End Message ---
--- Begin Message ---
Version: 4.9.4-3+rm

Dear submitter,

as the package gnat-4.9 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/838315

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#734973: marked as done (libcilkrts for kfreebsd and the Hurd fails to build)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #734973,
regarding libcilkrts for kfreebsd and the Hurd fails to build
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 ow...@bugs.debian.org
immediately.)


-- 
734973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Severity: important

Disabling libcilkrts for kfreebsd and the Hurd for now.
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#450746: marked as done (gcc: Generates extnernal references for static variable.)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #450746,
regarding gcc: Generates extnernal references for static variable.
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 ow...@bugs.debian.org
immediately.)


-- 
450746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.2
Version: 4.2.2-3

Hi,

This program:
static int foo();
int bar() { foo(); }

When being compiled generates a warning:
tst.c:1: warning: 'foo' used but never defined

And it actually creates an reference to an extneral symbol, just like
static wasn't there.

$ nm tst.o
 T bar
 U foo


Please turn this into an error.


Kurt



--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#727621: marked as done (armel: std::future appears to be broken?)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #727621,
regarding armel: std::future appears to be broken?
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 ow...@bugs.debian.org
immediately.)


-- 
727621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-4.8
Version: 4.8.1-10
Severity: normal

Hello, thank you for maintaining GCC.

When I tried to compile cupt 2.6.x in unstable/experimental, an armel
build (out of all) failed. This unfortunately blocks cupt's migration to
testing.

unstable, used g++ 4.8 - [1]
unstable, used g++ 4.6 - [2]
experimental, used g++ 4.6 - [3]

Errors were a bit different between 4.6 and 4.8, but both didn't like
something about std::future. Builds on other architectures, including
armhf, went fine.

[1]
https://buildd.debian.org/status/fetch.php?pkg=cupt&arch=armel&ver=2.6.3&stamp=1382566839
[2]
https://buildd.debian.org/status/fetch.php?pkg=cupt&arch=armel&ver=2.6.2&stamp=1381599864
[3]
https://buildd.debian.org/status/fetch.php?pkg=cupt&arch=armel&ver=2.6.1&stamp=1381587241


-- System Information:
Debian Release: 6.0.5
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages g++-4.8 depends on:
ii  gcc-4.84.8.1-10
ii  gcc-4.8-base   4.8.1-10
ii  libc6  2.17-3
ii  libcloog-isl4  0.18.0-2
ii  libgmp10   2:5.0.5+dfsg-2
ii  libisl10   0.11.2-1
ii  libmpc31.0.1-1
ii  libmpfr4   3.1.1-2
ii  libstdc++-4.8-dev  4.8.1-10
ii  zlib1g 1:1.2.7.dfsg-13

g++-4.8 recommends no packages.

Versions of packages g++-4.8 suggests:
pn  g++-4.8-multilib
pn  gcc-4.8-doc 
pn  libstdc++6-4.8-dbg  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#748024: marked as done (gcc-4.9-plugin-dev: gcc plugins can not build)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #748024,
regarding gcc-4.9-plugin-dev: gcc plugins can not build
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 ow...@bugs.debian.org
immediately.)


-- 
748024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9-plugin-dev
Version: 4.9.0-2
Severity: serious
Justification: Renders package unusable

Hello,

Some headers seem to be missing to make using plugins workable at all
with gcc-4.9:

$ cat test.cpp
#include 
#include 
#include 

int main(void) {
return 0;
}
$ g++-4.9 test.cpp -o test  -I$(g++-4.9 -print-file-name=plugin)/include
...
/usr/lib/gcc/x86_64-linux-gnu/4.9/plugin/include/gimple.h:276:22: error:
field ‘call_used’ has incomplete type ‘pt_solution’ struct pt_solution 
call_used;

struct pt_solution is nowhere to be found in the plugin headers.

Samuel

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gcc-4.9-plugin-dev depends on:
ii  gcc-4.9   4.9.0-2
ii  gcc-4.9-base  4.9.0-2
ii  libc6 2.18-5
ii  libgmp-dev2:6.0.0+dfsg-4

gcc-4.9-plugin-dev recommends no packages.

gcc-4.9-plugin-dev suggests no packages.

-- no debconf information

-- 
Samuel
"...[Linux's] capacity to talk via any medium except smoke signals."
(By Dr. Greg Wettstein, Roger Maris Cancer Center)
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#751812: marked as done (Incorrect fortify warning with -flto)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #751812,
regarding Incorrect fortify warning with -flto
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 ow...@bugs.debian.org
immediately.)


-- 
751812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gcc-4.9
Version: 4.9.0-6

$ cat t.c
#define _FORTIFY_SOURCE 2
#include 
#include 

long long size;

void execute(void) {
  unsigned char input[4096];
  size_t bytes = (size > (ssize_t)sizeof input
  ? sizeof input
  : size);
  size_t bytesRead = fread(input, 1, bytes, stdin);
}

int main(int argc, char **argv) {
  size = LLONG_MAX;
  execute();
  return 0;
}
$ gcc-4.9 -O2 t.c
$ gcc-4.9 -O2 -flto t.c
In function ‘__fread_alias’,
inlined from ‘execute’ at t.c:12:10:
/usr/include/i386-linux-gnu/bits/stdio2.h:290:2: warning: call to 
‘__fread_chk_warn’ declared with attribute warning: fread called with 
bigger size * nmemb than length of destination buffer

  return __fread_chk (__ptr, __bos0 (__ptr), __size, __n, __stream);
  ^


richard@deodand:~/src/vbig$ dpkg -l libc6-dev gcc-4.9
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  gcc-4.94.9.0-6  i386 GNU C compiler
ii  libc6-dev:i386 2.19-1   i386 Embedded GNU C Library: 
Developme


The relevant portion of stdio2.h is:

   266  extern size_t __fread_chk (void *__restrict __ptr, size_t __ptrlen,
   267 size_t __size, size_t __n,
   268 FILE *__restrict __stream) __wur;
   269  extern size_t __REDIRECT (__fread_alias,
   270(void *__restrict __ptr, size_t __size,
   271 size_t __n, FILE *__restrict __stream),
   272fread) __wur;
   273  extern size_t __REDIRECT (__fread_chk_warn,
   274(void *__restrict __ptr, size_t __ptrlen,
   275 size_t __size, size_t __n,
   276 FILE *__restrict __stream),
   277__fread_chk)
   278   __wur __warnattr ("fread called with bigger size * nmemb 
than length "

   279 "of destination buffer");
   280
   281  __fortify_function __wur size_t
   282  fread (void *__restrict __ptr, size_t __size, size_t __n,
   283 FILE *__restrict __stream)
   284  {
   285if (__bos0 (__ptr) != (size_t) -1)
   286  {
   287if (!__builtin_constant_p (__size)
   288|| !__builtin_constant_p (__n)
   289|| (__size | __n) >= (((size_t) 1) << (8 * sizeof 
(size_t) / 2)))
   290  return __fread_chk (__ptr, __bos0 (__ptr), __size, __n, 
__stream);

   291
   292if (__size * __n > __bos0 (__ptr))
   293  return __fread_chk_warn (__ptr, __bos0 (__ptr), __size, 
__n, __stream);

   294  }
   295return __fread_alias (__ptr, __size, __n, __stream);
   296  }

The warning attribute is attached to __fread_chk_warn (called line 293) 
but the warning is issued against line 290 where __fread_chk is called - 
so the compiler has got confused about these two functions?


ttfn/rjk
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#762005: marked as done (gcc-4.9: prototype subroutine (non-static) != functional subroutine (static))

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #762005,
regarding gcc-4.9: prototype subroutine (non-static) != functional subroutine 
(static)
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 ow...@bugs.debian.org
immediately.)


-- 
762005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.1-12
Severity: normal

Dear Maintainer,

   * What led up to the situation?
My program has interlocking subroutines. 
a() is called by any mouse click. Depending on state, it may call b(), which 
creates a subwindow (OpenGL)
Creation of a subwindow invokes c(), which associates mouse activity with that 
subwindow
A mouse click on the subwindow invokes c(), which calls a().
Accordingly, a prototype of a(); is placed before c(){...}, followed by 
b(){...}, followed by the actual implementation of a(){...}.
This construction results in an error message:
"error: static declaration of 'a()' follows non-static declaration void a(){"
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I changed the repository to "jessie" from "wheezy", and upgraded the gcc 
package. (no joy).
I placed the keyword "static" in the prototype declaration: "static void a();"
   * What was the outcome of this action?
an error message, "invalid storage class for function 'a'"
   * What outcome did you expect instead?
compile without error

This construction has compiled successfully on Debian stable amd64 for the past 
year.
Note to upstream: The use of the keyword "static" to indicate that the 
subroutine is local to
the file in which it is found is inconsistent with the meaning elsewhere in the 
C language;
i.e. "static" implies pesistent vs volatile. A more appropriate keyword would 
be "local".


-- System Information:
Debian Release: 7.6
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-4.9 depends on:
ii  binutils2.24.51.20140903-1
ii  cpp-4.9 4.9.1-12
ii  gcc-4.9-base4.9.1-12
ii  libc6   2.19-11
ii  libcloog-isl4   0.18.2-1
ii  libgcc-4.9-dev  4.9.1-12
ii  libgmp102:6.0.0+dfsg-6
ii  libisl100.12.2-2
ii  libmpc3 1.0.2-1
ii  libmpfr43.1.2-1
ii  zlib1g  1:1.2.7.dfsg-13

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-11

Versions of packages gcc-4.9 suggests:
ii  binutils [binutils-gold]  2.24.51.20140903-1
pn  gcc-4.9-doc   
pn  gcc-4.9-locales   
pn  gcc-4.9-multilib  
pn  libasan1-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 
pn  libvtv0-dbg   

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#762640: marked as done (gfortran-4.9: generates buggy assembler at -O2 on armhf)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #762640,
regarding gfortran-4.9: generates buggy assembler at -O2 on armhf
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 ow...@bugs.debian.org
immediately.)


-- 
762640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gfortran-4.9
Version: 4.9.1-15
Severity: important

nwchem FTBFS on armhf, see e.g.
https://buildd.debian.org/status/fetch.php?pkg=nwchem&arch=armhf&ver=6.3%2Br2-1&stamp=1410744209

|gfortran -c -g -O2 -ffast-math -fno-aggressive-loop-optimizations  -O2  
|   -ffast-math -Wuninitialized -I. -I../include -I./include
|   -I/«BUILDDIR»/nwchem-6.3+r2/src/include
|   -I/«BUILDDIR»/nwchem-6.3+r2/src/tools/install/include -DLINUX
|   -DGCC4 -DGCC46 -DGFORTRAN -DPARALLEL_DIAG -DMRCC_METHODS
|   tce_mrcc_energy.F
|/tmp/ccmB6kme.s: Assembler messages:
|/tmp/ccmB6kme.s:6881: Error: offset out of range
|/tmp/ccmB6kme.s:6885: Error: offset out of range
|make[5]: ***
|[/«BUILDDIR»/nwchem-6.3+r2/lib/LINUX/libtce.a(tce_mrcc_energy.o)]
|Error 1

This is a regression from earlier versions of gfortran-4.9, other arches
seem fine.

If -O2 is replaced with -O1, it builds fine.

The preprocessed source can be found here:

https://people.debian.org/~mbanck/tce_mrcc_energy.f

It should (not) build like this: "gfortran -O2 -c tce_mrcc_energy.f"

The assembler output for -O1 and -O2, respectively, can be found here:

https://people.debian.org/~mbanck/tce_mrcc_energy.s.ok
https://people.debian.org/~mbanck/tce_mrcc_energy.s.wrong


Michael
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#762238: marked as done (gcc-4.9: guile-2.0 fails to build with offset problem)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #762238,
regarding gcc-4.9: guile-2.0 fails to build with offset problem
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 ow...@bugs.debian.org
immediately.)


-- 
762238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gcc-4.9
Version: 4.9.1-14

I'm not sure this is a gcc bug, but currently on abel.debian.org, in a
sid chroot, guile-2.0 2.0.11+1-3 fails to build as depicted here:

  
https://buildd.debian.org/status/fetch.php?pkg=guile-2.0&arch=armel&ver=2.0.11%2B1-4&stamp=1411145211

After some testing, it looks like the problem may have been introduced
by the switch from 4.8 to 4.9.

You can likely ignore the the two rhdi errors -- those appear to be
quashed by adding "&" to the output register constraints in the relevant
guile inline asm (libguile/vm-i-scheme.c:365).

With regard to the offset error:

  vm.s:13691: Error: bad immediate value for offset (4096)

Here's the relevant vm.s temp file:



tmp-arm-vm.s.gz
Description: tmp-arm-vm.s.gz

Thanks, and let me know if I can help any further.
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#753134: marked as done (lto1: fatal error: LTO_tags out of range: Range is 0 to 368, value is 756)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #753134,
regarding lto1: fatal error: LTO_tags out of range: Range is 0 to 368, value is 
756
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 ow...@bugs.debian.org
immediately.)


-- 
753134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.0-6
Severity: normal

Dear Maintainer,

since 4.9, the simgrid package sometimes FTBFS with the following
error on various architectures:

 lto1: fatal error: LTO_tags out of range: Range is 0 to 368, value is 756

This may be related to the fact that we build with gcc-ar and
gcc-ranlib instead of ar and ranlib. We do that because we have a
static library factorizing some code between out test cases, and cmake
makes it uneasy to share the .o in another way.

The strange thing is that this bug does not seem to occur all time,
and appears on various architectures. Some builds leading to that bug:

https://buildd.debian.org/status/fetch.php?pkg=simgrid&arch=powerpc&ver=3.11.1-5&stamp=1403865151
https://buildd.debian.org/status/fetch.php?pkg=simgrid&arch=armhf&ver=3.11.1-5&stamp=1403865694

On armhf, it did build correctly 4 times before that failed build, for
versions 3.11.1-1 to 3.11.1-4. The changes between these version is
completely unrelated to armhf, I think.

On kfreebsd, it worked with LTO enabled here:
  
https://buildd.debian.org/status/fetch.php?pkg=simgrid&arch=kfreebsd-amd64&ver=3.11.1-5&stamp=1403865120
but failed here:
  
https://buildd.debian.org/status/fetch.php?pkg=simgrid&arch=kfreebsd-amd64&ver=3.11.1-2&stamp=1403119800
(versions in between were broken on kfreebsd because of our usage of
java, ignore them)

I tried to disable the parallel building of the simgrid package, in
vain. Do you guys have any idea about what's going wrong, please?

Thanks in advance,
Mt.

-- System Information:
Debian Release: jessie/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-4.9 depends on:
ii  binutils2.24.51.20140604-3
ii  cpp-4.9 4.9.0-6
ii  gcc-4.9-base4.9.0-6
ii  libc6   2.19-1
ii  libcloog-isl4   0.18.2-1
ii  libgcc-4.9-dev  4.9.0-6
ii  libgmp102:6.0.0+dfsg-4
ii  libisl100.12.2-1
ii  libmpc3 1.0.1-1
ii  libmpfr43.1.2-1
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-1

Versions of packages gcc-4.9 suggests:
ii  binutils [binutils-gold]  2.24.51.20140604-3
pn  gcc-4.9-doc   
pn  gcc-4.9-locales   
pn  gcc-4.9-multilib  
pn  libasan1-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 
pn  libvtv0-dbg   

-- no debconf information

-- 
Thou shalt foreswear, renounce, and abjure the vile heresy which claimeth
that ``All the world's a 386'', and have no commerce with the benighted
heathens who cling to this barbarous belief, that the days of thy program
may be long even though the days of thy current machine be short.
  -- Tenth commandment of the C programmer


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#764280: marked as done (g++-4.9: g++-4.9 ignore "pragma GCC diagnostic ..." directives)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #764280,
regarding g++-4.9: g++-4.9 ignore "pragma GCC diagnostic ..." directives
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 ow...@bugs.debian.org
immediately.)


-- 
764280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-4.7
Version: 4.7.1-7
Severity: normal

  Hi,

  Contrary to gcc, g++ ignore "#pragma GCC diagnostic ...".
Note that the GNU doc tell us that g++ support most of gcc pragma.
Moreover, g++ does not emit a warning about unknown pragma as it
does for typo.

Example:
vdanjean@eyak:/tmp$ cat toto.cpp 
#pragma GCC diagnostic ignored "-Wcpp"
#warning this is a warning
vdanjean@eyak:/tmp$ g++-4.7 -Wall -c toto.cpp
toto.cpp:2:2: warning: #warning this is a warning [-Wcpp]
vdanjean@eyak:/tmp$ gcc-4.7 --language=c -Wall -c toto.cpp
vdanjean@eyak:/tmp$ 

Example that shows that the previous pragma is recongnized but ignored
with various typo that make g++ emit other warnings:
vdanjean@eyak:/tmp$ cat titi.cpp 
#pragma GCC wrong-pragma ignored "-Wcpp"
#pragma GXX diagnostic ignored "-Wcpp"
#pragma GCC diagnostic ignored "-Wwrong-option"
#warning this is a warning
vdanjean@eyak:/tmp$ g++-4.7 -Wall -c titi.cpp 
titi.cpp:1:0: warning: ignoring #pragma GCC wrong [-Wunknown-pragmas]
titi.cpp:2:0: warning: ignoring #pragma GXX diagnostic [-Wunknown-pragmas]
titi.cpp:4:2: warning: #warning this is a warning [-Wcpp]
titi.cpp:3:32: warning: unknown option after ‘#pragma GCC diagnostic’ kind 
[-Wpragmas]
vdanjean@eyak:/tmp$ 

So "#pragma GCC diagnostic ignored "-Wcpp"" has been correctly recognized in
toto.cpp but ignored.

  Regards,
Vincent

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386 armel mipsel

Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages g++-4.7 depends on:
ii  gcc-4.7 4.7.1-7
ii  gcc-4.7-base4.7.1-7
ii  libc6   2.13-35
ii  libgmp102:5.0.5+dfsg-2
ii  libmpc2 0.9-4
ii  libmpfr43.1.0-5
ii  libstdc++6-4.7-dev  4.7.1-7
ii  zlib1g  1:1.2.7.dfsg-13

g++-4.7 recommends no packages.

Versions of packages g++-4.7 suggests:
ii  g++-4.7-multilib4.7.1-7
pn  gcc-4.7-doc 
pn  libstdc++6-4.7-dbg  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#759870: marked as done (gcc-4.9: Compiles zsh endlessly with -fstack-protector-strong on s390x)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #759870,
regarding gcc-4.9: Compiles zsh endlessly with -fstack-protector-strong on s390x
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 ow...@bugs.debian.org
immediately.)


-- 
759870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.1-9
Severity: serious
Affects: src:zsh

Dear GCC Maintainers,

since 2014-08-18 all zsh builds -- sid binNMUs as well as experimental
uploads -- fail on s390x upon the first gcc invocation by being killed
after 150 minutes of inactivity. Previous builds always took less than
15, sometimes just 5 minutes. See

  https://buildd.debian.org/status/logs.php?pkg=zsh&arch=s390x

One example:

  make[3]: Entering directory '/«PKGBUILDDIR»/obj/Src'
  gcc -c -I. -I../Src -I../../Src -I../../Src/Zle -I../../Src 
-D_FORTIFY_SOURCE=2  -DHAVE_CONFIG_H -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -g  -o builtin.o ../../Src/builtin.c
  E: Caught signal ‘Terminated’: terminating immediately
  make[3]: *** [builtin.o] Terminated
  make[2]: *** [modobjs] Terminated
  make[1]: *** [all] Terminated
  make: *** [build-arch] Terminated
  Makemod:231: recipe for target 'builtin.o' failed
  Makefile:451: recipe for target 'modobjs' failed
  Makefile:189: recipe for target 'all' failed
  debian/rules:48: recipe for target 'build-arch' failed
  Build killed with signal TERM after 150 minutes of inactivity

Waldi suspects some breakage related to the sigjmp_buf ABI issue. At
least zsh uses sigjmp_buf. Waldi also said on IRC he can reproduce the
issue.

 Kind regards, Axel
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#764732: marked as done (gcc-4.9: broken -O2 optimizations on armhf)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #764732,
regarding gcc-4.9: broken -O2 optimizations on armhf
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 ow...@bugs.debian.org
immediately.)


-- 
764732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.1-16
Severity: important

Hello,

  Found a FTBFS while trying to build unzip package in Debian/sid on armhf host.

gcc -c -g -O2 -fstack-protector-strong -Wall -D_FORTIFY_SOURCE=2 -I. 
-DACORN_FTYPE_NFS -DWILD_STOP_AT_DIR -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT 
-DUNICODE_WCHAR -DUTF8_MAYBE_NATIVE -DNO_LCHMOD -DDATE_FORMAT=DF_YMD 
-DUSE_BZIP2 -DIZ_HAVE_UXUIDGID -DNOMEMCPY -DNO_WORKING_ISPRINT inflate.c
gcc -c -g -O2 -fstack-protector-strong -Wall -D_FORTIFY_SOURCE=2 -I. 
-DACORN_FTYPE_NFS -DWILD_STOP_AT_DIR -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT 
-DUNICODE_WCHAR -DUTF8_MAYBE_NATIVE -DNO_LCHMOD -DDATE_FORMAT=DF_YMD 
-DUSE_BZIP2 -DIZ_HAVE_UXUIDGID -DNOMEMCPY -DNO_WORKING_ISPRINT list.c
gcc -c -g -O2 -fstack-protector-strong -Wall -D_FORTIFY_SOURCE=2 -I. 
-DACORN_FTYPE_NFS -DWILD_STOP_AT_DIR -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT 
-DUNICODE_WCHAR -DUTF8_MAYBE_NATIVE -DNO_LCHMOD -DDATE_FORMAT=DF_YMD 
-DUSE_BZIP2 -DIZ_HAVE_UXUIDGID -DNOMEMCPY -DNO_WORKING_ISPRINT match.c
gcc -c -g -O2 -fstack-protector-strong -Wall -D_FORTIFY_SOURCE=2 -I. 
-DACORN_FTYPE_NFS -DWILD_STOP_AT_DIR -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT 
-DUNICODE_WCHAR -DUTF8_MAYBE_NATIVE -DNO_LCHMOD -DDATE_FORMAT=DF_YMD 
-DUSE_BZIP2 -DIZ_HAVE_UXUIDGID -DNOMEMCPY -DNO_WORKING_ISPRINT process.c
process.c: In function 'wide_to_local_string':
process.c:2453:7: warning: variable 'state_dependent' set but not used 
[-Wunused-but-set-variable]
   int state_dependent;
  ^
  /tmp/cc0hC5mg.s: Assembler messages:
  /tmp/cc0hC5mg.s:898: Error: offset out of range
  /tmp/cc0hC5mg.s:899: Error: offset out of range
  make[1]: *** [process.o] Error 1
  unix/Makefile:234: recipe for target 'process.o' failed
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  make: *** [build] Error 2
  debian/rules:34: recipe for target 'build' failed
  dpkg-buildpackage: error: debian/rules build gave error exit status 2


After trying different toolchain versions, for binutils and gcc-4.9, it builds 
with -O1, but fails with -O2. So, apparently the bug is on the GCC optimizer.

I was about to file a bug upstream for that one, but I was unable to reproduce 
with gcc-snapshot, therefore I file it here for now.

Find attached testcase: process.i

Compile line to be able to reproduce:
gcc -c -g -O2 -fstack-protector-strong -Wall -D_FORTIFY_SOURCE=2 -I. 
-DACORN_FTYPE_NFS -DWILD_STOP_AT_DIR -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT 
-DUNICODE_WCHAR -DUTF8_MAYBE_NATIVE -DNO_LCHMOD -DDATE_FORMAT=DF_YMD 
-DUSE_BZIP2 -DIZ_HAVE_UXUIDGID -DNOMEMCPY -DNO_WORKING_ISPRINT process.i



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Foreign Architectures: armhf

Kernel: Linux 3.14-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-4.9 depends on:
ii  binutils2.24.51.20141001-1
ii  cpp-4.9 4.9.1-16
ii  gcc-4.9-base4.9.1-16
ii  libc6   2.19-11
ii  libcloog-isl4   0.18.2-1
ii  libgcc-4.9-dev  4.9.1-16
ii  libgmp102:6.0.0+dfsg-6
ii  libisl100.12.2-2
ii  libmpc3 1.0.2-1
ii  libmpfr43.1.2-1
ii  zlib1g  1:1.2.8.dfsg-2

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-11

Versions of packages gcc-4.9 suggests:
ii  gcc-4.9-doc   4.9.1-2
pn  gcc-4.9-locales   
ii  gcc-4.9-multilib  4.9.1-16
pn  libasan1-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information


process.i.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/83831

Bug#772436: marked as done (aarch64 optimization bug)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #772436,
regarding aarch64 optimization bug
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 ow...@bugs.debian.org
immediately.)


-- 
772436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.1-19
Severity: normal

I have a minimal reproducable test case in a git repo here:

https://github.com/erikd/gcc-aarch64-optimization-bug

which contails a test program which passes when run with
optimization flags "-O1" and fails with "-O1 -fschedule-insns".

Cloning that repo under aarch64 and doing:

CC=gcc-4.9 make clean check

compiles and runs the program with both sets of optimization
flags and displays success or failure. It does not hwoever
fail on aarch64 with gcc-4.8 or with gcc-snapshot, nor does
it fail with any version of GCC on any other architecture.

There is a usefule comment from Måns Rullgård on G+:

https://plus.google.com/u/0/+ErikdeCastroLopo/posts/F2BPxT7g1Gx

OK, it's a gcc bug. For some unfathomable reason, it chooses to
calculate "mask = ~0u >> (32 - numBits)" in a vector register by
means of left-shifting by -(32 - numBits). It then subtracts 
(bitPos & 7) from the negated value and uses this as the shift 
amount of a regular shift instruction in "mask <<= shift" which
is obviously nonsense.

This behaviour (and the bug) was introduced in rev 202020 (git
5674183), and reverting this commit makes things work again.

I believe the -fschedule-insns flag is a red herring. It probably 
merely stirs up the code in a way that makes the real bug trigger.

Older discussion about this problem here:

https://plus.google.com/u/0/+ThomasRuecker/posts/e9uxoUyk3Bk

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages gcc-4.9 depends on:
ii  binutils2.24.90.20141201-1
ii  cpp-4.9 4.9.2-5
ii  gcc-4.9-base4.9.2-5
ii  libc6   2.19-13
ii  libcloog-isl4   0.18.2-1+b2
ii  libgcc-4.9-dev  4.9.2-5
ii  libgmp102:6.0.0+dfsg-6
ii  libisl100.12.2-2+b2
ii  libmpc3 1.0.2-1+b2
ii  libmpfr43.1.2-1+b2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-13

Versions of packages gcc-4.9 suggests:
pn  gcc-4.9-doc  
pn  gcc-4.9-locales  
pn  libasan1-dbg 
pn  libatomic1-dbg   
pn  libcilkrts5-dbg  
pn  libgcc1-dbg  
pn  libgomp1-dbg 
pn  libitm1-dbg  
pn  liblsan0-dbg 
pn  libquadmath-dbg  
pn  libtsan0-dbg 
pn  libubsan0-dbg

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#755295: marked as done (GCC testsuite failures on the Hurd)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #755295,
regarding GCC testsuite failures on the Hurd
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 ow...@bugs.debian.org
immediately.)


-- 
755295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-4.9
Version: 4.9.1-1
Severity: important
User: debian-h...@lists.debian.org
Usertags: hurd, kfreebsd

gcc-4.9 4.9.1-1 still fails to build, but test results are already available in
the build log.  These don't look too good.

Please see
https://buildd.debian.org/status/fetch.php?pkg=gcc-4.9&arch=hurd-i386&ver=4.9.1-1&stamp=1405723348
and search for test-summary
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#764195: marked as done (gcc-4.9: problems with precompiled headers on arm64)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #764195,
regarding gcc-4.9: problems with precompiled headers on arm64
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 ow...@bugs.debian.org
immediately.)


-- 
764195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.1-16

There are a couple of Debian packages that failed to build on arm64
apparently because of problems with precompiled headers:

qtbase-opensource-src
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762702

aegisub
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764187

It's difficult to extract a small test case, and it's presumably
impossible to reproduce the problem with preprocessed source as GCC's
standard internal compiler error message suggests.
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#768265: marked as done (gcc-4.9: Please support i386 compilation on amd64 through multiarch)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #768265,
regarding gcc-4.9: Please support i386 compilation on amd64 through multiarch
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 ow...@bugs.debian.org
immediately.)


-- 
768265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.1-19
Severity: wishlist

Dear Maintainer,

I tried to compile a simple "Hello world" C program to a 32bit binary on
my amd64 system, using:

$ gcc -m32 test.c -o test

But this does not work:

/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.9/libgcc.a 
when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
/usr/bin/ld: skipping incompatible 
/usr/lib/gcc/x86_64-linux-gnu/4.9/libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: cannot find -lgcc_s
collect2: error: ld returned 1 exit status

I do have libgcc-4.9-dev:i386 installed, so both libgcc.a and libgcc_s.so are 
available as 32bit binaries.
It just doesn't find them. I tried guiding it with "-L", but that did not help.

Of course I could install gcc-multilib, but that will pull in 
libc6-dev-i386:amd64, duplicating what
I already have from libc6-dev:i386. That seems like a useless waste.

Kind regards
Ralf

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17.0+ (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-4.9 depends on:
ii  binutils2.24.90.20141023-1
ii  cpp-4.9 4.9.1-19
ii  gcc-4.9-base4.9.1-19
ii  libc6   2.19-12
ii  libcloog-isl4   0.18.2-1
ii  libgcc-4.9-dev  4.9.1-19
ii  libgmp102:6.0.0+dfsg-6
ii  libisl100.12.2-2
ii  libmpc3 1.0.2-1
ii  libmpfr43.1.2-1
ii  zlib1g  1:1.2.8.dfsg-2

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-12

Versions of packages gcc-4.9 suggests:
ii  gcc-4.9-doc   4.9.1-3
pn  gcc-4.9-locales   
pn  gcc-4.9-multilib  
pn  libasan1-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#766840: marked as done ([armhf] Illegal assembler code generated with -O2)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #766840,
regarding [armhf] Illegal assembler code generated with -O2
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 ow...@bugs.debian.org
immediately.)


-- 
766840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc
Version: 4:4.9.1-5

Hi,

If trying to compile the attached file on armhf with

gcc -O2 -c reg.c

one gets 

/tmp/ccuv9e3N.s: Assembler messages:
/tmp/ccuv9e3N.s:106: Error: registers may not be the same -- `str r2,[r2],#4'

A workaround is to use either -fno-expensive-optimizations or 
-fno-schedule-insns.

gcc -O1 -fexpensive-optimizations -fschedule-insns -c reg.c

shows the same error.

The file is a shortened version from one of my packages (starlink-ast) which 
always compiled nicely on armhf, started to fail with gcc-4.9.1 [1]. With 
gcc-4.8.4, the compilation succeeded [2]:

gcc -DHAVE_CONFIG_H -I. -D_FORTIFY_SOURCE=2 -I/usr/include/star -DTHREAD_SAFE 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c region.c  
-fPIC -DPIC -o .libs/libstarlink_ast_la-region.o
/tmp/ccJsRMs3.s: Assembler messages:
/tmp/ccJsRMs3.s:21403: Warning: base register written back, and overlaps one of 
transfer registers
/tmp/ccJsRMs3.s:28133: Error: registers may not be the same -- `str r3,[r3],#4'
/tmp/ccJsRMs3.s:28971: Warning: base register written back, and overlaps one of 
transfer registers

The warnings are on similar places as above, just with the floats replaced by 
doubles or long doubles.

Best regards

Ole

[1] 
https://buildd.debian.org/status/fetch.php?pkg=starlink-ast&arch=armhf&ver=8.0.2%2Bdfsg-1&stamp=1414223014
[2] 
https://buildd.debian.org/status/fetch.php?pkg=starlink-ast&arch=armhf&ver=8.0.0%2Bdfsg-2&stamp=1400237749

#include 

void *astFree();
void *astMalloc();
int astOK = 1;

int MaskF( int inside, int ndim, 
	   const int lbnd[], const int ubnd[], 
	   float in[], float val) { 

   void *used_region;
   float *c, *d, *tmp_out;
   double *lbndgd, *ubndgd;
   int *lbndg, *ubndg, idim, ipix, nax, nin, nout, npix, npixg, result = 0; 
   if ( !astOK ) return result; 
   lbndg = astMalloc( sizeof( int )*(size_t) ndim ); 
   ubndg = astMalloc( sizeof( int )*(size_t) ndim ); 
   lbndgd = astMalloc( sizeof( double )*(size_t) ndim ); 
   ubndgd = astMalloc( sizeof( double )*(size_t) ndim ); 
   npix = 1; 
   npixg = 1; 
   for ( idim = 0; idim < ndim; idim++ ) { 
 npix *= ubnd[ idim ] - lbnd[ idim ]; 
 npixg *= ubndg[ idim ] - lbndg[ idim ]; 
   } 
   if( npixg <= 0 ){ 
 if( astGetNegated( used_region )) { 
   c = in; 
   for( ipix = 0; ipix < npix; ipix++ ) *(c++) = val; 
 } 
   } else if( npixg > 0) { 
 if(astGetNegated( used_region )) { 
   tmp_out = astMalloc( sizeof( float )*(size_t) npix ); 
   if( tmp_out ) { 
	 c = tmp_out; 
   } 
 } 
 result += astResampleF( used_region, lbnd, ubnd, 
			 ubnd, lbndg, ubndg); 
   }
   return result; 
}
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#773065: marked as done (selecting target via dpkg-buildpackage --target-arch)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #773065,
regarding selecting target via dpkg-buildpackage --target-arch
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 ow...@bugs.debian.org
immediately.)


-- 
773065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-4.9
Version: 4.9.2-7
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
X-Debbugs-Cc: debian-cr...@lists.debian.orgj

Please allow selecting the target architecture using "dpkg-buildpackage
--target-arch" again. This ability was removed in 4.9.2-7 when #768167
was fixed.

I am attaching a diff that enables target selection via:
 * dpkg-buildpackage --target-arch
 * debian/target
 * DEB_GCC_TARGET

Please see below for the rationale for individual hunks.

Helmut

diff -u gcc-4.9-4.9.2/debian/rules.defs gcc-4.9-4.9.2/debian/rules.defs
--- gcc-4.9-4.9.2/debian/rules.defs
+++ gcc-4.9-4.9.2/debian/rules.defs
@@ -31,23 +31,7 @@
 # for rules.sonames
 vafilt_defined = 1
 
-dpkg_target_vars := $(shell (dpkg-architecture | grep -q DEB_TARGET) && echo 
yes)
-ifeq ($(dpkg_target_vars),yes)
-  DEB_TARGET_ARCH=
-  DEB_TARGET_ARCH_BITS=
-  DEB_TARGET_ARCH_CPU=
-  DEB_TARGET_ARCH_ENDIAN=
-  DEB_TARGET_ARCH_OS=
-  DEB_TARGET_GNU_CPU=
-  DEB_TARGET_GNU_SYSTEM=
-  DEB_TARGET_GNU_TYPE=
-  DEB_TARGET_MULTIARCH=
-endif
-
 DPKG_VARS  := $(shell dpkg-architecture)
-ifeq ($(dpkg_target_vars),yes)
-  DPKG_VARS:= $(filter-out DEB_TARGET_%, $(DPKG_VARS))
-endif
 DEB_BUILD_ARCH ?= $(call vafilt,$(DPKG_VARS),DEB_BUILD_ARCH)
 DEB_BUILD_GNU_TYPE ?= $(call vafilt,$(DPKG_VARS),DEB_BUILD_GNU_TYPE)
 DEB_BUILD_MULTIARCH?= $(call vafilt,$(DPKG_VARS),DEB_BUILD_MULTIARCH)

Explicitly clearing DEB_TARGET_ variables is not needed as they are set
later. Having them cleared prevents selection via dpkg-buildpackage
--target-arch. Furthermore, clearing DEB_TARGET_ assignments from
DPKG_VARS is not necessary, because those are never accessed using
vafilt.

@@ -97,7 +81,7 @@
 
 # ---
 # set target
-# - GNU triplet via DEB_TARGET_GNU_TYPE
+# - dpkg-buildpackage --target-arch (via DEB_TARGET_ARCH)
 # - Debian arch in debian/target
 # - Debian arch via DEB_GCC_TARGET or GCC_TARGET
 #
@@ -105,39 +89,35 @@
 ifdef GCC_TARGET
   DEB_GCC_TARGET := $(GCC_TARGET)
 endif
-ifdef DEB_TARGET_GNU_TYPE
-  TARGET_VARS := $(shell dpkg-architecture -f -t$(DEB_TARGET_GNU_TYPE) 
2>/dev/null)
-else
-  # allow debian/target to be used instead of DEB_GCC_TARGET - this was 
requested
-  # by toolchain-source maintainer
-  DEBIAN_TARGET_FILE := $(strip $(if $(wildcard debian/target),$(shell cat 
debian/target 2>/dev/null)))
-  ifndef DEB_TARGET_ARCH
-ifneq (,$(DEBIAN_TARGET_FILE))
-  DEB_TARGET_ARCH := $(DEBIAN_TARGET_FILE)
-else
-  ifdef DEB_GCC_TARGET
-DEB_TARGET_ARCH := $(DEB_GCC_TARGET)
-  else
-DEB_TARGET_ARCH := $(DEB_HOST_ARCH)
-  endif
+# since dpkg 1.17.14, DEB_TARGET_* default to DEB_HOST_*
+DEB_TARGET_ARCH ?= $(DEB_HOST_ARCH)
+# allow debian/target to be used instead of DEB_GCC_TARGET - this was requested
+# by toolchain-source maintainer
+DEBIAN_TARGET_FILE := $(strip $(if $(wildcard debian/target),$(shell cat 
debian/target 2>/dev/null)))
+# consider DEB_TARGET_* set, if it differs from DEB_HOST_*
+ifeq ($(DEB_TARGET_ARCH),$(DEB_HOST_ARCH))
+  ifneq (,$(DEBIAN_TARGET_FILE))
+DEB_TARGET_ARCH := $(DEBIAN_TARGET_FILE)
+  else
+ifdef DEB_GCC_TARGET
+  DEB_TARGET_ARCH := $(DEB_GCC_TARGET)
 endif
   endif

Rather than checking DEB_TARGET_GNU_TYPE, I check DEB_TARGET_ARCH here.
The reason for this is that the only way to determine whether a
DEB_TARGET_* variable was actually set is to compare it to the
DEB_HOST_* counterpart. But DEB_HOST_GNU_TYPE is munged for i386, so on
a i386 build system, DEB_TARGET_GNU_TYPE can differ from
DEB_HOST_GNU_TYPE without being set. Thus this patch does not examine
DEB_HOST_GNU_TYPE at all.

Not supporting DEB_TARGET_GNU_TYPE is not a regression in this patch, as
4.9.2-7 already removed that support. If it needs to be supported
anyway, the major alternative to this approach is to prefer
debian/target and DEB_GCC_TARGET over DEB_TARGET_GNU_TYPE and hope that
it doesn't break the native build on i386.

The order of preference implemented in this patch is:
 * dpkg-buildpackage --target-arch (via D

Bug#781060: marked as done (g++-4.9: Broken optimization when move-constructing from virtual subclass)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #781060,
regarding g++-4.9: Broken optimization when move-constructing from virtual 
subclass
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 ow...@bugs.debian.org
immediately.)


-- 
781060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-4.9
Version: 4.9.2-10

Using g++ 4.9.2-10 on amd64, the below program behaves differently
when compiled with -O2 vs. not. The non-optimized version is correct;
the program's output should be:

~A(): moved = true
~A(): moved = false

However, with the optimized version, the program incorrectly outputs:

~A(): moved = false
~A(): moved = false

I.e. the line `other.moved = true` has been elided, or perhaps written
to the wrong location in memory. In practice, given the typical use
cases for move constructors, this bug tends to cause double-frees and
use-after-frees. In praticular, this is breaking the Cap'n Proto
library, which I maintain.

The attached self-contained script will demonstrate the problem.

Both G++ 4.8.4-1 and Clang 3.5.0-10 produce the correct output.
Additionally, G++ "4.9.2 20150304 (prerelease)" on Arch Linux produces
the correct output, possibly suggesting that this bug is
Debian-specific. (You can test different compiler versions by passing
the compiler command to use as the script's first parameter. By
default it uses `g++`.)

-Kenton

===Program text===
#include 

class A {
public:
  bool moved = false;

  A() = default;
  A(A&& other) {
other.moved = true;
  }
  ~A() {
printf("~A(): moved = %s\n", moved ? "true" : "false");
  }
};
class B: virtual public A {};
class C: virtual public B {};
class D: public C {};

int main() {
  A a = D();
}
=

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages g++-4.9 depends on:
ii  gcc-4.94.9.2-10
ii  gcc-4.9-base   4.9.2-10
ii  libc6  2.19-15
ii  libcloog-isl4  0.18.2-1+b2
ii  libgmp10   2:6.0.0+dfsg-6
ii  libisl10   0.12.2-2
ii  libmpc31.0.2-1
ii  libmpfr4   3.1.2-2
ii  libstdc++-4.9-dev  4.9.2-10
ii  zlib1g 1:1.2.8.dfsg-2+b1

g++-4.9 recommends no packages.

Versions of packages g++-4.9 suggests:
ii  g++-4.9-multilib4.9.2-10
pn  gcc-4.9-doc 
pn  libstdc++6-4.9-dbg  

-- no debconf information


test-move-from-virtual-subclass.sh
Description: Bourne shell script
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#777275: marked as done (php5-cli: Odd compiled assembly causing mmap detection to sometimes fail)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #777275,
regarding php5-cli: Odd compiled assembly causing mmap detection to sometimes 
fail
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 ow...@bugs.debian.org
immediately.)


-- 
777275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-cli
Version: 5.6.5+dfsg-1
Severity: normal

Dear Maintainer,

I've noticed some weird assembly being generated in the following piece of 
code.  I've only noticed this in the Debian amd64 binary - DotDeb's version 
doesn't seem to have the issue.
I suspect that this may be related to a compiler issue.

>From main/streams/plain_wrapper.c:

switch (value) {
case PHP_STREAM_MMAP_SUPPORTED:
return fd == -1 ? 
PHP_STREAM_OPTION_RETURN_ERR : PHP_STREAM_OPTION_RETURN_OK;

case PHP_STREAM_MMAP_MAP_RANGE:
do_fstat(data, 1);

The above return statement (third line) seems to compile to the following:

  >x0x6a4740 cmp$0x,%r14d
  ; if (fd == -1)
   x0x6a4744 je 0x6a4632 
   ;   return -1
   x0x6a474a mov$0x1,%esi
  ;
   x0x6a474f mov%rbp,%rdi
  ;
   x0x6a4752 callq  0x6a4440   
  ; do_fstat(%rdi, 1)
   x0x6a4757 xor%eax,%eax
  ;
   x0x6a4759 cmpq   $0x40,0x60(%rbp) 
  ; %eax = -( *(%rbp+0x60) > 0x40 )
   x0x6a4761 setg   %al  
  ;
   x0x6a4764 neg%eax 
  ;
   x0x6a4766 jmpq   0x6a4538 
   ; return %eax

First bit looks okay, but I don't know what the rest is about.  DotDeb's binary 
seems to compile to the following:

  >x0x693f55 cmp$0x,%r13d
  ; if (fd == -1)
   x0x693f59 je 0x693ea8 
   ;   return -1
   x0x693f5f xor%ebx,%ebx
  ; %ebx = 0
   x0x693f61 jmpq   0x693de3 
; return %ebx

which makes a whole lot more sense.

I'm not sure what the "0x60(%rbp)" is referring to, but I've seen the 
comparison evaluate to true and false in various cases, sometimes causing mmap 
detection to fail.

I've only tested this with PHP 5.6.5 so I don't know what version it showed up 
in.

If you want a way to test it yourself, you can use the following PHP script:

# cat >t.php


Versions of packages php5-cli suggests:
pn  php-pear  

Versions of packages php5-common depends on:
ii  libc6   2.19-13
ii  lsof4.86+dfsg-1
ii  psmisc  22.19-1+deb7u1
ii  sed 4.2.1-10
ii  ucf 3.0025+nmu3

Versions of packages php5-common suggests:
pn  php5-user-cache  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#774543: marked as done (gcc-4.9: add DEB_CROSS_NO_BIARCH support)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #774543,
regarding gcc-4.9: add DEB_CROSS_NO_BIARCH support
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 ow...@bugs.debian.org
immediately.)


-- 
774543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-4.9
Version: 4.9.2-10

Please add DEB_CROSS_NO_BIARCH option,
so we can build it without biarch support if necessary.


-- 
YunQiang Su


0003-allow-no-biarch.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#774541: marked as done (gcc-4.9: remove override with_deps_on_target_arch_pkgs)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #774541,
regarding gcc-4.9: remove override with_deps_on_target_arch_pkgs
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 ow...@bugs.debian.org
immediately.)


-- 
774541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.2-10

Please remove

override with_deps_on_target_arch_pkgs :=

in debian/rules.defs

Which is not used any more.


-- 
YunQiang Su
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#777169: marked as done (FTBFS on sparc64: symbol errors)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #777169,
regarding FTBFS on sparc64: symbol errors
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 ow...@bugs.debian.org
immediately.)


-- 
777169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-4.9
Version: 4.9.1-17
User: helm...@debian.org
Usertags: rebootstrap

gcc-4.9 currently FTBFS on sparc64 due to symbol errors. While the last
two builds on sompek failed due to -ENOSPC the build of 4.9.1-17 shows
proper symbol diffs:

http://buildd.debian-ports.org/status/fetch.php?pkg=gcc-4.9&arch=sparc64&ver=4.9.1-17&stamp=1413678403

The very same issue is reproducible with 4.9.2-10 in a cross-build
setting:

https://jenkins.debian.net/job/rebootstrap_sparc64_gcc49/105/console

You can find the relevant excerpt from the native build at the end of
this mail.

Reporting during freeze without any expectation of having this fixed
before the jessie release.

Helmut

| dh_makeshlibs -plib32stdc++6 
| objdump: 
debian/lib32stdc++6/usr/share/gdb/auto-load/usr/lib32/libstdc++.so.6.0.20-gdb.py:
 File format not recognized
| dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
| dpkg-gensymbols: warning: debian/lib32stdc++6/DEBIAN/symbols doesn't match 
completely debian/lib32stdc++6.symbols.sparc64
| --- debian/lib32stdc++6.symbols.sparc64 (lib32stdc++6_4.9.1-17_sparc64)
| +++ dpkg-gensymbolsEGATZT 2014-10-19 00:24:57.244023375 +
| @@ -452,9 +452,9 @@
|   _ZNKSt14error_category10equivalentERKSt10error_codei@GLIBCXX_3.4.11 4.4.0
|   _ZNKSt14error_category10equivalentEiRKSt15error_condition@GLIBCXX_3.4.11 
4.4.0
|   _ZNKSt14error_category23default_error_conditionEi@GLIBCXX_3.4.11 4.4.0
| - _ZNKSt15__exception_ptr13exception_ptr20__cxa_exception_typeEv@CXXABI_1.3.3 
4.4.0
| - _ZNKSt15__exception_ptr13exception_ptrcvMS0_FvvEEv@CXXABI_1.3.3 4.4.0
| - _ZNKSt15__exception_ptr13exception_ptrntEv@CXXABI_1.3.3 4.4.0
| +#MISSING: 4.9.1-17# 
_ZNKSt15__exception_ptr13exception_ptr20__cxa_exception_typeEv@CXXABI_1.3.3 
4.4.0
| +#MISSING: 4.9.1-17# 
_ZNKSt15__exception_ptr13exception_ptrcvMS0_FvvEEv@CXXABI_1.3.3 4.4.0
| +#MISSING: 4.9.1-17# _ZNKSt15__exception_ptr13exception_ptrntEv@CXXABI_1.3.3 
4.4.0
|   _ZNKSt15basic_streambufIcSt11char_traitsIcEE4gptrEv@GLIBCXX_3.4 4.1.1
|   _ZNKSt15basic_streambufIcSt11char_traitsIcEE4pptrEv@GLIBCXX_3.4 4.1.1
|   _ZNKSt15basic_streambufIcSt11char_traitsIcEE5ebackEv@GLIBCXX_3.4 4.1.1
| @@ -1570,17 +1570,17 @@
|   _ZNSt12system_errorD0Ev@GLIBCXX_3.4.11 4.4.0
|   _ZNSt12system_errorD1Ev@GLIBCXX_3.4.11 4.4.0
|   _ZNSt12system_errorD2Ev@GLIBCXX_3.4.11 4.4.0
| - _ZNSt13__future_base11_State_baseD0Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base11_State_baseD1Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base11_State_baseD2Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseC1Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseC2Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseD0Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseD1Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base12_Result_baseD2Ev@GLIBCXX_3.4.15 4.6
| - _ZNSt13__future_base19_Async_state_commonD0Ev@GLIBCXX_3.4.17 4.7.0~rc1
| - _ZNSt13__future_base19_Async_state_commonD1Ev@GLIBCXX_3.4.17 4.7.0~rc1
| - _ZNSt13__future_base19_Async_state_commonD2Ev@GLIBCXX_3.4.17 4.7.0~rc1
| +#MISSING: 4.9.1-17# _ZNSt13__future_base11_State_baseD0Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base11_State_baseD1Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base11_State_baseD2Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseC1Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseC2Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseD0Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseD1Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# _ZNSt13__future_base12_Result_baseD2Ev@GLIBCXX_3.4.15 4.6
| +#MISSING: 4.9.1-17# 
_ZNSt13__future_base19_Async_state_commonD0Ev@GLIBCXX_3.4.17 4.7.0~rc1
| +#MISSING: 4.9.1-17# 
_ZNSt13__future_base19_Async_state_commonD1Ev@GLIBCXX_3.4.17 4.7.0~rc1
| +#MISSING: 4.9.1-17# 
_ZNSt13__future_base19_Async_state_commonD2Ev@GLIBCXX_3.4.17 4.7.0~rc1
|   _ZNSt13bad_exceptionD0Ev@GLIBCXX_3.4 4.1.1
|   _ZNSt13bad_exceptionD1Ev@GLIBCXX_3.4 4.1.1
|   _ZNSt13bad_exceptionD2Ev@GLIBCXX_3.4 4.1.1
| @

Bug#774548: marked as done (gcc-4.9: add with_deps_on_target_arch_pkgs back and rename packages)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #774548,
regarding gcc-4.9: add with_deps_on_target_arch_pkgs back and rename packages
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 ow...@bugs.debian.org
immediately.)


-- 
774548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-4.9
Version: 4.9.2-10

This patch add with_deps_on_target_arch_pkgs back and when it is used,
rename the packages, like gcc-4.9, with pattern like
gcc-4.9- instead of gcc-4.9-

-- 
YunQiang Su


0001-reverted-removal-of-with_deps_on_target_arch_pkgs-in.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#785249: marked as done (gcc-4.9: test suite errors when memory overcommitting is turned off)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #785249,
regarding gcc-4.9: test suite errors when memory overcommitting is turned off
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 ow...@bugs.debian.org
immediately.)


-- 
785249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.2-10
Severity: normal

When I tried building gcc from sources (debuild -us -uc), I got a
number of errors like this:

FAIL: g++.dg/asan/interception-malloc-test-1.C  -O1  output pattern test, is 
==25380==ERROR: AddressSanitizer failed to allocate 0xdfff0001000 
(15392894357504) bytes at address 0x02008fff7000 (12)
==25380==ReserveShadowMemoryRange failed while trying to map 0xdfff0001000 
bytes. Perhaps you're using ulimit -v
, should match malloc call.*(
|
)[^
]*heap-use-after-free

In fact I wasn't using ulimit -v, but I had turned off memory
overcommitting (sysctl: vm.overcommit_memory=2). Obviously I have
less than 14 TB of RAM in my system. ;) After I turned it on, these
errors disappeared.

So I suggest:

- If possible, amend the test to use a more reasonable allocation.
  Not sure what it's actually testing, but I wonder what I can do
  with 14 TB (which is way short of the 64 bit address range) that
  it couldn't do with, say 6 GB (larger than 32 bit range, in case
  that matters). Otherwise:

- In the wording of the message, add "or have turned off memory
  overcommitting" as a possible reason.

- Verify [ `sysctl -n vm.overcommit_memory` -eq 0 ] early in the
  build process, so you don't get to see such errors after a long
  time building.

  Same for a ulimit check if there isn't one already.
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#784544: marked as done (gcc-4.9: 'cc --version' fails to identify cc as GCC)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #784544,
regarding gcc-4.9: 'cc --version' fails to identify cc as GCC
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 ow...@bugs.debian.org
immediately.)


-- 
784544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.2-10
Severity: normal

Dear Maintainer,

I would like (expect) to see "GCC" somewhere in the output of  'cc --version' 
when
it is in fact GCC that is providing the output:

tony@ohio:~$ cc --version
cc (Debian 4.9.2-10) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.



-- System Information:
Debian Release: 7.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gcc-4.9 depends on:
ii  binutils2.25-5
ii  cpp-4.9 4.9.2-10
ii  gcc-4.9-base4.9.2-10
ii  libc6   2.19-17
ii  libcloog-isl4   0.18.2-1+b2
ii  libgcc-4.9-dev  4.9.2-10
ii  libgmp102:5.0.5+dfsg-2
ii  libisl100.12.2-2
ii  libmpc3 1.0.3-1
ii  libmpfr43.1.2-3
ii  zlib1g  1:1.2.7.dfsg-13

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-17

Versions of packages gcc-4.9 suggests:
ii  gcc-4.9-doc   4.9.1-3
pn  gcc-4.9-locales   
pn  gcc-4.9-multilib  
pn  libasan1-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#782391: marked as done (g++-4.9: false-positive -Warray-bounds apprently due to wrong integer-range inference)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #782391,
regarding g++-4.9: false-positive -Warray-bounds apprently due to wrong 
integer-range inference
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 ow...@bugs.debian.org
immediately.)


-- 
782391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-4.9
Version: 4.9.2-10
Severity: normal

This warning can be seen while compiling skaakii-1.0.0 on several
architectures (looks like it includes some 64bit archs, plus sparc).
It does not appear with g++-4.8.

https://qa.debian.org/bls/packages/s/sjaakii.html
http://buildd.debian.org/status/fetch.php?pkg=sjaakii&arch=arm64&ver=1.0.0-1&stamp=1427152943

| SjaakII-1.0.0$ g++-4.8-g -O2 -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2  -O3 -finline -Wall -Wextra -Wno-unused 
-DSJAAKIIVERSION=\""1.0.0"\" -DDATADIR=\"/usr/share/games/sjaakii/\" 
-DHAVE_READLINE -I/work/yann/deb/sjaak/SjaakII-1.0.0/include 
-I/work/yann/deb/sjaak/SjaakII-1.0.0/obj-x86_64-linux-gnu/include-o 
obj-x86_64-linux-gnu/CMakeFiles/sjaakii.dir/src/xboard.o -c 
/work/yann/deb/sjaak/SjaakII-1.0.0/src/xboard.cc
| 
| SjaakII-1.0.0$ g++-4.9-g -O2 -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2  -O3 -finline -Wall -Wextra -Wno-unused 
-DSJAAKIIVERSION=\""1.0.0"\" -DDATADIR=\"/usr/share/games/sjaakii/\" 
-DHAVE_READLINE -I/work/yann/deb/sjaak/SjaakII-1.0.0/include 
-I/work/yann/deb/sjaak/SjaakII-1.0.0/obj-x86_64-linux-gnu/include-o 
obj-x86_64-linux-gnu/CMakeFiles/sjaakii.dir/src/xboard.o -c 
/work/yann/deb/sjaak/SjaakII-1.0.0/src/xboard.cc
| In file included from /work/yann/deb/sjaak/SjaakII-1.0.0/include/sjaak.h:4:0,
|  from /work/yann/deb/sjaak/SjaakII-1.0.0/src/xboard.cc:27:
| /work/yann/deb/sjaak/SjaakII-1.0.0/include/bitboard.h: In function ‘game_t* 
create_capablanca_game(const char*)’:
| /work/yann/deb/sjaak/SjaakII-1.0.0/include/bitboard.h:478:65: warning: array 
subscript is above array bounds [-Warray-bounds]
| board_between[square][attack] |= 
square_bitboards[pack_rank_file(n, file)];
|  ^
| /work/yann/deb/sjaak/SjaakII-1.0.0/include/bitboard.h:478:65: warning: array 
subscript is above array bounds [-Warray-bounds]
| /work/yann/deb/sjaak/SjaakII-1.0.0/include/bitboard.h:478:65: warning: array 
subscript is above array bounds [-Warray-bounds]
| 
| SjaakII-1.0.0$


Sorry for the lack of a minimal testcase.  What I've been able to
gather till now, is that we have 2 similar cases, with only one
triggering the warning:

473: for (int n=file;n<=unpack_file(attack);n++)
474:  board_between[square][attack] |= square_bitboards[pack_rank_file(rank, 
n)];

477: for (int n=rank;n<=unpack_rank(attack);n++)
478:  board_between[square][attack] |= square_bitboards[pack_rank_file(n, 
file)];

... and that the above-bound alert is linked to the infered values for
the loop range.  Whereas this ensures there is no warning:

| static inline int unpack_file(int packed)
| {
|return packed_file_rank[packed] & 0xf;
| }

... this does not:

| static inline int unpack_rank(int packed)
| {
|return packed_file_rank[packed] >> 4;
| }

Changing the latter to "return (packed_file_rank[packed] >> 4) &
0xf;", which should show no difference because packed_file_rank is an
uint8_t[], does indeed silence the warning, which seems to show that
the range of that return value was wrongly infered.


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages g++-4.9 depends on:
ii  gcc-4.94.9.2-10
ii  gcc-4.9-base   4.9.2-10
ii  libc6  2.19-17
ii  libcloog-isl4  0.18.2-1+b2
ii  libgmp10   2:6.0.0+dfsg-6
ii  libisl10   0.12.2-2
ii  libmpc31.0.2-1
ii  libmpfr4   3.1.2-2
ii  libstdc++-4.9-dev  4.9.2-10
ii  zlib1g 1:1.2.8.dfsg-2+b1

g++-4.9 recommends no packages.

Versions of packages g++-4.9 suggests:
ii  g++-4.9-m

Bug#810868: marked as done (threads: condition_variable or atomic causes _sometimes_ a deadlock)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #810868,
regarding threads: condition_variable or atomic causes _sometimes_ a deadlock
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 ow...@bugs.debian.org
immediately.)


-- 
810868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-4.9
Version: 4.9.2-10
Severity: normal

Dear Maintainer,

there is a mysterious bug in g++ or its libraries.
The bug happens when one compiles and executes the following test code multiple
times:
sometimes the executable just hangs, ie. a deadlock happens.
I think the error lies not in the test code, but in the g++ libraries or even
in g++ itself.

/*
test.cpp

2016-01-13-We
Author: U.Mutlu

condition variable example (but is [sometimes] buggy)

Code adapted from the example at [1]

Question:
  How to fix this code?
  --> it could be a low-level issue, ie. compiler-, stdlibrary-, or pthread-
issue

What-it-does:
  10 threads race for a job. The main thread supplies the job.
  One of the threads takes the job and processes it.
  This is repeated 1 times.
  BUT: sometimes the pgm freezes (ie. a deadlock bug happens) --> see below

Compile:
  g++ -Wall -O2 -std=gnu++11 test.cpp -lpthread

Run:
  ./a.out
  repeat multiple times (up to 10 times should be ok for the runtime bug to
show up)

Symptoms of the bug:
  sometimes pgm lands in an endless-loop! ie. deadlock happens --> pgm not
finishing

Test environment:
  - g++ --version
g++ (Debian 4.9.2-10) 4.9.2

  - uname -a
Linux my 4.2.0-0.bpo.1-amd64 #1 SMP Debian 4.2.6-3~bpo8+2 (2015-12-14)
x86_64 GNU/Linux

  - dpkg -l | grep -i pthread
ii libpthread-stubs0-dev:amd64  0.3-4  amd64 pthread stubs not provided by
native libc, development files

See also:
  [1] http://www.cplusplus.com/reference/condition_variable/condition_variable/
  [2] http://en.cppreference.com/w/cpp/thread/condition_variable
*/

#include 
#include 
#include 
#include 
#include 
#include 
#include 

using namespace std;

mutexmtx;
condition_variable cv;
atomic fReady;  // init done in main
atomic fQuit;   // init done in main
atomic fThreadsOk;  // init done in main

void threadfunc(int id)
  {
/*
Any thread that intends to wait on condition_variable has to acquire a
unique_lock first.
The wait operations atomically release the mutex and suspend the execution of
the thread.
When the condition variable is notified, the thread is awakened, and the mutex
is reacquired [2].
*/

while (!fQuit)
  {
// wait for fReady:
unique_lock lck(mtx);
fThreadsOk = true;
cv.wait(lck);   // unlocks lck, and waits for cv be signalled; then
autom. reacquires lck
if (fQuit) break;
if (!fReady) continue;

// work, ie. process the job:
cout << "thread " << id << " has grabbed the job\n";
//...

// notify parent with fReady=false; wakes up also all the other threads
fReady = false;
cv.notify_all();
  }
  }

int main()
  {
fQuit  = false;
fReady = false;
fThreadsOk = false;

const size_t N = 10;
vector threads;
for (size_t i = 0; i < N; ++i)
  threads.push_back(thread(threadfunc, i));

// wait so that at least one thread has done "cv.wait(lck)", see above
while (!fThreadsOk) sleep(1);

for (size_t i = 0; i < 1; ++i)
  {
cout << N << " threads ready to race: ";

// notify threads about work to do
{
unique_lock lck(mtx);
fReady = true;
cv.notify_all();

// wait till job was done
while (fReady) cv.wait(lck);
}
  }

// set fQuit and wake up the threads
{
unique_lock lck(mtx);
fQuit = true;
cv.notify_all();
}

// wait till all threads quit:
for (auto& th : threads) th.join();

cout << "pgm finished\n";
return 0;
  }

// end of test.cpp



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages g++-4.9 depends on:
ii  gcc-4.94.9.2-10
ii  gcc-4.9-base   4.9.

Bug#814239: marked as done (gcc-4.9: debian/patches/ada-symbolic-tracebacks.diff use snprintf return value without check)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #814239,
regarding gcc-4.9: debian/patches/ada-symbolic-tracebacks.diff use snprintf 
return value without check
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 ow...@bugs.debian.org
immediately.)


-- 
814239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gcc-4.9
Version: 4.9.2-10
Severity: normal
Tags: security

During code search, I found potentially problematic code in 
debian/patches/ada-symbolic-tracebacks.diff: it uses snprintf() results 
without checking its range, like this:


+else {
+  *len += snprintf(s, (max_len - (*len)), "%p at 
%s",addrs[i], line);

+}
+s = buf + (*len);

When formatted string would overflow supplied buffer or other error 
happens, snprintf returns value larger than buffer size or -1. In both 
cases, if you directly add it to the pointer, like in the above code, 
bad things will happen.


(Same patch seems used with other versions of gcc-* packages.)

-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcc-4.9 depends on:
ii  binutils2.25-5
ii  cpp-4.9 4.9.2-10
ii  gcc-4.9-base4.9.2-10
ii  libc6   2.19-18
ii  libcloog-isl4   0.18.2-1+b2
ii  libgcc-4.9-dev  4.9.2-10
ii  libgmp102:6.0.0+dfsg-6
ii  libisl100.12.2-2
ii  libmpc3 1.0.2-1
ii  libmpfr43.1.2-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-18

Versions of packages gcc-4.9 suggests:
ii  gcc-4.9-doc   4.9.1-3
pn  gcc-4.9-locales   
ii  gcc-4.9-multilib  4.9.2-10
pn  libasan1-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#799953: marked as done (4.9/5: incorrect double to integer conversion on i386)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #799953,
regarding 4.9/5: incorrect double to integer conversion on i386
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 ow...@bugs.debian.org
immediately.)


-- 
799953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc
Version: 4:5.2.1-4
Severity: normal
Tags: upstream

Hello,

I believe I've found a bug in GCC that affects plymouth and maybe
other packages on i386. The following minimal code produces an
incorrect result.


$ cat test.c 
#include 
#include 

void main(int argc, char **argv) {
  float f = 999;
  double d = f*atoi(argv[1]);
  float g = d;
  int i = d;

  printf("f = %f\n", f);
  printf("d = %f\n", d);
  printf("g = %f\n", g);
  /* printf("i = %d\n", i); */
  printf("fractional part of d is %f\n", d-i);
}

$ gcc-4.9 -O1 -o test test.c && ./test 100
f = 999.00
d = 99900.00
g = 99900.00
fractional part of d is 28.00


The variable 'i' should contain the integral part of 'd', and 'd-i'
should give 0.00. This is a standard method to calculate the
fractional part of a number. The bug disappears with optimization
turned off (-O0) or with uncommented printf statement. Assembly output
shows that an intermediate float is used for conversion instead of a
double.

The bug is present in gcc-snapshot package from unstable, but not in
gcc-4.6 from wheezy.


$ gcc-5 -O1 -o test test.c && ./test 100
f = 999.00
d = 99900.00
g = 99900.00
fractional part of d is 28.00

$ gcc-4.6 -O1 -o test test.c && ./test 100
f = 999.00
d = 99872.00
g = 99872.00
fractional part of d is 0.00


Cheers,
MU


$ gcc-4.9 -v
Using built-in specs.
COLLECT_GCC=gcc-4.9
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i586-linux-gnu/4.9/lto-wrapper
Target: i586-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-10' 
--with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.9 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --with-system-zlib --disable-browser-plugin 
--enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-i386/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-i386 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-i386 
--with-arch-directory=i386 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-targets=all --enable-multiarch --with-arch-32=i5
 86 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-checking=release --build=i586-linux-gnu --host=i586-linux-gnu 
--target=i586-linux-gnu
Thread model: posix
gcc version 4.9.2 (Debian 4.9.2-10)

$ gcc-5 -v
Using built-in specs.
COLLECT_GCC=gcc-5
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i586-linux-gnu/5/lto-wrapper
Target: i586-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 5.2.1-17' 
--with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-5 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib 
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-i386/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-i386 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-i386 
--with-arch-directory=i386 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-targets=all --enable-multiarch --with-arch-32=i58
 6 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-chec

Bug#798029: marked as done (Impossible to keep gcc-4.7 after upgrade to Debian Jessie)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #798029,
regarding Impossible to keep gcc-4.7 after upgrade to Debian Jessie
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 ow...@bugs.debian.org
immediately.)


-- 
798029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gcc-4.9-base
Version: 4.9.2-10

Debian bug 770025 added a "Breaks: gcc-4.7-base (< 4.7.3)" header to 
gcc-4.9, because it was found in bug 736607 (which relates to gcc-4.8) 
that the package manager would sometimes leave the system with an 
older-release version of gcc instead of using the version from Jessie 
(4.7.3 and up).

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770025
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736607

However, then Debian bug 765379 came around and gcc 4.7 was completely 
removed from Jessie.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765379

As a result it is now impossible to keep gcc 4.7 installed on a Jessie 
system when upgrading from an earlier release, or to install the package 
from an older release, even though absolutely nothing would actually 
break as a result of this.


Since the original problem posed in bug 770025 (of the package manager 
failing to update gcc-4.7) has been fixed, I believe the "Breaks: 
gcc-4.7-base (<4.7.3)" clause should be removed from gcc-4.9 (and 
probably from gcc-4.8, too).
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#786883: marked as done (gcc-4.9: --sysroot=... not properly respected - /usr/lib still stays in library search path)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #786883,
regarding gcc-4.9: --sysroot=... not properly respected - /usr/lib still stays 
in library search path
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 ow...@bugs.debian.org
immediately.)


-- 
786883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.2-18
Severity: normal

Dear Maintainer,

I'm trying to re-prefix gcc at runtime and found that --sysroot option
is not properly respected - /usr/lib/ still stays in ld search path.

Here is an example

$ pwd
/home/kirr/tmp/gcc-sysroot  # NOTE - non /  nor /usr/...

$ mkdir root# NOTE it will stay _empty_

$ cat prog.c# test program to compile/link
int main() { return 0; }

$ gcc --sysroot=`pwd`/root prog.c   # NOTE links ok. But it should
$ echo $?   # complain that it cannot find
0   # e.g. crt1.o

# like e.g. gcc-snapshot is complaining
$ /usr/lib/gcc-snapshot/bin/gcc --sysroot=`pwd`/root prog.c
/usr/bin/ld: cannot find crt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
collect2: error: ld returned 1 exit status

# though without --sysroot gcc-snapshot builds it ok:
$ /usr/lib/gcc-snapshot/bin/gcc prog.c
$ echo $?
0


I've investigated a bit with `gcc -v`:

$ gcc -v --sysroot=`pwd`/root prog.c
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-18' 
--with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.9 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --with-system-zlib --disable-browser-plugin 
--enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch --with-arch-32=i586 --
 with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib 
--with-tune=generic --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.2 (Debian 4.9.2-18) 
COLLECT_GCC_OPTIONS='-v' '-mtune=generic' '-march=x86-64'
 /usr/lib/gcc/x86_64-linux-gnu/4.9/cc1 -quiet -v -imultiarch 
x86_64-linux-gnu -isysroot /home/kirr/tmp/gcc-sysroot/root prog.c -quiet 
-dumpbase prog.c -mtune=generic -march=x86-64 -auxbase prog -version -o 
/tmp/cc7D9nYw.s
GNU C (Debian 4.9.2-18) version 4.9.2 (x86_64-linux-gnu)
compiled by GNU C version 4.9.2, GMP version 6.0.0, MPFR version 
3.1.2-p11, MPC version 1.0.3
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
ignoring nonexistent directory 
"/home/kirr/tmp/gcc-sysroot/root/usr/local/include/x86_64-linux-gnu"
ignoring nonexistent directory 
"/home/kirr/tmp/gcc-sysroot/root/usr/local/include"
ignoring nonexistent directory 
"/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../../x86_64-linux-gnu/include"
ignoring nonexistent directory 
"/home/kirr/tmp/gcc-sysroot/root/usr/include/x86_64-linux-gnu"
ignoring nonexistent directory "/home/kirr/tmp/gcc-sysroot/root/usr/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc/x86_64-linux-gnu/4.9/include
 /usr/lib/gcc/x86_64-linux-gnu/4.9/include-fixed
End of search list.
GNU C (Debian 4.9.2-18) version 4.9.2 (x86_64-linux-gnu)
compiled by GNU C version 4.9.2, GMP version 6.0.0, MPFR version 
3.1.2-p11, MPC version 1.0.3
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-hea

Bug#816776: marked as done (g++: internal compiler error: Segmentation fault when building qt-everywhere-opensource-src-4.8.7)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #816776,
regarding g++: internal compiler error: Segmentation fault when building 
qt-everywhere-opensource-src-4.8.7
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 ow...@bugs.debian.org
immediately.)


-- 
816776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-4.9
Version: 4.9.2-10
Severity: normal

Dear Maintainer,

Here is my error log :

/*/

g++ -c -include .pch/release-shared/QtCore 
-I/home/linuxconsole25/x86_64/include -I/home/linuxconsole25/dibab/CXXFLAGS 
-I/home/linuxconsole25/x86_64/include -I/home/linuxconsole25/x86_64/include/AL 
-I/home/linuxconsole25/x86_64/irrlicht 
-I/home/linuxconsole25/x86_64/include/freetype2 
-I/home/linuxconsole25/x86_64/include -I/home/linuxconsole25/dibab/CXXFLAGS 
-I/home/linuxconsole25/x86_64/include -I/home/linuxconsole25/x86_64/include/AL 
-I/home/linuxconsole25/x86_64/irrlicht 
-I/home/linuxconsole25/x86_64/include/freetype2 -pthread 
-I/home/linuxconsole25/x86_64/include/glib-2.0 
-I/home/linuxconsole25/x86_64/lib/glib-2.0/include -O2 -fvisibility=hidden 
-fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC -DQT_SHARED 
-DQT_BUILD_CORE_LIB -DQT_NO_USING_NAMESPACE -DQT_NO_CAST_TO_ASCII 
-DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER 
-DELF_INTERPRETER=\"/lib64/ld-linux-x86-64.so.2\" -DQLIBRARYINFO_EPOCROOT 
-DQT_USE_ICU -DHB_EXPORT=Q_CORE_EXPORT -DQT_NO_DEBUG -DQT_HAVE_MMX 
 -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_HAVE_SSE3 
-DQT_HAVE_SSSE3 -DQT_HAVE_SSE4_1 -DQT_HAVE_SSE4_2 -DQT_HAVE_AVX 
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
-I/home/linuxconsole25/dibab/src/qt-everywhere-opensource-src-4.8.7/mkspecs/linux-g++
 
-I/home/linuxconsole25/dibab/src/qt-everywhere-opensource-src-4.8.7/src/corelib 
-I../../include -I../../include/QtCore -I.rcc/release-shared -Iglobal 
-I/home/linuxconsole25/dibab/src/qt-everywhere-opensource-src-4.8.7/tools/shared
 
-I/home/linuxconsole25/dibab/src/qt-everywhere-opensource-src-4.8.7/src/3rdparty/harfbuzz/src
 
-I/home/linuxconsole25/dibab/src/qt-everywhere-opensource-src-4.8.7/src/3rdparty/md5
 
-I/home/linuxconsole25/dibab/src/qt-everywhere-opensource-src-4.8.7/src/3rdparty/md4
 -I.moc/release-shared -I/home/linuxconsole25//include -I. -o 
.obj/release-shared/qabstractanimation.o 
/home/linuxconsole25/dibab/src/qt-everywhere-opensource-src-4.8.7/src/corelib/animation/qabstractanimation.cpp

g++: internal compiler error: Segmentation fault (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
Makefile:7394: recipe for target '.obj/release-shared/qabstractanimation.o' 
failed
make[1]: *** [.obj/release-shared/qabstractanimation.o] Error 4
make[1]: Leaving directory 
'/home/linuxconsole25/dibab/build-x86_64/qt-everywhere-opensource-src-4.8.7/src/corelib'
Makefile:204: recipe for target 'sub-corelib-make_default-ordered' failed
make: *** [sub-corelib-make_default-ordered] Error 2

/*/

What can I do for "full bug report" ?

Thanks

Yann Le Doaré, France

-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14.32--grs-ipv6-64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages g++-4.9 depends on:
ii  gcc-4.94.9.2-10
ii  gcc-4.9-base   4.9.2-10
ii  libc6  2.19-18+deb8u3
ii  libcloog-isl4  0.18.2-1+b2
ii  libgmp10   2:6.0.0+dfsg-6
ii  libisl10   0.12.2-2
ii  libmpc31.0.2-1
ii  libmpfr4   3.1.2-2
ii  libstdc++-4.9-dev  4.9.2-10
ii  zlib1g 1:1.2.8.dfsg-2+b1

g++-4.9 recommends no packages.

Versions of packages g++-4.9 suggests:
pn  g++-4.9-multilib
pn  gcc-4.9-doc 
pn  libstdc++6-4.9-dbg  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version 

Bug#785762: marked as done (gcc-4.9: Segfault on llvm build)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #785762,
regarding gcc-4.9: Segfault on llvm build
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 ow...@bugs.debian.org
immediately.)


-- 
785762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.2-16
Severity: important
building with
g...@github.com:llvm-mirror/llvm.git
commit d70b3aca8e69e52f5683c2c0f351722482f5929f
Author: Tobias Grosser 
Date:   Tue May 19 06:25:19 2015 +


llvm[3]: Building Debug+Asserts Archive Library libLLVMipo.a
make[3]: Leaving directory
`/mnt/data/home/mdupont/experiments/llvm/build/lib/Transforms/IPO'
make[3]: Entering directory
`/mnt/data/home/mdupont/experiments/llvm/build/lib/Transforms/Vectorize'
llvm[3]: Compiling BBVectorize.cpp for Debug+Asserts build
/mnt/data/home/mdupont/experiments/llvm/lib/Transforms/Vectorize/BBVectorize.cpp:
In member function 'bool
{anonymous}::BBVectorize::vectorizeBB(llvm::BasicBlock&)':
/mnt/data/home/mdupont/experiments/llvm/lib/Transforms/Vectorize/BBVectorize.cpp:394:10:
internal compiler error: Segmentation fault
 bool vectorizeBB(BasicBlock &BB) {
  ^
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-4.9 depends on:
ii  binutils2.25-4
ii  cpp-4.9 4.9.2-16
ii  gcc-4.9-base4.9.2-16
ii  libc6   2.19-3
ii  libcloog-isl4   0.18.2-1
ii  libgcc-4.9-dev  4.9.2-16
ii  libgmp102:6.0.0+dfsg-4
ii  libisl130.14-2
ii  libmpc3 1.0.1-1
ii  libmpfr43.1.2-1
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-3

Versions of packages gcc-4.9 suggests:
pn  gcc-4.9-doc   
pn  gcc-4.9-locales   
pn  gcc-4.9-multilib  
pn  libasan1-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information


-- 
James Michael DuPont
Member of Free Libre Open Source Software Kosova http://www.flossk.org
Saving Wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#797426: marked as done (g++: internal compiler error: Getötet (program cc1plus))

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #797426,
regarding g++: internal compiler error: Getötet (program cc1plus)
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 ow...@bugs.debian.org
immediately.)


-- 
797426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-4.9
Version: 4.9.3-3
Severity: important

I was trying to build phantomjs (git hash 
d038a004be21b0cf6d47a1330002e383de06fb27) from github.com/ariya/phantomjs.git
when this error ocurred:
g++: internal compiler error: Getötet (program cc1plus)
Please submit a full bug report

The last lines of the output where:
https://paste.debian.net/309703/
(The full log was 14MB, so a bit much)
I still have it if you need it.

gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.3-3' 
--with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.9 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --with-system-zlib --disable-browser-plugin 
--enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64 
 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.3 (Debian 4.9.3-3)

Cheers,
Konstantin

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages g++-4.9 depends on:
ii  gcc-4.94.9.3-3
ii  gcc-4.9-base   4.9.3-3
ii  libc6  2.19-19
ii  libcloog-isl4  0.18.3-1
ii  libgmp10   2:6.0.0+dfsg-7
ii  libisl13   0.14-2
ii  libmpc31.0.3-1
ii  libmpfr4   3.1.3-1
ii  libstdc++-4.9-dev  4.9.3-3
ii  zlib1g 1:1.2.8.dfsg-2+b1

g++-4.9 recommends no packages.

Versions of packages g++-4.9 suggests:
pn  g++-4.9-multilib
pn  gcc-4.9-doc 
pn  libstdc++6-4.9-dbg  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#823222: marked as done (gcc-4.9: reordering of signed int operations triggers overflow)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #823222,
regarding gcc-4.9: reordering of signed int operations triggers overflow
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 ow...@bugs.debian.org
immediately.)


-- 
823222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.2-10
Severity: normal

I compiled the program

#include 
#include 
int main() {
int s = 1 << 30;
s += (s - 1);
printf("%d\n%d\n%d\n", sizeof s, s, INT_MAX);
return 0;
}

with "gcc -W -Wall -ansi -pedantic -O0 -fsanitize=undefined".
The executable emits warnings for undefined behaviour at runtime:

a.c:6:7: runtime error: signed integer overflow: 1073741824 + 1073741824 cannot 
be represented in type 'int'
a.c:6:7: runtime error: signed integer overflow: -2147483648 + -1 cannot be 
represented in type 'int'
4
2147483647
2147483647

As far as I can tell, the program is correct, and does not involve undefined
behaviour because no signed-integer overflow occurs.  It turns out, however,
that gcc transforms 

s += (s - 1);

into 

s += s;
s -= 1;

even at -O0, as is apparent in the generated assembly code (gcc -O0 -S)
...
movl$1073741824, -12(%ebp)
movl-12(%ebp), %eax
addl%eax, %eax
subl$1, %eax
movl%eax, -12(%ebp)
...

Here, it seems that the compiler and libubsan disagree, and I'm not sure which
one is right.

Best regards,
g.

-- System Information:
Debian Release: 8.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gcc-4.9 depends on:
ii  binutils2.25-5
ii  cpp-4.9 4.9.2-10
ii  gcc-4.9-base4.9.2-10
ii  libc6   2.19-18+deb8u4
ii  libcloog-isl4   0.18.2-1+b2
ii  libgcc-4.9-dev  4.9.2-10
ii  libgmp102:6.0.0+dfsg-6
ii  libisl100.12.2-2
ii  libmpc3 1.0.2-1
ii  libmpfr43.1.2-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-18+deb8u4

Versions of packages gcc-4.9 suggests:
ii  gcc-4.9-doc   4.9.1-3
pn  gcc-4.9-locales   
pn  gcc-4.9-multilib  
pn  libasan1-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#797151: marked as done (gcc-4.9: Spurious warnings about pointer to array -> const pointer to array conversion.)

[Debian Bug Tracking System]

Your message dated Tue, 20 Sep 2016 22:15:11 +
with message-id 
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #797151,
regarding gcc-4.9: Spurious warnings about pointer to array -> const pointer to 
array conversion.
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 ow...@bugs.debian.org
immediately.)


-- 
797151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.9
Version: 4.9.3-3
Severity: normal

Dear Maintainer,

This bug may affect all gcc-4, but has been fixed on gcc-5 upstream:
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16602).

When compiling the attached code, gcc-4 always warns
"
ex_ptrtoarr.c: In function ‘main’:
ex_ptrtoarr.c:13:3: warning: passing argument 1 of ‘mdsumcmp’ from
incompatible pointer type [enabled by default]
   return mdsumcmp(&sum1, &sum2);
   ^
ex_ptrtoarr.c:4:5: note: expected ‘const uint8_t (*)[16]’ but argument is
of type ‘uint8_t (*)[16]’
 int mdsumcmp(const uint8_t (*s1)[16], const uint8_t (*s2)[16])
 ^
ex_ptrtoarr.c:13:3: warning: passing argument 2 of ‘mdsumcmp’ from
incompatible pointer type [enabled by default]
   return mdsumcmp(&sum1, &sum2);
   ^
ex_ptrtoarr.c:4:5: note: expected ‘const uint8_t (*)[16]’ but argument is
of type ‘uint8_t (*)[16]’
 int mdsumcmp(const uint8_t (*s1)[16], const uint8_t (*s2)[16])
 ^
"
but gcc-5 and clang complain nothing.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcc-4.9 depends on:
ii  binutils2.25.1-1
ii  cpp-4.9 4.9.3-3
ii  gcc-4.9-base4.9.3-3
ii  libc6   2.19-19
ii  libcloog-isl4   0.18.3-1
ii  libgcc-4.9-dev  4.9.3-3
ii  libgmp102:6.0.0+dfsg-7
ii  libisl130.14-2
ii  libmpc3 1.0.3-1
ii  libmpfr43.1.3-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-19

Versions of packages gcc-4.9 suggests:
pn  gcc-4.9-doc   
pn  gcc-4.9-locales   
pn  gcc-4.9-multilib  
pn  libasan1-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information
#include 
#include 

int mdsumcmp(const uint8_t (*s1)[16], const uint8_t (*s2)[16])
{
  return memcmp(*s1, *s2, sizeof(*s1));
}

int main(void)
{
  uint8_t sum1[16];
  uint8_t sum2[16];
  return mdsumcmp(&sum1, &sum2);
}
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm

Dear submitter,

as the package gcc-4.9 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/838316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Processed: Re: Bug#773065 closed by Debian FTP Masters (Bug#838316: Removed package(s) from unstable)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #773065 {Done: Debian FTP Masters } 
[src:gcc-4.9] selecting target via dpkg-buildpackage --target-arch
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4.9.4-2+rm.
> reassign -1 src:gcc-6
Bug #773065 [src:gcc-4.9] selecting target via dpkg-buildpackage --target-arch
Bug reassigned from package 'src:gcc-4.9' to 'src:gcc-6'.
No longer marked as found in versions gcc-4.9/4.9.2-7.
Ignoring request to alter fixed versions of bug #773065 to the same values 
previously set

-- 
773065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 727621 to g++-6, reopening 727621

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 727621 g++-6
Bug #727621 {Done: Debian FTP Masters } 
[gcc-4.9,gcc-6] armel: std::future appears to be broken?
Bug reassigned from package 'gcc-4.9,gcc-6' to 'g++-6'.
Ignoring request to alter found versions of bug #727621 to the same values 
previously set
No longer marked as fixed in versions 4.9.4-2+rm.
> reopen 727621
Bug #727621 {Done: Debian FTP Masters } 
[g++-6] armel: std::future appears to be broken?
Bug reopened
Ignoring request to alter fixed versions of bug #727621 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
727621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forwarded gcc issue

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 838438 https://gcc.gnu.org/PR77686
Bug #838438 [g++-6] g++/armel,armhf: -O2 causes memory corruption for some 
lambda captures
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR77686'.
> tags 838438 + upstream
Bug #838438 [g++-6] g++/armel,armhf: -O2 causes memory corruption for some 
lambda captures
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
838438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Fwd: Processed: Fwd:

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 838892 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71709
Bug #838892 [src:gcc-6] [ppc64el] boot arguments (passed as CONFIG_CMDLINE) are 
not being picked up by kernel
Set Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71709'.
> tags 838892 confirmed fixed-upstream
Bug #838892 [src:gcc-6] [ppc64el] boot arguments (passed as CONFIG_CMDLINE) are 
not being picked up by kernel
Added tag(s) fixed-upstream and confirmed.
> user debian-powe...@lists.debian.org
Setting user to debian-powe...@lists.debian.org (was ma...@debian.org).
> usertags 838892 ppc64el
There were no usertags set.
Usertags are now: ppc64el.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
838892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 838892 src:linux
Bug #838892 [src:gcc-6] [ppc64el] boot arguments (passed as CONFIG_CMDLINE) are 
not being picked up by kernel
Added indication that 838892 affects src:linux
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
838892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forwarded gcc issue

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 838874 https://gcc.gnu.org/PR66317
Bug #838874 [gcc-6] gcc-6: crash on malformed __FILE__
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR66317'.
> tags 838874 + upstream
Bug #838874 [gcc-6] gcc-6: crash on malformed __FILE__
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
838874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#838591: gcc-6: GROMACS compiled with gcc 6.2.0-4 fails the tests

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 838591 gromacs
Bug #838591 [gcc-6] gcc-6: GROMACS compiled with gcc 6.2.0-4 fails the tests
Bug reassigned from package 'gcc-6' to 'gromacs'.
No longer marked as found in versions gcc-6/6.2.0-4.
Ignoring request to alter fixed versions of bug #838591 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
838591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#838111: marked as done (gcj-6-jre-headless: /usr/bin/gij-6.bin: not found)

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2016 16:21:48 +
with message-id 
and subject line Bug#838111: fixed in gcc-6 6.2.0-5
has caused the Debian Bug report #838111,
regarding gcj-6-jre-headless: /usr/bin/gij-6.bin: not found
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 ow...@bugs.debian.org
immediately.)


-- 
838111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcj-6-jre-headless
Version: 6.2.0-4
Severity: normal

Dear Maintainer,

The /usr/bin/gij-6.bin file/link is not installed on hppa.  This causes
vtk6 and libreoffice builds to fail.  See for example:
https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=hppa&ver=1%3A5.2.1-3&stamp=1474103136

checking for posix_fallocate... yes
checking whether to add custom build version... yes, 1:5.2.1-3
/usr/lib/jvm/java-gcj/bin/java: 10: exec: /usr/bin/gij-6.bin: not found
checking the installed JDK... configure: error: JDK is too old, you need at 
least 1.5
Error running configure at ./autogen.sh line 281.
debian/rules:1979: recipe for target 'debian/stampdir/build-arch' failed
make: *** [debian/stampdir/build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Build finished at 2016-09-17T09:03:54Z

Regards,
Dave

-- System Information:
Debian Release: stretch/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.7.4+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gcj-6-jre-headless depends on:
ii  gcc-6-base 6.2.0-4
ii  gcj-6-jre-lib  6.2.0-4
ii  libc6  2.24-2+b1
ii  libgcc41:6.2.0-4
ii  libgcj17   6.2.0-4
ii  prctl  1.6-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

gcj-6-jre-headless recommends no packages.

Versions of packages gcj-6-jre-headless suggests:
ii  fastjar   2:0.98-6
ii  gcj-6-jdk 6.2.0-4
ii  libgcj17-awt  6.2.0-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gcc-6
Source-Version: 6.2.0-5

We believe that the bug you reported is fixed in the latest version of
gcc-6, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 838...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 28 Sep 2016 15:53:28 +0200
Source: gcc-6
Binary: gcc-6-base libgcc1 libgcc1-dbg libgcc2 libgcc2-dbg libgcc-6-dev libgcc4 
libgcc4-dbg lib64gcc1 lib64gcc1-dbg lib64gcc-6-dev lib32gcc1 lib32gcc1-dbg 
lib32gcc-6-dev libn32gcc1 libn32gcc1-dbg libn32gcc-6-dev libx32gcc1 
libx32gcc1-dbg libx32gcc-6-dev gcc-6 gcc-6-multilib gcc-6-test-results 
gcc-6-plugin-dev gcc-6-hppa64-linux-gnu cpp-6 gcc-6-locales g++-6 
g++-6-multilib libgomp1 libgomp1-dbg lib32gomp1 lib32gomp1-dbg lib64gomp1 
lib64gomp1-dbg libn32gomp1 libn32gomp1-dbg libx32gomp1 libx32gomp1-dbg libitm1 
libitm1-dbg lib32itm1 lib32itm1-dbg lib64itm1 lib64itm1-dbg libx32itm1 
libx32itm1-dbg libatomic1 libatomic1-dbg lib32atomic1 lib32atomic1-dbg 
lib64atomic1 lib64atomic1-dbg libn32atomic1 libn32atomic1-dbg libx32atomic1 
libx32atomic1-dbg libasan3 libasan3-dbg lib32asan3 lib32asan3-dbg lib64asan3 
lib64asan3-dbg libx32asan3 libx32asan3-dbg liblsan0 liblsan0-dbg lib32lsan0 
lib32lsan0-dbg libx32lsan0 libx32lsan0-dbg libtsan0 libtsan0-dbg libubsan0 
libubsan0-dbg lib32ubsan0
 lib32ubsan0-dbg lib64ubsan0 lib64ubsan0-dbg libx32ubsan0 libx32ubsan0-dbg 
libcilkrts5 libcilkrts5-dbg lib32cilkrts5 lib32cilkrts5-dbg lib64cilkrts5 
lib64cilkrts5-dbg libx32cilkrts5 libx32cilkrts5-dbg libmpx2 libmpx2-dbg 
lib32mpx2 lib32mpx2-dbg lib64mpx2 lib64mpx2-dbg libquadmath0 libquadmath0-dbg 
lib32quadmath0 lib32quadmath0-dbg lib64quadmath0 lib64quadmath0-dbg 
libx32quadmath0 libx32quadmath0-dbg libcc1-0 libgccjit0 libgccjit0-dbg 
libgccjit-6-doc libgccjit-6-dev gob

Processed: Re: Bug#839132: libgo9: libgo built without FFI in mips*

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + help
Bug #839132 [libgo9] libgo9: libgo built without FFI in mips*
Added tag(s) help.

-- 
839132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package gcc-6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package gcc-6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #838438 (http://bugs.debian.org/838438)
> # Bug title: g++/armel,armhf: -O2 causes memory corruption for some lambda 
> captures
> #  * http://gcc.gnu.org/PR77686
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 838438 + fixed-upstream
Bug #838438 [g++-6] g++/armel,armhf: -O2 causes memory corruption for some 
lambda captures
Added tag(s) fixed-upstream.
> usertags 838438 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 838438 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
838438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 2 errors): limit source to gcc-doc-defaults, tagging 794778, tagging 825320, tagging 833505

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source gcc-doc-defaults
Limiting to bugs with field 'source' containing at least one of 
'gcc-doc-defaults'
Limit currently set to 'source':'gcc-doc-defaults'

> tags 794778 + pending
source: "gcc-defaults, gcc-doc-defaults"' does not match at least one of 
"gcc-doc-defaults"
source: "gcc-defaults, gcc-doc-defaults"' does not match at least one of 
"gcc-doc-defaults"
Failed to alter tags of Bug 794778: limit failed for bugs: 794778, 833505.

> tags 825320 + pending
Bug #825320 [src:gcc-doc-defaults] gcc-doc-defaults: FTBFS in sid: error in 
'Version' field string '5:': nothing after colon in version number
Added tag(s) pending.
> tags 833505 + pending
source: "gcc-defaults, gcc-doc-defaults"' does not match at least one of 
"gcc-doc-defaults"
source: "gcc-defaults, gcc-doc-defaults"' does not match at least one of 
"gcc-doc-defaults"
Failed to alter tags of Bug 833505: limit failed for bugs: 833505, 794778.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
825320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 833505, tagging 794778

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 833505 + pending
Bug #833505 [gcc-doc] gcc-doc: please update to gcc-6-doc
Bug #794778 [gcc-doc] Should update to gcc-6-doc packages
Added tag(s) pending.
Added tag(s) pending.
> tags 794778 + pending
Bug #794778 [gcc-doc] Should update to gcc-6-doc packages
Bug #833505 [gcc-doc] gcc-doc: please update to gcc-6-doc
Ignoring request to alter tags of bug #794778 to the same tags previously set
Ignoring request to alter tags of bug #833505 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
794778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794778
833505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#794778: marked as done (Should update to gcc-6-doc packages)

[Debian Bug Tracking System]

Your message dated Sun, 02 Oct 2016 10:29:53 +
with message-id 
and subject line Bug#794778: fixed in gcc-doc-defaults 5:15
has caused the Debian Bug report #794778,
regarding Should update to gcc-6-doc packages
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 ow...@bugs.debian.org
immediately.)


-- 
794778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-doc
Version: 5:4.9.2-1
Severity: normal

Now that gcc 5 is the new default, gcc-doc/cpp-doc/etc should depend on the
newer 5 versions.

Thanks.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcc-doc depends on:
ii  gcc-4.9-doc  4.9.2-2

gcc-doc recommends no packages.

gcc-doc suggests no packages.
--- End Message ---
--- Begin Message ---
Source: gcc-doc-defaults
Source-Version: 5:15

We believe that the bug you reported is fixed in the latest version of
gcc-doc-defaults, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 794...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Eremin-Solenikov  (supplier of updated 
gcc-doc-defaults package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Sep 2016 23:48:17 +0300
Source: gcc-doc-defaults
Binary: gcc-doc cpp-doc gfortran-doc gnat-doc gcj-doc gccgo-doc gcc-doc-base
Architecture: source amd64 all
Version: 5:15
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Dmitry Eremin-Solenikov 
Description:
 cpp-doc- documentation for the GNU C preprocessor (cpp)
 gcc-doc- documentation for the GNU compilers (gcc, gobjc, g++)
 gcc-doc-base - several GNU manual pages
 gccgo-doc  - documentation for the GNU Go compiler (gccgo)
 gcj-doc- documentation for the GNU Java tools (gcj, gij)
 gfortran-doc - documentation for the GNU Fortran Compiler (gfortran)
 gnat-doc   - documentation for the GNU Ada Compiler (gnat)
Closes: 794778 825320 833505
Changes:
 gcc-doc-defaults (5:15) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dmitry Eremin-Solenikov ]
   * Updated to 6.1 versions. (Closes: #794778, #833505)
 .
   [ Paul Wise ]
   * Switch from gnatgcc to gnat for version determination due to #839209
 (Closes: #825320)
Checksums-Sha1:
 90df4f7b636b525b3d665a3308edd2da94fa 2261 gcc-doc-defaults_15.dsc
 37a23e03f76994b23c51201ecb358619b07f7a05 30200 gcc-doc-defaults_15.tar.xz
 108ea64cc9923d7150e9f64f8da9988d773a2522 5462 cpp-doc_6.1.0-1_amd64.deb
 6323c80396b53b277e2dade579a8ef3377d526cc 32176 gcc-doc-base_6.1.0-1_all.deb
 70b8a09d2761355bd35cc7b957670539009a7795 5560 gcc-doc_6.1.0-1_amd64.deb
 854e3b6ea66c05a93229761ef1b64dde2535bd6a 5300 gccgo-doc_6.1.0-1_amd64.deb
 d2ababb7312662f0b996108542cd9e84c7c42e58 5528 gcj-doc_6.1.0-1_amd64.deb
 f21be1a1befa07492d553837341b8ed6e855574e 5442 gfortran-doc_6.1.0-1_amd64.deb
 cfc8fdfa0eed3bd273871f8dc00b2ba7262d7610 5450 gnat-doc_6.1.0-1_amd64.deb
Checksums-Sha256:
 3e5f33477575cf78c1e2b7e0a5d0cefef49fcdeddd9de27eeddc85ac4c49a174 2261 
gcc-doc-defaults_15.dsc
 b9cbb045c0c030f46e9cdb496595e9bfa649ce8669d841d6f88032eb3a1ea5ed 30200 
gcc-doc-defaults_15.tar.xz
 f1f523fad3a1c201d0aaa35bbcc7627a930225935e4631531151c7607167003d 5462 
cpp-doc_6.1.0-1_amd64.deb
 25d36eeb205e8f68d3cb3a69277bec8f5e1617848e9423b49eb6e6d44458e289 32176 
gcc-doc-base_6.1.0-1_all.deb
 78e8610d6b2d52f61b1bc09cc9dc83a972ea879bd5c72d3e36948fddc6745b21 5560 
gcc-doc_6.1.0-1_amd64.deb
 75ebf5ec755bb61f987cd66bb8ed646985bceb1484016e1c349a6bbeb4b795f8 5300 
gccgo-doc_6.1.0-1_amd64.deb
 550f7d7486c18a30fa366c3ed7164e8a394a0fa93b77cf4051f934bcda40d5c8 5528 
gcj-doc_6.1.0-1_amd64.deb
 88c2fe7e96030dfce9fd7a09f3f330aa2141a8883d21d27b861f4d8f457aac72 5442 
gfortran-doc_6.1.0-1_amd64.deb
 93250428b9229da52b640c42dd592c4a1a2121ec169b39951d5e8644af39314b 5450 
gnat-doc_6.1

Bug#833505: marked as done (gcc-doc: please update to gcc-6-doc)

[Debian Bug Tracking System]

Your message dated Sun, 02 Oct 2016 10:29:53 +
with message-id 
and subject line Bug#833505: fixed in gcc-doc-defaults 5:15
has caused the Debian Bug report #833505,
regarding gcc-doc: please update to gcc-6-doc
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 ow...@bugs.debian.org
immediately.)


-- 
833505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-doc
Version: 5:4.9.2-1
Severity: important

Hi,

please update gcc-doc so it points to the documentation
for the version of GCC that’s to be released as the
default compiler for stretch.

Thanks!

-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages gcc-doc depends on:
ii  gcc-4.9-doc  4.9.3-1

gcc-doc recommends no packages.

gcc-doc suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: package gcc-doc is not installed
--- End Message ---
--- Begin Message ---
Source: gcc-doc-defaults
Source-Version: 5:15

We believe that the bug you reported is fixed in the latest version of
gcc-doc-defaults, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 833...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Eremin-Solenikov  (supplier of updated 
gcc-doc-defaults package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Sep 2016 23:48:17 +0300
Source: gcc-doc-defaults
Binary: gcc-doc cpp-doc gfortran-doc gnat-doc gcj-doc gccgo-doc gcc-doc-base
Architecture: source amd64 all
Version: 5:15
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Dmitry Eremin-Solenikov 
Description:
 cpp-doc- documentation for the GNU C preprocessor (cpp)
 gcc-doc- documentation for the GNU compilers (gcc, gobjc, g++)
 gcc-doc-base - several GNU manual pages
 gccgo-doc  - documentation for the GNU Go compiler (gccgo)
 gcj-doc- documentation for the GNU Java tools (gcj, gij)
 gfortran-doc - documentation for the GNU Fortran Compiler (gfortran)
 gnat-doc   - documentation for the GNU Ada Compiler (gnat)
Closes: 794778 825320 833505
Changes:
 gcc-doc-defaults (5:15) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dmitry Eremin-Solenikov ]
   * Updated to 6.1 versions. (Closes: #794778, #833505)
 .
   [ Paul Wise ]
   * Switch from gnatgcc to gnat for version determination due to #839209
 (Closes: #825320)
Checksums-Sha1:
 90df4f7b636b525b3d665a3308edd2da94fa 2261 gcc-doc-defaults_15.dsc
 37a23e03f76994b23c51201ecb358619b07f7a05 30200 gcc-doc-defaults_15.tar.xz
 108ea64cc9923d7150e9f64f8da9988d773a2522 5462 cpp-doc_6.1.0-1_amd64.deb
 6323c80396b53b277e2dade579a8ef3377d526cc 32176 gcc-doc-base_6.1.0-1_all.deb
 70b8a09d2761355bd35cc7b957670539009a7795 5560 gcc-doc_6.1.0-1_amd64.deb
 854e3b6ea66c05a93229761ef1b64dde2535bd6a 5300 gccgo-doc_6.1.0-1_amd64.deb
 d2ababb7312662f0b996108542cd9e84c7c42e58 5528 gcj-doc_6.1.0-1_amd64.deb
 f21be1a1befa07492d553837341b8ed6e855574e 5442 gfortran-doc_6.1.0-1_amd64.deb
 cfc8fdfa0eed3bd273871f8dc00b2ba7262d7610 5450 gnat-doc_6.1.0-1_amd64.deb
Checksums-Sha256:
 3e5f33477575cf78c1e2b7e0a5d0cefef49fcdeddd9de27eeddc85ac4c49a174 2261 
gcc-doc-defaults_15.dsc
 b9cbb045c0c030f46e9cdb496595e9bfa649ce8669d841d6f88032eb3a1ea5ed 30200 
gcc-doc-defaults_15.tar.xz
 f1f523fad3a1c201d0aaa35bbcc7627a930225935e4631531151c7607167003d 5462 
cpp-doc_6.1.0-1_amd64.deb
 25d36eeb205e8f68d3cb3a69277bec8f5e1617848e9423b49eb6e6d44458e289 32176 
gcc-doc-base_6.1.0-1_all.deb
 78e8610d6b2d52f61b1bc09cc9dc83a972ea879bd5c72d3e36948fddc6745b21 5560 
gcc-doc_6.1.0-1_amd64.deb
 75ebf5ec755bb61f987cd66bb8ed646985bceb1484016e1c349a6bbeb4b795f8 5300 
gccgo-doc_6.1.0-1_amd64.deb
 550f7d7486c18a30fa366c3ed7164e8a394a0fa93b77cf4051f934bcda40d5c8 5

Bug#794778: marked as done (Should update to gcc-6-doc packages)

[Debian Bug Tracking System]

Your message dated Sun, 02 Oct 2016 10:29:53 +
with message-id 
and subject line Bug#833505: fixed in gcc-doc-defaults 5:15
has caused the Debian Bug report #833505,
regarding Should update to gcc-6-doc packages
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 ow...@bugs.debian.org
immediately.)


-- 
833505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-doc
Version: 5:4.9.2-1
Severity: normal

Now that gcc 5 is the new default, gcc-doc/cpp-doc/etc should depend on the
newer 5 versions.

Thanks.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcc-doc depends on:
ii  gcc-4.9-doc  4.9.2-2

gcc-doc recommends no packages.

gcc-doc suggests no packages.
--- End Message ---
--- Begin Message ---
Source: gcc-doc-defaults
Source-Version: 5:15

We believe that the bug you reported is fixed in the latest version of
gcc-doc-defaults, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 833...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Eremin-Solenikov  (supplier of updated 
gcc-doc-defaults package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Sep 2016 23:48:17 +0300
Source: gcc-doc-defaults
Binary: gcc-doc cpp-doc gfortran-doc gnat-doc gcj-doc gccgo-doc gcc-doc-base
Architecture: source amd64 all
Version: 5:15
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Dmitry Eremin-Solenikov 
Description:
 cpp-doc- documentation for the GNU C preprocessor (cpp)
 gcc-doc- documentation for the GNU compilers (gcc, gobjc, g++)
 gcc-doc-base - several GNU manual pages
 gccgo-doc  - documentation for the GNU Go compiler (gccgo)
 gcj-doc- documentation for the GNU Java tools (gcj, gij)
 gfortran-doc - documentation for the GNU Fortran Compiler (gfortran)
 gnat-doc   - documentation for the GNU Ada Compiler (gnat)
Closes: 794778 825320 833505
Changes:
 gcc-doc-defaults (5:15) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dmitry Eremin-Solenikov ]
   * Updated to 6.1 versions. (Closes: #794778, #833505)
 .
   [ Paul Wise ]
   * Switch from gnatgcc to gnat for version determination due to #839209
 (Closes: #825320)
Checksums-Sha1:
 90df4f7b636b525b3d665a3308edd2da94fa 2261 gcc-doc-defaults_15.dsc
 37a23e03f76994b23c51201ecb358619b07f7a05 30200 gcc-doc-defaults_15.tar.xz
 108ea64cc9923d7150e9f64f8da9988d773a2522 5462 cpp-doc_6.1.0-1_amd64.deb
 6323c80396b53b277e2dade579a8ef3377d526cc 32176 gcc-doc-base_6.1.0-1_all.deb
 70b8a09d2761355bd35cc7b957670539009a7795 5560 gcc-doc_6.1.0-1_amd64.deb
 854e3b6ea66c05a93229761ef1b64dde2535bd6a 5300 gccgo-doc_6.1.0-1_amd64.deb
 d2ababb7312662f0b996108542cd9e84c7c42e58 5528 gcj-doc_6.1.0-1_amd64.deb
 f21be1a1befa07492d553837341b8ed6e855574e 5442 gfortran-doc_6.1.0-1_amd64.deb
 cfc8fdfa0eed3bd273871f8dc00b2ba7262d7610 5450 gnat-doc_6.1.0-1_amd64.deb
Checksums-Sha256:
 3e5f33477575cf78c1e2b7e0a5d0cefef49fcdeddd9de27eeddc85ac4c49a174 2261 
gcc-doc-defaults_15.dsc
 b9cbb045c0c030f46e9cdb496595e9bfa649ce8669d841d6f88032eb3a1ea5ed 30200 
gcc-doc-defaults_15.tar.xz
 f1f523fad3a1c201d0aaa35bbcc7627a930225935e4631531151c7607167003d 5462 
cpp-doc_6.1.0-1_amd64.deb
 25d36eeb205e8f68d3cb3a69277bec8f5e1617848e9423b49eb6e6d44458e289 32176 
gcc-doc-base_6.1.0-1_all.deb
 78e8610d6b2d52f61b1bc09cc9dc83a972ea879bd5c72d3e36948fddc6745b21 5560 
gcc-doc_6.1.0-1_amd64.deb
 75ebf5ec755bb61f987cd66bb8ed646985bceb1484016e1c349a6bbeb4b795f8 5300 
gccgo-doc_6.1.0-1_amd64.deb
 550f7d7486c18a30fa366c3ed7164e8a394a0fa93b77cf4051f934bcda40d5c8 5528 
gcj-doc_6.1.0-1_amd64.deb
 88c2fe7e96030dfce9fd7a09f3f330aa2141a8883d21d27b861f4d8f457aac72 5442 
gfortran-doc_6.1.0-1_amd64.deb
 93250428b9229da52b640c42dd592c4a1a2121ec169b39951d5e8644af39314b 5450 
gnat-doc_6.1

Bug#833505: marked as done (gcc-doc: please update to gcc-6-doc)

[Debian Bug Tracking System]

Your message dated Sun, 02 Oct 2016 10:29:53 +
with message-id 
and subject line Bug#794778: fixed in gcc-doc-defaults 5:15
has caused the Debian Bug report #794778,
regarding gcc-doc: please update to gcc-6-doc
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 ow...@bugs.debian.org
immediately.)


-- 
794778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-doc
Version: 5:4.9.2-1
Severity: important

Hi,

please update gcc-doc so it points to the documentation
for the version of GCC that’s to be released as the
default compiler for stretch.

Thanks!

-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages gcc-doc depends on:
ii  gcc-4.9-doc  4.9.3-1

gcc-doc recommends no packages.

gcc-doc suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: package gcc-doc is not installed
--- End Message ---
--- Begin Message ---
Source: gcc-doc-defaults
Source-Version: 5:15

We believe that the bug you reported is fixed in the latest version of
gcc-doc-defaults, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 794...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Eremin-Solenikov  (supplier of updated 
gcc-doc-defaults package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Sep 2016 23:48:17 +0300
Source: gcc-doc-defaults
Binary: gcc-doc cpp-doc gfortran-doc gnat-doc gcj-doc gccgo-doc gcc-doc-base
Architecture: source amd64 all
Version: 5:15
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Dmitry Eremin-Solenikov 
Description:
 cpp-doc- documentation for the GNU C preprocessor (cpp)
 gcc-doc- documentation for the GNU compilers (gcc, gobjc, g++)
 gcc-doc-base - several GNU manual pages
 gccgo-doc  - documentation for the GNU Go compiler (gccgo)
 gcj-doc- documentation for the GNU Java tools (gcj, gij)
 gfortran-doc - documentation for the GNU Fortran Compiler (gfortran)
 gnat-doc   - documentation for the GNU Ada Compiler (gnat)
Closes: 794778 825320 833505
Changes:
 gcc-doc-defaults (5:15) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dmitry Eremin-Solenikov ]
   * Updated to 6.1 versions. (Closes: #794778, #833505)
 .
   [ Paul Wise ]
   * Switch from gnatgcc to gnat for version determination due to #839209
 (Closes: #825320)
Checksums-Sha1:
 90df4f7b636b525b3d665a3308edd2da94fa 2261 gcc-doc-defaults_15.dsc
 37a23e03f76994b23c51201ecb358619b07f7a05 30200 gcc-doc-defaults_15.tar.xz
 108ea64cc9923d7150e9f64f8da9988d773a2522 5462 cpp-doc_6.1.0-1_amd64.deb
 6323c80396b53b277e2dade579a8ef3377d526cc 32176 gcc-doc-base_6.1.0-1_all.deb
 70b8a09d2761355bd35cc7b957670539009a7795 5560 gcc-doc_6.1.0-1_amd64.deb
 854e3b6ea66c05a93229761ef1b64dde2535bd6a 5300 gccgo-doc_6.1.0-1_amd64.deb
 d2ababb7312662f0b996108542cd9e84c7c42e58 5528 gcj-doc_6.1.0-1_amd64.deb
 f21be1a1befa07492d553837341b8ed6e855574e 5442 gfortran-doc_6.1.0-1_amd64.deb
 cfc8fdfa0eed3bd273871f8dc00b2ba7262d7610 5450 gnat-doc_6.1.0-1_amd64.deb
Checksums-Sha256:
 3e5f33477575cf78c1e2b7e0a5d0cefef49fcdeddd9de27eeddc85ac4c49a174 2261 
gcc-doc-defaults_15.dsc
 b9cbb045c0c030f46e9cdb496595e9bfa649ce8669d841d6f88032eb3a1ea5ed 30200 
gcc-doc-defaults_15.tar.xz
 f1f523fad3a1c201d0aaa35bbcc7627a930225935e4631531151c7607167003d 5462 
cpp-doc_6.1.0-1_amd64.deb
 25d36eeb205e8f68d3cb3a69277bec8f5e1617848e9423b49eb6e6d44458e289 32176 
gcc-doc-base_6.1.0-1_all.deb
 78e8610d6b2d52f61b1bc09cc9dc83a972ea879bd5c72d3e36948fddc6745b21 5560 
gcc-doc_6.1.0-1_amd64.deb
 75ebf5ec755bb61f987cd66bb8ed646985bceb1484016e1c349a6bbeb4b795f8 5300 
gccgo-doc_6.1.0-1_amd64.deb
 550f7d7486c18a30fa366c3ed7164e8a394a0fa93b77cf4051f934bcda40d5c8 5

Bug#825320: marked as done (gcc-doc-defaults: FTBFS in sid: error in 'Version' field string '5:': nothing after colon in version number)

[Debian Bug Tracking System]

Your message dated Sun, 02 Oct 2016 10:29:53 +
with message-id 
and subject line Bug#825320: fixed in gcc-doc-defaults 5:15
has caused the Debian Bug report #825320,
regarding gcc-doc-defaults: FTBFS in sid: error in 'Version' field string '5:': 
nothing after colon in version number
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 ow...@bugs.debian.org
immediately.)


-- 
825320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-doc-defaults
Version: 5:14
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

gcc-doc-defaults FTBFS in curent sid:

   dh_builddeb
dpkg-deb: building package 'gcc-doc' in '../gcc-doc_5.1.0-1_amd64.deb'.
dpkg-deb: building package 'gccgo-doc' in '../gccgo-doc_5.1.0-1_amd64.deb'.
dpkg-deb: building package 'gcj-doc' in '../gcj-doc_5.1.0-1_amd64.deb'.
dpkg-deb: error: parsing file 'debian/gnat-doc/DEBIAN/control' near line 3 
package 'gnat-doc':
 error in 'Version' field string '5:': nothing after colon in version number
dpkg-deb: building package 'gfortran-doc' in 
'../gfortran-doc_5.1.0-1_amd64.deb'.
dh_builddeb: dpkg-deb --build debian/gnat-doc .. returned exit code 2
dpkg-deb: building package 'gcc-doc-base' in '../gcc-doc-base_4.9.2-1_all.deb'.
dpkg-deb: building package 'cpp-doc' in '../cpp-doc_5.1.0-1_amd64.deb'.
debian/rules:100: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2


Andreas


gcc-doc-defaults_5%14.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-doc-defaults
Source-Version: 5:15

We believe that the bug you reported is fixed in the latest version of
gcc-doc-defaults, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 825...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Eremin-Solenikov  (supplier of updated 
gcc-doc-defaults package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Sep 2016 23:48:17 +0300
Source: gcc-doc-defaults
Binary: gcc-doc cpp-doc gfortran-doc gnat-doc gcj-doc gccgo-doc gcc-doc-base
Architecture: source amd64 all
Version: 5:15
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Dmitry Eremin-Solenikov 
Description:
 cpp-doc- documentation for the GNU C preprocessor (cpp)
 gcc-doc- documentation for the GNU compilers (gcc, gobjc, g++)
 gcc-doc-base - several GNU manual pages
 gccgo-doc  - documentation for the GNU Go compiler (gccgo)
 gcj-doc- documentation for the GNU Java tools (gcj, gij)
 gfortran-doc - documentation for the GNU Fortran Compiler (gfortran)
 gnat-doc   - documentation for the GNU Ada Compiler (gnat)
Closes: 794778 825320 833505
Changes:
 gcc-doc-defaults (5:15) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dmitry Eremin-Solenikov ]
   * Updated to 6.1 versions. (Closes: #794778, #833505)
 .
   [ Paul Wise ]
   * Switch from gnatgcc to gnat for version determination due to #839209
 (Closes: #825320)
Checksums-Sha1:
 90df4f7b636b525b3d665a3308edd2da94fa 2261 gcc-doc-defaults_15.dsc
 37a23e03f76994b23c51201ecb358619b07f7a05 30200 gcc-doc-defaults_15.tar.xz
 108ea64cc9923d7150e9f64f8da9988d773a2522 5462 cpp-doc_6.1.0-1_amd64.deb
 6323c80396b53b277e2dade579a8ef3377d526cc 32176 gcc-doc-base_6.1.0-1_all.deb
 70b8a09d2761355bd35cc7b957670539009a7795 5560 gcc-doc_6.1.0-1_amd64.deb
 854e3b6ea66c05a93229761ef1b64dde2535bd6a 5300 gccgo-doc_6.1.0-1_amd64.deb
 d2ababb7312662f0b996108542cd9e84c7c42e58 5528 gcj-doc_6.1.0-1_amd64.deb
 f21be1a1befa07492d553837341b8ed6e855574e 5442 gfortran-doc_6.1.0-1_amd64.deb
 cfc8fdfa0eed3bd273871f8dc00b2ba7262d7610 5450 gnat-doc_6.1.0-1_amd64.deb
Checksums-Sha256:
 3e5f33477575cf78c1e2b7e0a5d0cefef49fcdeddd9de27eeddc85ac4c49a174 2261 
gcc-doc-defaults_15.dsc
 b9cbb0

Processed: Re: gcc-6: fails to build MAME on arm64

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77822
Bug #839249 [gcc-6] gcc-6: fails to build MAME on arm64
Set Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77822'.

-- 
839249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 839598 is forwarded to https://github.com/golang/go/issues/15628

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 839598 https://github.com/golang/go/issues/15628
Bug #839598 [gccgo-6] unable to build gitlab-workhorse with gccgo-6
Set Bug forwarded-to-address to 'https://github.com/golang/go/issues/15628'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
839598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reopen gnat issues

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 748297
Bug #748297 {Done: Debian FTP Masters } 
[gnat-4.9] the libgnatprj and libgnatvsn patches should be upstreamed or dropped
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4.9.4-3+rm.
> reassign 748297 gnat-6
Bug #748297 [gnat-4.9] the libgnatprj and libgnatvsn patches should be 
upstreamed or dropped
Bug reassigned from package 'gnat-4.9' to 'gnat-6'.
No longer marked as found in versions gnat-4.9/4.9.0-1.
Ignoring request to alter fixed versions of bug #748297 to the same values 
previously set
> reopen 748298
Bug #748298 {Done: Debian FTP Masters } 
[gnat-4.9] please drop the sjlj support
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4.9.4-3+rm.
> reassign 748298 gnat-6
Bug #748298 [gnat-4.9] please drop the sjlj support
Bug reassigned from package 'gnat-4.9' to 'gnat-6'.
No longer marked as found in versions gnat-4.9/4.9.0-1.
Ignoring request to alter fixed versions of bug #748298 to the same values 
previously set
> reopen 746689
Bug #746689 {Done: Debian FTP Masters } 
[gnat-4.9] libgnatvsn should have a proper configure.ac and Makefile.in
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4.9.4-3+rm.
> reassign 746689 gnat-6
Bug #746689 [gnat-4.9] libgnatvsn should have a proper configure.ac and 
Makefile.in
Bug reassigned from package 'gnat-4.9' to 'gnat-6'.
Ignoring request to alter found versions of bug #746689 to the same values 
previously set
Ignoring request to alter fixed versions of bug #746689 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
746689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746689
748297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748297
748298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign to gnat-6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 781457 gnat-6
Bug #781457 [src:gcc-5] ada bootstrap failure on mips and mipsel
Bug reassigned from package 'src:gcc-5' to 'gnat-6'.
No longer marked as found in versions gcc-5/5-20150327-1.
Ignoring request to alter fixed versions of bug #781457 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
781457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#838111: marked as done (gcj-6-jre-headless: /usr/bin/gij-6.bin: not found)

[Debian Bug Tracking System]

Your message dated Mon, 10 Oct 2016 04:20:39 +
with message-id 
and subject line Bug#838111: fixed in gcc-6 6.2.0-6
has caused the Debian Bug report #838111,
regarding gcj-6-jre-headless: /usr/bin/gij-6.bin: not found
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 ow...@bugs.debian.org
immediately.)


-- 
838111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcj-6-jre-headless
Version: 6.2.0-4
Severity: normal

Dear Maintainer,

The /usr/bin/gij-6.bin file/link is not installed on hppa.  This causes
vtk6 and libreoffice builds to fail.  See for example:
https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=hppa&ver=1%3A5.2.1-3&stamp=1474103136

checking for posix_fallocate... yes
checking whether to add custom build version... yes, 1:5.2.1-3
/usr/lib/jvm/java-gcj/bin/java: 10: exec: /usr/bin/gij-6.bin: not found
checking the installed JDK... configure: error: JDK is too old, you need at 
least 1.5
Error running configure at ./autogen.sh line 281.
debian/rules:1979: recipe for target 'debian/stampdir/build-arch' failed
make: *** [debian/stampdir/build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Build finished at 2016-09-17T09:03:54Z

Regards,
Dave

-- System Information:
Debian Release: stretch/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.7.4+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gcj-6-jre-headless depends on:
ii  gcc-6-base 6.2.0-4
ii  gcj-6-jre-lib  6.2.0-4
ii  libc6  2.24-2+b1
ii  libgcc41:6.2.0-4
ii  libgcj17   6.2.0-4
ii  prctl  1.6-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

gcj-6-jre-headless recommends no packages.

Versions of packages gcj-6-jre-headless suggests:
ii  fastjar   2:0.98-6
ii  gcj-6-jdk 6.2.0-4
ii  libgcj17-awt  6.2.0-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gcc-6
Source-Version: 6.2.0-6

We believe that the bug you reported is fixed in the latest version of
gcc-6, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 838...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Oct 2016 05:20:07 +0200
Source: gcc-6
Binary: gcc-6-base libgcc1 libgcc1-dbg libgcc2 libgcc2-dbg libgcc-6-dev libgcc4 
libgcc4-dbg lib64gcc1 lib64gcc1-dbg lib64gcc-6-dev lib32gcc1 lib32gcc1-dbg 
lib32gcc-6-dev libn32gcc1 libn32gcc1-dbg libn32gcc-6-dev libx32gcc1 
libx32gcc1-dbg libx32gcc-6-dev gcc-6 gcc-6-multilib gcc-6-test-results 
gcc-6-plugin-dev gcc-6-hppa64-linux-gnu cpp-6 gcc-6-locales g++-6 
g++-6-multilib libgomp1 libgomp1-dbg lib32gomp1 lib32gomp1-dbg lib64gomp1 
lib64gomp1-dbg libn32gomp1 libn32gomp1-dbg libx32gomp1 libx32gomp1-dbg libitm1 
libitm1-dbg lib32itm1 lib32itm1-dbg lib64itm1 lib64itm1-dbg libx32itm1 
libx32itm1-dbg libatomic1 libatomic1-dbg lib32atomic1 lib32atomic1-dbg 
lib64atomic1 lib64atomic1-dbg libn32atomic1 libn32atomic1-dbg libx32atomic1 
libx32atomic1-dbg libasan3 libasan3-dbg lib32asan3 lib32asan3-dbg lib64asan3 
lib64asan3-dbg libx32asan3 libx32asan3-dbg liblsan0 liblsan0-dbg lib32lsan0 
lib32lsan0-dbg libx32lsan0 libx32lsan0-dbg libtsan0 libtsan0-dbg libubsan0 
libubsan0-dbg lib32ubsan0
 lib32ubsan0-dbg lib64ubsan0 lib64ubsan0-dbg libx32ubsan0 libx32ubsan0-dbg 
libcilkrts5 libcilkrts5-dbg lib32cilkrts5 lib32cilkrts5-dbg lib64cilkrts5 
lib64cilkrts5-dbg libx32cilkrts5 libx32cilkrts5-dbg libmpx2 libmpx2-dbg 
lib32mpx2 lib32mpx2-dbg lib64mpx2 lib64mpx2-dbg libquadmath0 libquadmath0-dbg 
lib32quadmath0 lib32quadmath0-dbg lib64quadmath0 lib64quadmath0-dbg 
libx32quadmath0 libx32quadmath0-dbg libcc1-0 libgccjit0 libgccjit0-dbg 
libgccjit-6-doc libgccjit-6-dev gob

Bug#840190: marked as done (provide /usr/bin/go via alternatives)

[Debian Bug Tracking System]

Your message dated Mon, 10 Oct 2016 04:20:39 +
with message-id 
and subject line Bug#840190: fixed in gcc-6 6.2.0-6
has caused the Debian Bug report #840190,
regarding provide /usr/bin/go via alternatives
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 ow...@bugs.debian.org
immediately.)


-- 
840190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: gccgo-6
version: 6.2.0-5
severity: wishlist

Currently gccgo-6 on amd64 only provides /usr/bin/go-6. Providing
/usr/bin/go via alternatives will make it easy to test building against
gccgo-6 on amd64.

Architectures like powerpc only has gccgo-6 and we need to test building
our packages with gccgo-6. Currently we have to manually add a symlink
to test building against gccgo-6.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gcc-6
Source-Version: 6.2.0-6

We believe that the bug you reported is fixed in the latest version of
gcc-6, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Oct 2016 05:20:07 +0200
Source: gcc-6
Binary: gcc-6-base libgcc1 libgcc1-dbg libgcc2 libgcc2-dbg libgcc-6-dev libgcc4 
libgcc4-dbg lib64gcc1 lib64gcc1-dbg lib64gcc-6-dev lib32gcc1 lib32gcc1-dbg 
lib32gcc-6-dev libn32gcc1 libn32gcc1-dbg libn32gcc-6-dev libx32gcc1 
libx32gcc1-dbg libx32gcc-6-dev gcc-6 gcc-6-multilib gcc-6-test-results 
gcc-6-plugin-dev gcc-6-hppa64-linux-gnu cpp-6 gcc-6-locales g++-6 
g++-6-multilib libgomp1 libgomp1-dbg lib32gomp1 lib32gomp1-dbg lib64gomp1 
lib64gomp1-dbg libn32gomp1 libn32gomp1-dbg libx32gomp1 libx32gomp1-dbg libitm1 
libitm1-dbg lib32itm1 lib32itm1-dbg lib64itm1 lib64itm1-dbg libx32itm1 
libx32itm1-dbg libatomic1 libatomic1-dbg lib32atomic1 lib32atomic1-dbg 
lib64atomic1 lib64atomic1-dbg libn32atomic1 libn32atomic1-dbg libx32atomic1 
libx32atomic1-dbg libasan3 libasan3-dbg lib32asan3 lib32asan3-dbg lib64asan3 
lib64asan3-dbg libx32asan3 libx32asan3-dbg liblsan0 liblsan0-dbg lib32lsan0 
lib32lsan0-dbg libx32lsan0 libx32lsan0-dbg libtsan0 libtsan0-dbg libubsan0 
libubsan0-dbg lib32ubsan0
 lib32ubsan0-dbg lib64ubsan0 lib64ubsan0-dbg libx32ubsan0 libx32ubsan0-dbg 
libcilkrts5 libcilkrts5-dbg lib32cilkrts5 lib32cilkrts5-dbg lib64cilkrts5 
lib64cilkrts5-dbg libx32cilkrts5 libx32cilkrts5-dbg libmpx2 libmpx2-dbg 
lib32mpx2 lib32mpx2-dbg lib64mpx2 lib64mpx2-dbg libquadmath0 libquadmath0-dbg 
lib32quadmath0 lib32quadmath0-dbg lib64quadmath0 lib64quadmath0-dbg 
libx32quadmath0 libx32quadmath0-dbg libcc1-0 libgccjit0 libgccjit0-dbg 
libgccjit-6-doc libgccjit-6-dev gobjc++-6 gobjc++-6-multilib gobjc-6 
gobjc-6-multilib libobjc-6-dev lib64objc-6-dev lib32objc-6-dev libn32objc-6-dev 
libx32objc-6-dev libobjc4 libobjc4-dbg lib64objc4 lib64objc4-dbg lib32objc4 
lib32objc4-dbg libn32objc4 libn32objc4-dbg libx32objc4 libx32objc4-dbg 
gfortran-6 gfortran-6-multilib libgfortran-6-dev lib64gfortran-6-dev 
lib32gfortran-6-dev libn32gfortran-6-dev libx32gfortran-6-dev libgfortran3 
libgfortran3-dbg lib64gfortran3 lib64gfortran3-dbg lib32gfortran3 
lib32gfortran3-dbg libn32gfortran3
 libn32gfortran3-dbg libx32gfortran3 libx32gfortran3-dbg gccgo-6 
gccgo-6-multilib libgo9 libgo9-dbg lib64go9 lib64go9-dbg lib32go9 lib32go9-dbg 
libn32go9 libn32go9-dbg libx32go9 libx32go9-dbg gcj-6 gcj-6-jdk 
gcj-6-jre-headless gcj-6-jre libgcj17 gcj-6-jre-lib libgcj17-awt libgcj17-dev 
libgcj17-dbg gcj-6-source libgcj-doc libstdc++6 lib32stdc++6 lib64stdc++6 
libn32stdc++6 libx32stdc++6 libstdc++-6-dev libstdc++-6-pic libstdc++6-6-dbg 
lib32stdc++-6-dev lib32stdc++6-6-dbg lib64stdc++-6-dev lib64stdc++6-6-dbg 
libn32stdc++-6-dev libn32stdc++6-6-dbg libx32stdc++-6-dev libx32stdc++6-6-dbg 
libstdc++-6-doc gnat-6 gnat-6-sjlj libgnat-6 libgnat-6-dbg libgnatvsn6-dev 
libgnatvsn6 libgnatvsn6-dbg libgnatprj6-dev libgnatprj6 libgnatprj6-dbg gdc-6 
gdc-6-multilib libphobos-6-dev lib64phobos-6-dev lib32phobos-6-dev 
libx32phobos-6-dev fixincludes
 gcc-6

Bug#839995: marked as done (g++-6: g++6 fails to compile files that include /usr/include/c++/6/bits/locale_conv.h)

[Debian Bug Tracking System]

Your message dated Mon, 10 Oct 2016 07:39:03 +0200
with message-id <6836f07f-af86-e244-5be7-6243e1cd6...@debian.org>
and subject line Re: Bug#839995: g++-6: g++6 fails to compile files that 
include /usr/include/c++/6/bits/locale_conv.h
has caused the Debian Bug report #839995,
regarding g++-6: g++6 fails to compile files that include 
/usr/include/c++/6/bits/locale_conv.h
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 ow...@bugs.debian.org
immediately.)


-- 
839995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: g++-6
Version: 6.2.0-5
Severity: important
Tags: upstream

Dear Maintainer,

Trying to compile libgtop11dotnet-2.2.0.12 for a gemalto pki, i have a
build error that has nothing to do with the packages itself but
with the content of /usr/include/c++/6/bits/locale_conv.h
and especially the __out temporary variable used in some of its inline.

It is not related to libgtop11dotnet-2.2.0.13 code epr se as I have found
complains for the same problem on various c++ code with g++ 6.

I will attach a standalone file that shows the problem and a possible fix.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.23 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages g++-6 depends on:
ii  gcc-66.2.0-5
ii  gcc-6-base   6.2.0-5
ii  libc62.24-3
ii  libgmp10 2:6.1.1+dfsg-1
ii  libisl15 0.17.1-1
ii  libmpc3  1.0.3-1
ii  libmpfr4 3.1.5-1
ii  libstdc++-6-dev  6.2.0-5
ii  zlib1g   1:1.2.8.dfsg-2+b1

g++-6 recommends no packages.

Versions of packages g++-6 suggests:
pn  g++-6-multilib
pn  gcc-6-doc 
pn  libstdc++6-6-dbg  

-- no debconf information
--- End Message ---
--- Begin Message ---
On 07.10.2016 10:49, Eric Valette wrote:
> Package: g++-6
> Version: 6.2.0-5
> Severity: important
> Tags: upstream
> 
> Dear Maintainer,
> 
> Trying to compile libgtop11dotnet-2.2.0.12 for a gemalto pki, i have a
> build error that has nothing to do with the packages itself but
> with the content of /usr/include/c++/6/bits/locale_conv.h
> and especially the __out temporary variable used in some of its inline.
> 
> It is not related to libgtop11dotnet-2.2.0.13 code epr se as I have found
> complains for the same problem on various c++ code with g++ 6.
> 
> I will attach a standalone file that shows the problem and a possible fix.


upstream replied (https://gcc.gnu.org/PR77913):

(In reply to Andrew Pinski from comment #3)
> This is a bug in libgtop11dotnet:
>
>
> ./cardmod.h:#define __out
> ./cardmod.h:#define __out_bcount_part_opt(x, y)
> ./cardmod.h:#define __out_bcount(x)
> ./cardmod.h:#define __out_opt
>
>
> __ is in the implementation namespace but they are abusing it.

Basically they are trying to compile the sources under both MSVC++ and GCC but
default to MSVC++'s source style in a way it is undefined for other compilers.--- End Message ---

Processed: Re: unable to build gitlab-workhorse with gccgo-6

[Debian Bug Tracking System]

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 problems

Processed: found 840360 in 20160807-1, tagging 840360

[Debian Bug Tracking System]

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 fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840360: marked as done (Multiple security issues)

[Debian Bug Tracking System]

Your message dated Tue, 11 Oct 2016 07:54:51 +
with message-id 
and subject line Bug#840360: fixed in libiberty 20161011-1
has caused the Debian Bug report #840360,
regarding Multiple security issues
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 ow...@bugs.debian.org
immediately.)


-- 
840360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.debian.org/tracker/CVE-2016-4492
https://security-tracker.debian.org/tracker/CVE-2016-4491
https://security-tracker.debian.org/tracker/CVE-2016-4490
https://security-tracker.debian.org/tracker/CVE-2016-4489
https://security-tracker.debian.org/tracker/CVE-2016-4488
https://security-tracker.debian.org/tracker/CVE-2016-4487
https://security-tracker.debian.org/tracker/CVE-2016-2226

These are all fixed in trunk since 2016-08-04, the source
package currently in sid as libiberty-20160807 does not
contain those, though.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: libiberty
Source-Version: 20161011-1

We believe that the bug you reported is fixed in the latest version of
libiberty, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libiberty package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 11 Oct 2016 09:14:23 +0200
Source: libiberty
Binary: libiberty-dev
Architecture: source
Version: 20161011-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Description:
 libiberty-dev - library of utility functions used by GNU programs
Closes: 840360
Changes:
 libiberty (20161011-1) unstable; urgency=medium
 .
   * Update to 20161011 (security issues fixed: CVE-2016-6131, CVE-2016-4493,
 CVE-2016-4492, CVE-2016-4491, CVE-2016-4490, CVE-2016-4489, CVE-2016-4488,
 CVE-2016-4487, CVE-2016-2226. Closes: #840360.
Checksums-Sha1:
 ecafd1e17948e885b833b039cfd0b5a7d4e3b9ae 1806 libiberty_20161011-1.dsc
 542e22ca5830563a4d13e6f79e94144f2b98b37b 1109668 libiberty_20161011.orig.tar.xz
 95b46e0135544646d9f03fc19cd276a3c4a0e956 4172 
libiberty_20161011-1.debian.tar.xz
Checksums-Sha256:
 a1c1fb386ea00fddd82688b1395ace73cee19e4f86b05325feae9897cabaf438 1806 
libiberty_20161011-1.dsc
 1b0ad63bcb38f1f9bb877acc293a9094d48e8607ff1324bbf53f368467bf23da 1109668 
libiberty_20161011.orig.tar.xz
 703e986b4bec32adab169598c20c23905d0eeb769476b89ecfa7ea2cf1676c37 4172 
libiberty_20161011-1.debian.tar.xz
Files:
 2cf1062a3289a747c3c41688af2a1548 1806 libdevel optional 
libiberty_20161011-1.dsc
 d5f21102233461c94bff933a42d52740 1109668 libdevel optional 
libiberty_20161011.orig.tar.xz
 ad8aa219c3ee9581cdc46d1c846ae7a9 4172 libdevel optional 
libiberty_20161011-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQItBAEBCAAXBQJX/JJQEBxkb2tvQGRlYmlhbi5vcmcACgkQvX6qYHePpvU0GQ//
VNth/7kST3+JFFnVsLpUQC0apyGfcqCVyiOpdV/KcNeuHRyW6BB75ayzHqEg0rbY
VoGeaKYOKni6nOZ9E5yvQUKuqXmUfZtJaD7vr8qxR7VqoYI+RkKrY05EHPM7QRRo
P5U2OKwyxxXilaeoZgHefcFhN2qKP0boGFNUJ+LxHUk/zjhjIgB7pS0YJRvPibG9
Ll+nbjxZhoCm0Ge2fXHSiuTjmGaPZGUe6CSNCnhkyx2ZP6nGtriUHJTON4CmeajI
jAwrj9U7/qQevYTm4E3ZLFPPgXq5A2nTHUc8nfmY1HM/Uyy3fbLvJxXCIpRXsZkX
cGrpIeYyEDIWk2pKQuDxE34J8itieW5ekZvoddUbUclDB0Rl+EPqypseMMRJ5f0Y
EmeySDbrWLlw8ZfVsDsUIdEC9Y+3TJiu689or6l9p463+2gP3Fj4khCjrbH9aX0G
9aqx+J1sJftby4NngKD5TlWg6hxho0+dXxHOKenkyC0IZsPhpVILgL/YZtpwjzHT
frhehnPpZbAh8VVu/7yrmI6R5kwYrTZbFWry3nfnWK30Pk2fmsu3YQPYJrHWW0l7
W7UYkJrE741Os9uEixG+P37+CmICvsZ+6TcA7QLGB7wBgdtR7ArHU0eHhUSPQUX4
0oiSeNxxmNufQ/dRfBAuZzcUSCNIyqYVTJGL5dRmAS4=
=2oRQ
-END PGP SIGNATURE End Message ---

Processed: motif: FTBFS: relocation R_X86_64_PC32 against symbol `exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 840394 by 837658
Bug #840394 [src:motif] motif: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
840394 was not blocked by any bugs.
840394 was not blocking any bugs.
Added blocking bug(s) of 840394: 837658
> block 837658 by 835148
Bug #837658 [libfl-dev] libfl-dev: Please build libfl_pic.a with -fPIC
837658 was not blocked by any bugs.
837658 was blocking: 840394
Added blocking bug(s) of 837658: 835148
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837658
840394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#840574: Please backport libgo fixes for sparc64

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + help
Bug #840574 [src:gcc-6] Please backport libgo fixes for sparc64
Added tag(s) help.
> tags -1 - patch
Bug #840574 [src:gcc-6] Please backport libgo fixes for sparc64
Removed tag(s) patch.

-- 
840574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: diff NMU for libiberty_20161011-1.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 840889 +pending
Bug #840889 [src:libiberty] CVE-2016-4491 and CVE-2016-6131 not fixed in 
libiberty_20161011-1
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 840889 in 20141014-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 840889 20141014-1
Bug #840889 [src:libiberty] CVE-2016-4491 and CVE-2016-6131 not fixed in 
libiberty_20161011-1
Marked as found in versions libiberty/20141014-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#840574: Please backport libgo fixes for sparc64

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - help + patch
Bug #840574 [src:gcc-6] Please backport libgo fixes for sparc64
Removed tag(s) help.
Bug #840574 [src:gcc-6] Please backport libgo fixes for sparc64
Added tag(s) patch.

-- 
840574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems