On Fri, Aug 14, 2015 at 1:59 PM, Daniel van Vugt
<daniel.van.v...@canonical.com> wrote:
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).
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).
--
Mir-devel mailing list
Mir-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/mir-devel
