touch-packages team mailing list archive

[Alan Griffiths <1418962@xxxxxxxxxxxxxxxxxx>]

There are a number of reasons for not fixing and "the team has decided
to move to C++14 instead" is not one of them.

Trusty has out of date versions of a number of build dependencies:
android headers, gmock and g++ all cause problems. There are also binary
compatibility issues between g++4.8 and g++4.9 (which led to distro
fixing Mir and relating projects to g++4.9 - which we know will cause
problems).

We've accepted some workarounds for bugs in g++4.8 that got fixed in 4.9
(and clang) but we don't want to get into supporting old versions of
dependencies that we are not set up to test properly.

It is possible to install g++4.9 on trusty, which solves both bugs in
4.8 and allows for use of C++14:

https://launchpad.net/~ubuntu-
toolchain-r/+archive/ubuntu/test?field.series_filter=trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1418962

Title:
  Mir is not building in trusty

Status in Mir:
  Won't Fix
Status in mir package in Ubuntu:
  New

Bug description:
  Trying to compile mir in trusty, using gcc-4.8 fails, mostly due to
  the initialization lists with curly brackets.

  Attached patch fixes them, but them I'm getting a weird linking issue
  (not happening with clang), that I wasn't experiencing some weeks ago
  (when the demo shell was in examples I think):

  [100%] Built target mirserver
  Linking CXX executable ../../bin/.mir_proving_server-uninstalled
  CMakeFiles/mir_proving_server.dir/demo_shell.cpp.o: in function "mir::DefaultServerConfiguration::~DefaultServerConfiguration()":
  /home/marco/Dev/mir-ports/mir/src/include/server/mir/default_server_configuration.h:159: invalid reference to "vtable for mir::DefaultServerConfiguration"
  /home/marco/Dev/mir-ports/mir/src/include/server/mir/default_server_configuration.h:159: invalid reference to "vtable for mir::DefaultServerConfiguration"
  collect2: error: ld returned 1 exit status

  Installing the rest (libs, example clients, example servers) works as
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1418962/+subscriptions