Hello, W dniu 16.07.2015 o 09:26, Steve Langasek pisze: > Hi all, > > As Matthias posted about on ubuntu-devel last week[1], we are facing a > transition with the update to gcc 5 in wily. Many C++ libraries will need > rebuilds for an ABI transition due to changes in the C++11 support in gcc 5. > > We have a silo in progress for this, so that this transition can be staged > in a way that's minimally disruptive to the phone builds in wily, but we > need the phone team's help this transition complete in a timely fashion. > There are a number of bug reports filed a while ago for packages that have > build-dependencies on g++-4.9, and need to be updated. The bugs are here: > > https://bugs.launchpad.net/ubuntu/+bugs?field.tag=lsd-cxx11 > > the full list of affected packages is: > > dbus-cpp > indicator-datetime > indicator-display > indicator-location > indicator-network > indicator-transfer > location-service > media-hub > mediascanner2 > mir > net-cpp > platform-api > process-cpp > qtmir > qtmir-gles > trust-store > unity-api > unity-scope-mediascanner > unity-scopes-api > unity-system-compositor > unity8 > > The bugs are now marked critical, and there's good progress on a number of > them with merge proposals raised, but we need these to be fixed as soon as > possible; because once fixed, we will need to see which of these packages > fail to build with gcc 5. There are already a number of packages failing to > build, which will need to be fixed up as shown in the silo ppa: > > > https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016/+packages > > And once the above packages have been adjusted not to use g++-4.9, we may > see a few more build failures. > > We'll prepare a list of all failing packages shortly to discuss with the > responsible teams, but in the meantime if you want to get started on fixing > the build failures shown there, there's no time like the present! > > Thanks, > > >
One thing we need to think about here is what changes do those touch projects require to become gcc-5 compatible. Most projects currently dual-land to vivid and wily and I suppose every lander would like that to stay this way - as branching to two trunks means trouble for both the developers and train operators. I wonder it it'll be possible to still keep that compatibility for everything. I'll try to help out as much as I can next week. Cheers, -- Łukasz 'sil2100' Zemczak Foundations Team [email protected] www.canonical.com -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
