Bug#652856: g++-4.6: g++-4.5/4.6 does not call update-alternatives for a "g++" link

2011-12-20 Thread Brendan Byrd
Package: g++-4.6 Version: 4.6.2-7 Severity: normal Installation of both or either g++-4.5/4.6 will not provide a direct link to "g++". The command is called g++-4.X, which won't be auto-detected by programs like configure. The packages should use update-alternatives, just like gcc already does.

Bug#652735: fixed

2011-12-20 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following changes were made to the overrides... Concerning package lib32stdc++6... Operating on the unstable suite Changed priority from optional to extra Thank you for reporting the bug, which will now be closed. If you have further commen

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

2011-12-20 Thread Hiroyuki Yamamoto
Hi, On ppc64, both packages of gcc-4.7 (4.7-20111217-2) and gcj-4.7 (4.7-20111217-1) were built without any problem. 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 (c

Processed: mudflap is not further developed

2011-12-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 479390 + wontfix Bug #479390 [libmudflap0] libmudflap0 doesn't wrap memalign Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 479390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47939

Bug#487078: marked as done (warning: will never be executed)

2011-12-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Dec 2011 14:40:57 +0100 with message-id <4ef09069.9030...@debian.org> and subject line not seen with g++-4.6 has caused the Debian Bug report #487078, regarding warning: will never be executed to be marked as done. This means that you claim that the problem has been deal

Bug#551188: marked as done ("libgomp: Thread creation failed" after stack size limit increase)

2011-12-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Dec 2011 14:36:44 +0100 with message-id <4ef08f6c.1070...@debian.org> and subject line Re: Bug#551188: "libgomp: Thread creation failed" after stack size limit increase has caused the Debian Bug report #551188, regarding "libgomp: Thread creation failed" after stack size

Bug#542794: marked as done (libgomp1: Throwing exceptions segfaults when libgomp is being dlopen'ed through python-vipscc)

2011-12-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Dec 2011 14:34:55 +0100 with message-id <4ef08eff.3010...@debian.org> and subject line Re: Bug#542794: Test case has caused the Debian Bug report #542794, regarding libgomp1: Throwing exceptions segfaults when libgomp is being dlopen'ed through python-vipscc to be marked

Bug#610291: marked as done (libgfortran: /usr/bin/ld: cannot find -lgfortran)

2011-12-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Dec 2011 14:29:06 +0100 with message-id <4ef08da2.20...@debian.org> and subject line Re: Bug#610291: libgfortran: /usr/bin/ld: cannot find -lgfortran has caused the Debian Bug report #610291, regarding libgfortran: /usr/bin/ld: cannot find -lgfortran to be marked as done

Bug#603113: marked as done (libstdc++6: SIGSEGV in sort(rndit, rndit,cmp) with cmp modifying vector outside boundaries)

2011-12-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Dec 2011 14:30:54 +0100 with message-id <4ef08e0e.9050...@debian.org> and subject line Re: Bug#603113: all my apologies has caused the Debian Bug report #603113, regarding libstdc++6: SIGSEGV in sort(rndit, rndit,cmp) with cmp modifying vector outside boundaries to be ma

Bug#629930: marked as done (libstdc++6: 4.6.0-12 breaks something in /lib64/*)

2011-12-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Dec 2011 14:22:13 +0100 with message-id <4ef08c05.3000...@debian.org> and subject line Re: Bug#629930: libstdc++6: 4.6.0-12 breaks something in /lib64/* has caused the Debian Bug report #629930, regarding libstdc++6: 4.6.0-12 breaks something in /lib64/* to be marked as

Bug#651550: libstdc++6 4.6.1-4 breaks libstdc++6-4.4-dev 4.4.5-8 but doesn't "conflict" with it

2011-12-20 Thread Matthias Klose
On 12/09/2011 08:52 PM, Joerg Schneider wrote: > This could be fixed by adding a "Conflicts" dependency for > libstdc++6-4.4-dev to libstdc++6, which prevents the installation of > incompatible versions. libgcc1 has: Breaks: gcc-4.1, gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-