*** This bug is a duplicate of bug 1192908 *** https://bugs.launchpad.net/bugs/1192908
Duplicate of bug 1192908, but forgive me for forgetting the exact details. ** This bug has been marked a duplicate of bug 1192908 Mir/Mesa packaging have a dependency cycle so neither can build -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1239037 Title: circular build-dependency between mesa, mir Status in Mir: New Status in “mesa” package in Ubuntu: New Status in “mir” package in Ubuntu: New Bug description: While testing cross-building of mir, I noticed that mir and mesa have a build-dependency loop: installing the build-dependencies of mir installs libmirclient-dev. This is because mir build-depends on libegl1-mesa-dev, and libegl1 -mesa-dev depends on libmirclient-dev. The libegl1-mesa runtime package does *not* depend on libmirclient3, so this dependency looks spurious to me. Is there a reason this dependency loop shouldn't be broken by dropping the dep from libegl1 -mesa-dev -> libmirclient-dev? As near as I can tell, the dependency on libmirclient-dev is because of this section of /usr/include/EGL/eglplatform.h: #elif defined(MIR_EGL_PLATFORM) #include <mir_toolkit/mir_client_library.h> typedef MirEGLNativeDisplayType EGLNativeDisplayType; typedef void *EGLNativePixmapType; typedef MirEGLNativeWindowType EGLNativeWindowType; [...] But that's optional, and anybody defining MIR_EGL_PLATFORM would presumably need to depend on mir themselves, no? To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1239037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp