-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FTBFS with --enable-wayland: Comparison operator but no version after package name 'gdk-wayland-3.0' #361
Comments
Odd that this didn't fail unconditionally. All my tests that worked but should NOT have, I just submitted |
I am still wondering about this report.
Please show us your config. |
I did find that |
Triggered a build on our CI: NixOS/nixpkgs@375421f, here is the build log: https://logs.ofborg.org/?attempt_id=c4d11f4c-ed6d-43e7-9656-eb0a36cf0ffb&key=nixos%2Fnixpkgs.289062 And by patching the undefined version requirements: NixOS/nixpkgs@1b9d35e, the build went fine: https://logs.ofborg.org/?key=nixos/nixpkgs.289062&attempt_id=34a829c3-b186-405d-b459-f650ec352df8 The build log can be fetched as below, click "Details" next to the Then click "View more details on OfBorg" (below "Partial log") |
I searched where the |
#362 is still waiting for a review |
Expected behaviour
Building with explicit
--enable-wayland
succeedsActual behaviour
This line:
mate-utils/configure.ac
Line 239 in a519784
But neither
GTK_LAYER_SHELL_REQUIRED_VERSION
norGDK_WAYLAND_REQUIRED_VERSION
is set anywhere (also searched on GitHub to make sure it is not set elsewhere),The build complains:
The
--enable-wayland
build succeeds after I removed>= $GTK_LAYER_SHELL_REQUIRED_VERSION
and>= $GDK_WAYLAND_REQUIRED_VERSION
so I don't think needed libraries (or versions) are missingSteps to reproduce the behaviour
Build with explicit
--enable-wayland
(I use release tarballs)MATE general version
1.28
Package version
1.28
Linux Distribution
NixOS
Link to bugreport of your Distribution (requirement)
(I am the packager?)
The text was updated successfully, but these errors were encountered: