Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62600 - [supertuxkart] built without wayland

Attached to Project: Community Packages
Opened by Lukas Lihotzki (lukasl) - Saturday, 11 May 2019, 04:07 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 24 May 2019, 03:46 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Wayland support (ENABLE_WAYLAND_DEVICE) is enabled by default in supertuxkart 1.0. I have built the 1.0-2 PKGBUILD on my system without any modifications and Wayland is enabled as expected. However, it seems like the official supertuxkart package was built on a system without the wayland package, so it got disabled.

'wayland' should be added to depends to ensure the wayland package is always installed. Please ensure the warning "Wayland not found. Disable wayland support." does not show up during build.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Friday, 24 May 2019, 03:46 GMT
Reason for closing:  Fixed
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 17 May 2019, 02:36 GMT
Please test the current package.
Comment by Lukas Lihotzki (lukasl) - Friday, 17 May 2019, 06:48 GMT
The current package (1.0-3) does not support Wayland. I tested it directly, but it can be checked with "ldd /usr/bin/supertuxkart" too: My self-built binary needs libwayland-client.so.0, libwayland-cursor.so.0, and libwayland-egl.so.1. The official 1.0-3 binary does not need any of those. Those libraries are owned by the 'wayland' package, so libxkbcommon is not sufficient, unless libxkbcommon somehow depends on wayland.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 20 May 2019, 05:06 GMT
True, I was led to believe that it worked due to the build output. I thought it would perhaps dynamically try to load libwayland.so in which case it wouldn't appear in the ldd output. Anyway, the new package hard-deps on wayland and it links to that now.

Loading...