Found the cause. It was this update:
android-headers (23-0ubuntu1) xenial; urgency=medium
* New upstream release which now includes multiple sets of header files
divided by the Android API levels we care about.
* All header sets are now installed in their corresponding debian package
android-headers-<API level>. The former android-headers package is now
a transitional one depending on android-headers-19 and installing proper
symlinks to allow all current users to still build without any changes.
* Install proper pkgconfig configuration files for all header sets so that
users can now select which of those to use a build time.
-- Simon Fels <[email protected]> Mon, 11 Jan 2016 08:50:59
+0100
** Also affects: mir/0.18
Importance: Undecided
Status: New
** Changed in: mir/0.18
Importance: Undecided => Critical
** Changed in: mir/0.19
Importance: Undecided => Critical
** Changed in: mir/0.18
Milestone: None => 0.18.2
** Changed in: mir/0.19
Milestone: None => 0.19.0
** Tags removed: ftmfs
** Tags added: ftbfs
** Also affects: android-headers (Ubuntu)
Importance: Undecided
Status: New
** Changed in: android-headers (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539338
Title:
Mir fails to build on xenial today:
android_graphic_buffer_allocator.h:23:31: fatal error:
hardware/hardware.h: No such file or directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1539338/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
