Re: Accepted gcc-defaults 1.118 (source all amd64)
On 08.05.2012 14:44, Cyril Brulebois wrote:
> Matthias Klose <email@example.com> (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 affect other ongoing transitions.
> Wrong. At least strigi, gnome-commander, and hugin are getting hit.
stop blaming the compiler for unrelated build failures. You did so already
<mbiebl> awesome, libchamplain ftbfs with an ICE in gcc-4.7
<mbiebl> yeah for switching the default compiler
<KiBi> doko: It looks like I'm going to take up your offer. Please fix that.
<mbiebl> doko: you have your first problem of gcc-4.7 breaking an ongoing
<adsb> mbiebl: that might be the gmp10 bug
<doko> 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.
strigi was fixed, the gnome-commander and hugin builds were both tried on
brahms (and did succeed on other architectures).
> What's worse is that at least for the last two, there were no gcc 4.7 bug
> reports for them! And don't tell me thins changed for them, since hugin is
> getting his *fourth* binNMU in a row.
no, because it's a buildd issue, or an gmp issue, afaics. Again, please don't
blame the compiler if you can't explain a build failure.
so what is the status of brahms?
> You're making our job difficult. It's really ***NOT*** appreciated.
well, not deciding on the release architectures for over a year now makes my
job difficult as well. still trying to get it done.