Re: Accepted gcc-defaults 1.118 (source all amd64)

On 08.05.2012 19:14, Cyril Brulebois wrote: > Matthias Klose (08/05/2012): >> mbiebl: that might be the gmp10 bug KiBi, can't reproduce >> the libchamplain ICE locally. could you do a local build as well? >> >> and I didn't get a reply on that. > > Because, if you didn't get the memo, we're tr

Re: Accepted gcc-defaults 1.118 (source all amd64)

Matthias Klose (08/05/2012): > stop blaming the compiler for unrelated build failures. You did so already > yesterday: > > awesome, libchamplain ftbfs with an ICE in gcc-4.7 > yeah for switching the default compiler > doko: It looks like I'm going to take up your offer. Please fix that. > dok

Re: Accepted gcc-defaults 1.118 (source all amd64)

On 08.05.2012 17:55, Matthias Klose wrote: stop blaming the compiler for unrelated build failures. You did so already yesterday: awesome, libchamplain ftbfs with an ICE in gcc-4.7 yeah for switching the default compiler doko: It looks like I'm going to take up your offer. Please fix that.

Re: Accepted gcc-defaults 1.118 (source all amd64)

Matthias Klose (08/05/2012): > mbiebl: that might be the gmp10 bug > KiBi, can't reproduce the libchamplain ICE locally. could you do a > local build as well? > > and I didn't get a reply on that. Because, if you didn't get the memo, we're trying to get packages built, which we finally managed

Re: Accepted gcc-defaults 1.118 (source all amd64)

On Tue, May 8, 2012 at 18:55:49 +0200, Matthias Klose wrote: > awesome, libchamplain ftbfs with an ICE in gcc-4.7 > yeah for switching the default compiler > doko: It looks like I'm going to take up your offer. Please fix that. > doko: you have your first problem of gcc-4.7 breaking an ongoin

Re: Accepted gcc-defaults 1.118 (source all amd64)

On Tue, May 8, 2012 at 18:55:49 +0200, Matthias Klose wrote: > strigi was fixed, the gnome-commander and hugin builds were both tried on > brahms (and did succeed on other architectures). > Other architectures didn't switch to 4.7. > > What's worse is that at least for the last two, there were

Re: Accepted gcc-defaults 1.118 (source all amd64)

On 08.05.2012 14:44, Cyril Brulebois wrote: > Matthias Klose (07/05/2012): >> see my email to -release. It's ahead of the freeze, and the fix rate for >> the build failures shows that all these issues can be fixed even before >> the freeze. It is not a transition which requires binNMU's itself (ex

Processed (with 2 errors): gnat-4.6: intermittent FTBFS, race condition in Makefiles with too many parallel processes

Processing commands for cont...@bugs.debian.org: > retitle 667184 gnat-4.6: intermittent FTBFS, race condition in Bug #667184 [gnat-4.6] gnat-4.6: ftbfs with GCC-4.7 Changed Bug title to 'gnat-4.6: intermittent FTBFS, race condition in' from 'gnat-4.6: ftbfs with GCC-4.7' > gnattools/Makefile Unk

Bug#667184: gnat-4.6: intermittent FTBFS, race condition in Makefiles with too many parallel processes

retitle 667184 gnat-4.6: intermittent FTBFS, race condition in gnattools/Makefile severity 667184 important user debian-gcc@lists.debian.org usertags - ftbfs-gcc-4.7 thanks This bug has nothing to do with gcc-4.7. Analysis of the full log file reveals that the bootstrap used 10 parallel processe

Re: GCC 4.7 is now the default for x86 architectures

Hi, Matthias Klose wrote: > On 07.05.2012 19:35, Thorsten Glaser wrote: >> Matthias Klose dixit: >> >>> GCC 4.7 is now the default for x86 architectures for all frontends except >>> the D >>> frontends, including KFreeBSD and the Hurd. >> >> How are the plans for other architectures? About ppc64

Re: Accepted gcc-defaults 1.118 (source all amd64)

Matthias Klose (07/05/2012): > see my email to -release. It's ahead of the freeze, and the fix rate for the > build failures shows that all these issues can be fixed even before the > freeze. It is not a transition which requires binNMU's itself (except for the > libobjc stuff), and shouldn't affe