Bug#431014: Why won't you ship /usr/bin/gcc-snapshot?

2011-12-31 Thread Vincent Lefevre
On 2011-12-31 14:00:04 -0600, Jonathan Nieder wrote: > Vincent Lefevre wrote: > > > At runtime? Do you mean that one needs to change the library path > > also for running the generated executable? > > Yes, gcc-snapshot includes a snapshot of libgcc (and libstdc++, > libgcj, libobjc, etc). So che

Bug#431014: Why won't you ship /usr/bin/gcc-snapshot?

2011-12-31 Thread Jonathan Nieder
Vincent Lefevre wrote: > At runtime? Do you mean that one needs to change the library path > also for running the generated executable? Yes, gcc-snapshot includes a snapshot of libgcc (and libstdc++, libgcj, libobjc, etc). So checking those libraries' behavior involves modifying the library path

Bug#431014: Why won't you ship /usr/bin/gcc-snapshot?

2011-12-31 Thread Vincent Lefevre
On 2011-12-31 17:04:19 +0100, Matthias Klose wrote: > A wrapper will never remind you using the new library paths at runtime. At runtime? Do you mean that one needs to change the library path also for running the generated executable? The README.Debian file doesn't say anything like that. Accordin

Bug#653002: marked as done (G++-4.6: internal compiler error: Segmentation fault (works on 4.5)segfault))

2011-12-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Dec 2011 17:50:04 +0100 with message-id <4eff3d3c.9010...@debian.org> and subject line Re: G++-4.6: internal compiler error: Segmentation fault (works on 4.5)segfault) has caused the Debian Bug report #653002, regarding G++-4.6: internal compiler error: Segmentation faul

Bug#431014: Why won't you ship /usr/bin/gcc-snapshot?

2011-12-31 Thread Matthias Klose
On 12/31/2011 01:34 AM, Vincent Lefevre wrote: > On 2011-12-30 17:15:00 -0600, Jonathan Nieder wrote: >> No, I mean that packagers can but should not use >> >> Build-Depends: gcc-snapshot >> >> CC = gcc-snapshot >> >> "Don't do that, then." you might say. But not providing a >> /usr/bin/

gcc-4.7_4.7-20111231-1_amd64.changes ACCEPTED into experimental

2011-12-31 Thread Debian FTP Masters
Accepted: cpp-4.7-doc_4.7-20111231-1_all.deb to main/g/gcc-4.7/cpp-4.7-doc_4.7-20111231-1_all.deb cpp-4.7_4.7-20111231-1_amd64.deb to main/g/gcc-4.7/cpp-4.7_4.7-20111231-1_amd64.deb fixincludes_4.7-20111231-1_amd64.deb to main/g/gcc-4.7/fixincludes_4.7-20111231-1_amd64.deb g++-4.7

Processing of gcc-4.7_4.7-20111231-1_amd64.changes

2011-12-31 Thread Debian FTP Masters
gcc-4.7_4.7-20111231-1_amd64.changes uploaded successfully to localhost along with the files: gcc-4.7_4.7-20111231-1.dsc gcc-4.7_4.7-20111231.orig.tar.gz gcc-4.7_4.7-20111231-1.diff.gz gcc-4.7-source_4.7-20111231-1_all.deb cpp-4.7-doc_4.7-20111231-1_all.deb libstdc++6-4.7-doc_4.7

Re: please update patches / investigate build failures for gcc-4.7 snapshot builds

2011-12-31 Thread Konstantinos Margaritis
On 19 December 2011 14:55, Konstantinos Margaritis wrote: > On 19 December 2011 01:55, Matthias Klose wrote: >> Please have a look at the gcc-4.7 package in experimental, update patches >> (hurd, >> kfreebsd, ARM is fixed in svn), and investigate the build failures (currently >> ia64, but more w