[regression] unity-system-compositor FTBFS against Mir 0.6/0.7: undefined reference to `...@MIR_CLIENT_8'

Bug #1355021 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Critical
Mir development team
0.6
Fix Released
Critical
Mir development team
Unity System Compositor
Invalid
Critical
Unassigned
mir (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

unity-system-compositor can't build against Mir 0.6/0.7: undefined reference to `...@MIR_CLIENT_8'

I've tried with both the usc trunk and devel-next branches. Neither is buildable any more...

Linking CXX executable ../bin/unity-system-compositor
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_horizontal_resize_cursor_name@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_connection_create_display_config@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_surface_is_valid@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_connection_create_surface_sync@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_connection_set_display_config_change_callback@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_surface_get_egl_native_window@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_closed_hand_cursor_name@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_vsplit_resize_cursor_name@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_pointing_hand_cursor_name@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_omnidirectional_resize_cursor_name@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_vertical_resize_cursor_name@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_hsplit_resize_cursor_name@MIR_CLIENT_8'
/home/dan/mir.toy/lib/x86_64-linux-gnu/libmirserver.so: undefined reference to `mir_busy_cursor_name@MIR_CLIENT_8'

Tags: rtm14

Related branches

Changed in mir:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 0.7.0
Changed in mir:
assignee: nobody → Daniel van Vugt (vanvugt)
Changed in unity-system-compositor:
assignee: nobody → Daniel van Vugt (vanvugt)
Changed in mir:
status: Triaged → In Progress
Changed in unity-system-compositor:
status: Triaged → In Progress
Changed in unity-system-compositor:
status: In Progress → Invalid
summary: - unity-system-compositor can't build against Mir 0.6/0.7: undefined
- reference to `...@MIR_CLIENT_8'
+ unity-system-compositor FTBFS against Mir 0.6/0.7: undefined reference
+ to `...@MIR_CLIENT_8'
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Bisected. The regression came from changes to mirserver.pc.in during:

------------------------------------------------------------
revno: 1831 [merge]
author: Alan Griffiths <email address hidden>
committer: Tarmac
branch nick: development-branch
timestamp: Thu 2014-08-07 23:35:52 +0000
message:
  Add versioning and pkg config to libmirplatform. Fixes: https://bugs.launchpad.net/bugs/1293944.

  Approved by PS Jenkins bot, Chris Halse Rogers, Alexandros Frantzis.
------------------------------------------------------------

summary: - unity-system-compositor FTBFS against Mir 0.6/0.7: undefined reference
- to `...@MIR_CLIENT_8'
+ [regression] unity-system-compositor FTBFS against Mir 0.6/0.7:
+ undefined reference to `...@MIR_CLIENT_8'
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The regression also affects 0.6. It came in during:

------------------------------------------------------------
revno: 1839
fixes bug: https://launchpad.net/bugs/1293944
author: Alan Griffiths <email address hidden>
committer: Cemil Azizoglu <email address hidden>
branch nick: 0.6
timestamp: Fri 2014-08-08 12:08:04 -0500
message:
    Add versioning and pkg config to libmirplatform. Fixes: https://bugs.launchpad.net/bugs/1293944.
------------------------------------------------------------

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

Fixed (in USC at least) by adding "Requires.private: mirclient" in src/server/mirserver.pc.in

Revision history for this message
Cemil Azizoglu (cemil-azizoglu) wrote :

How is it that this built in the silo successfully? (and I was on the lookout for it due to the newly-introduced platform versioning).

Changed in mir:
assignee: Daniel van Vugt (vanvugt) → Alan Griffiths (alan-griffiths)
Changed in mir:
status: In Progress → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix committed to lp:mir/0.6 at revision 1842.

Changed in mir:
assignee: Alan Griffiths (alan-griffiths) → Mir development team (mir-team)
Changed in unity-system-compositor:
assignee: Daniel van Vugt (vanvugt) → nobody
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Not really fixed still :(

But I found the cause. A second fix is coming for USC --> bug 1355609

Revision history for this message
Cemil Azizoglu (cemil-azizoglu) wrote :

Daniel, how do you repro this exactly?
Next time, can you please add your commit for a fix found during a release to the MP (devel-mir-next --> trunk) that's (likely) already up and being reviewed?

https://code.launchpad.net/~mir-team/unity-system-compositor/devel-mir-next/+merge/228904

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

mir (0.6.0+14.10.20140811-0ubuntu1) utopic; urgency=medium

Changed in mir (Ubuntu):
importance: Undecided → Critical
status: New → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry for the confusion. Most of the 0.7.0 series got merged into 0.6.0 at a late stage. I've verified everything in 0.6.0 is also fixed in 0.7.0. So although the branched fixes in 0.7.0 have not been "released" yet, the equivalent fixes in 0.6.0 have. No need to mention them in 0.7 any more.

Changed in mir:
milestone: 0.7.0 → none
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.