FS#67612 - [meson] arch-meson caused build error, request for removal

Attached to Project: Arch Linux
Opened by G3ro (G3ro) - Sunday, 16 August 2020, 21:57 GMT
Last edited by Jan Alexander Steffens (heftig) - Monday, 17 August 2020, 22:46 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
While building the master branch of Xserver with the PKGBUILD file from arch (https://github.com/archlinux/svntogit-packages/blob/packages/xorg-server/trunk/PKGBUILD) I had a bug that stated:
undefined reference to `GrabButton'

See also Bug report upstream:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1060

After several days I found out that arch-meson applies specific options to meson and the problem was:
b_lto=true

After using plain meson, everything worked fine.

I would like to ask for removal of arch-meson, because it is confusing for people that config options are applied outside of PKGBUILD files.
For reasons of transparency and KISS I think it is reasonable to ask all maintainers to apply those few lines themselves if necessary.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Monday, 17 August 2020, 22:46 GMT
Reason for closing:  Won't implement
Comment by Jan Alexander Steffens (heftig) - Monday, 17 August 2020, 22:46 GMT
I think a set of predefined options suitable for most packages is a reasonable compromise between automation and duplication and does follow the KISS philosophy. It's also a clear invocation of something different than plain "meson" and not a jungle of RPM macros or debhelper rules, either.
Comment by Eli Schwartz (eschwartz) - Monday, 17 August 2020, 23:09 GMT
We already have a set of predefined options suitable for most packages, in makepkg.conf -- and meson -Db_lto=true merely adds -flto to CFLAGS and LDFLAGS. If the consensus is we want LTO, this should not be meson-specific; use it everywhere, tell people to opt out by adding -fno-lto to packages that break. And it's apparent that meson projects aren't immune to being buggy with LTO.

Loading...