Subject: Mir's not building

From: Daniel van Vugt <[email-masked]>
Date: Wed, 12 Aug 2015 12:16:06 +0800

Mir does not build on a fully updated wily system today. This is 
expected as the whole archive is "transitioning" (rebuilding) to GCC 5 
and a new C++ ABI.

A workaround for the time being is:
    cmake .. -DCMAKE_CXX_COMPILER=g++-4.9 -DCMAKE_C_COMPILER=gcc-4.9
or clang of course.

You can monitor the progress of the transition here:
    http://people.canonical.com/~ubuntu-archive/transitions/

Looks like we should be unblocked and over this problem by tomorrow.

- Daniel

---

From: Daniel van Vugt <[email-masked]>
Date: Wed, 12 Aug 2015 14:30:44 +0800

This also means autolandings won't work. So best to hold off any top 
approvals till wily is updated and working again.

---

From: Daniel van Vugt <[email-masked]>
Date: Fri, 14 Aug 2015 11:59:44 +0800

OK, this is a bit messy. Mir still doesn't build on wily.

There is already a fix for the protobuf issue that was holding us up, 
but I'm not sure if it's the permanent solution. The fix is to use the 
new "v5" protobuf packages in wily-proposed:
   https://launchpad.net/ubuntu/+source/protobuf

But even if you manage to wedge them into your system, the Mir build 
gets a bit further and stops on similar issues with libboost*, which 
apparently isn't transitioned yet. But now I'm not really sure what that 
means...
   http://people.canonical.com/~ubuntu-archive/transitions/

So shifting to the new C++ ABI in GCC 5 is a mess for Mir right now. Not 
sure if it will just fix itself when all the transitions are complete or 
if we need to change something in Mir (like moving to boost 1.58).

The workaround continues to work though:
   cmake .. -DCMAKE_CXX_COMPILER=g++-4.9 -DCMAKE_C_COMPILER=gcc-4.9

- Daniel

---

From: Christopher James Halse Rogers <[email-masked]>
Date: Fri, 14 Aug 2015 14:19:48 +1000

On Fri, Aug 14, 2015 at 1:59 PM, Daniel van Vugt 
<[email-masked]> wrote:
> but I'm not sure if it's the permanent solution. The fix is to use 
> the new "v5" protobuf packages in wily-proposed:
> apparently isn't transitioned yet. But now I'm not really sure what 
> that means...
> So shifting to the new C++ ABI in GCC 5 is a mess for Mir right now. 
> Not sure if it will just fix itself when all the transitions are 
> complete or if we need to change something in Mir (like moving to 
> boost 1.58).

a) This should fix itself once the transitions are over.
b) Once the transitions are over Mir will be built against boost 1.58 
anyway (boost-defaults are changing, so libboost-dev points to 1.58 
instead of 1.55).