** Description changed:
+ [ Impact ]
+
+ Mutter failed to build, only once, on jammy amd64:
+
In file included from ../src/backends/meta-backend-private.h:39,
- from ../src/backends/x11/meta-backend-x11.h:31,
- from ../src/backends/x11/nested/meta-backend-x11-nested.h:25,
- from ../src/tests/meta-backend-test.h:23,
- from ../src/tests/meta-backend-test.c:22:
+ from ../src/backends/x11/meta-backend-x11.h:31,
+ from ../src/backends/x11/nested/meta-backend-x11-nested.h:25,
+ from ../src/tests/meta-backend-test.h:23,
+ from ../src/tests/meta-backend-test.c:22:
../src/backends/meta-monitor-manager-private.h:41:10: fatal error:
meta/meta-enum-types.h: No such file or directory
- 41 | #include "meta/meta-enum-types.h"
- | ^~~~~~~~~~~~~~~~~~~~~~~~
+ 41 | #include "meta/meta-enum-types.h"
+ | ^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Seems like an old issue that you can hit at random in highly parallel
builds. Because meta-enum-types.h is auto-generated its consumers need
to declare stronger dependencies.
+
+ [ Test Plan ]
+
+ Build mutter.
+
+ [ Where problems could occur ]
+
+ More build failures or accidentally depending on meson features that
+ don't exist in jammy.
+
+ [ Other Info ]
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055530
Title:
Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-
types.h: No such file or directory]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
