please fix build failures, including those introduced by GCC 5

Clint Byrum clint at
Thu Mar 5 08:16:13 UTC 2015

MySQL will be fixed by an upload of 5.5.42, which has security fixes and
so should be done anyway. I'll try and coordinate that with the usual

Excerpts from Matthias Klose's message of 2015-03-04 15:12:05 -0800:
> Hi,
> two test rebuilds for vivid are almost finished on all architectures (pending
> powerpc and arm64).  It's time to address the build failures seen with these
> test rebuilds.  The most important ones are listed in [1] for the vivid
> archives.  These really have to be addressed.
> In preparation for the w-series (15.10), there was another test rebuild using
> GCC 5 (yes, GCC 5 will be the default for 15.10, without any possibility to fall
> back to older g++ and gfortran versions).  Some outfall as usual [2].  I think
> the switch to GCC 5 will cause a bit more work than the switch to GCC 4.9 in
> utopic, so I would like to address as many issues as possible before the switch,
> even during the preparation of the 15.04 (vivid) release.  Safe uploads to vivid
> would be appreciated.  To check for buildability with GCC 5, add the
> ubuntu-toolchain-r/test PPA [3] to your apt sources.  If you have time to kill,
> please fix these issues now.  Make sure to forward fixes to the Debian bug
> tracker, bugs were filed for a Debian test rebuild as well [4].  Help for
> porting issues can be found in the GCC 5 porting notes [5] and an analysis of a
> test rebuild for another distro [6].
> If you can't, or if you don't want to do an upload, please make sure to file a
> launchpad issue, and tag it with 'ftbfs' and probably 'patch', then the issue
> will show up in [1] and [2].
> Help would be appreciated to fix issues in packages like boost so that we can
> get more reliable test rebuild results.
> Thanks, Matthias
> [1]
> [2]
> [3]
> [4]
> [5]
> [6]

More information about the Ubuntu-devel-discuss mailing list