From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] mutter-45.* fails to build for musl targets due to the 'undeclared RLIMIT_RTTIME' error
Date: Sat, 27 Jan 2024 00:48:44 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48391@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4687 bytes --]
New issue by chrysos349 on void-packages repository
https://github.com/void-linux/void-packages/issues/48391
Description:
Hey,
I've created the [issue](https://gitlab.gnome.org/GNOME/mutter/-/issues/3255) upstream a week ago. No answer.
Any ideas? Am I doing something wrong?
The issue is below.
>`mutter 45.*` fails to (cross)build for musl targets due to the `error: 'RLIMIT_RTTIME' undeclared`.
>
>AFAIK, `RLIMIT_RTTIME` was introduced in `musl-1.2`. Unfortunately, Void Linux has `musl-1.1` and has no plans to update it.
>
>It seems the only way to build successfully for musl targets in Void Linux is to disable wayland functionality by adding `-Dnative_backend=false -Dwayland=false -Dxwayland=false` to configure arguments, but this outcome is not desirable.
>
>TLDR: Is there a way to patch `mutter 45.*` in order to be able to build it for musl targets in Void Linux with `musl-1.1` which lacks `RLIMIT_RTTIME`?
>
>```
>RLIMIT_RTTIME[752/767] Compiling C object src/libmutter-13.so.0.0.0.p/backends_native_meta-thread.c.o
>FAILED: src/libmutter-13.so.0.0.0.p/backends_native_meta-thread.c.o
>aarch64-linux-musl-gcc -Isrc/libmutter-13.so.0.0.0.p -Isrc -I../src -I. -I.. -Iclutter -I../clutter -Iclutter/clutter -I../clutter/clutter -Imtk -I../mtk -Imtk/mtk -I../mtk/mtk -Icogl -I../cogl -Icogl/cogl -I../cogl/cogl -Isrc/meta -I/usr/aarch64-linux-musl/usr/include/glib-2.0 -I/usr/aarch64-linux-musl/usr/lib64/glib
>-2.0/include -I/usr/aarch64-linux-musl/usr/include/gio-unix-2.0 -I/usr/aarch64-linux-musl/usr/include/libmount -I/usr/aarch64-linux-musl/usr/include/blkid -I/usr/aarch64-linux-musl/usr/include/graphene-1.0 -I/usr/aarch64-linux-musl/usr/lib64/graphene-1.0/include -I/usr/aarch64-linux-musl/usr/include/cairo -I/usr/aarch
>64-linux-musl/usr/include/freetype2 -I/usr/aarch64-linux-musl/usr/include/libpng16 -I/usr/aarch64-linux-musl/usr/include/pixman-1 -I/usr/aarch64-linux-musl/usr/include/gdk-pixbuf-2.0 -I/usr/aarch64-linux-musl/usr/include/atk-1.0 -I/usr/aarch64-linux-musl/usr/include/json-glib-1.0 -I/usr/aarch64-linux-musl/usr/include/
>pango-1.0 -I/usr/aarch64-linux-musl/usr/include/fribidi -I/usr/aarch64-linux-musl/usr/include/harfbuzz -I/usr/aarch64-linux-musl/usr/include/libwacom-1.0 -I/usr/aarch64-linux-musl/usr/include/gudev-1.0 -I/usr/aarch64-linux-musl/usr/include/libevdev-1.0/ -I/usr/aarch64-linux-musl/usr/include/gsettings-desktop-schemas -
>I/usr/aarch64-linux-musl/usr/include/colord-1 -I/usr/aarch64-linux-musl/usr/include/gnome-settings-daemon-45 -I/usr/aarch64-linux-musl/usr/include/libei-1.0 -I/usr/aarch64-linux-musl/usr/include/gnome-desktop-4.0 -I/usr/aarch64-linux-musl/usr/include/libxml2 -I/usr/aarch64-linux-musl/usr/include/startup-notification-1
>.0 -I/usr/aarch64-linux-musl/usr/include/pipewire-0.3 -I/usr/aarch64-linux-musl/usr/include/spa-0.2 -I/usr/aarch64-linux-musl/usr/include/gobject-introspection-1.0 -I/usr/aarch64-linux-musl/usr/include/uuid -I/usr/aarch64-linux-musl/usr/include/elogind -I/usr/aarch64-linux-musl/usr/include/libdrm -I/usr/aarch64-linux-
>musl/usr/include -fvisibility=hidden -flto=auto -fdiagnostics-color=always -DNDEBUG -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -D_GNU_SOURCE -fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -pipe -march=armv8-a -ffile-prefix-map=/builddir/mutter-45.3/build=. -fPIC -D_REENTRANT -pthread -DCLUTTER_ENABLE_COMPOSITOR_API
>-DCOGL_ENABLE_EXPERIMENTAL_API -DCOGL_ENABLE_EXPERIMENTAL_2_0_API -DCOGL_ENABLE_MUTTER_API -DCLUTTER_DISABLE_DEPRECATION_WARNINGS -DCOGL_DISABLE_DEPRECATION_WARNINGS -DSN_API_NOT_YET_FROZEN=1 '-DGETTEXT_PACKAGE="mutter"' -DWITH_VERBOSE_MODE '-DG_LOG_DOMAIN="libmutter"' -MD -MQ src/libmutter-13.so.0.0.0.p/backends_nati
>ve_meta-thread.c.o -MF src/libmutter-13.so.0.0.0.p/backends_native_meta-thread.c.o.d -o src/libmutter-13.so.0.0.0.p/backends_native_meta-thread.c.o -c ../src/backends/native/meta-thread.c
>../src/backends/native/meta-thread.c: In function 'request_realtime_scheduling':
>../src/backends/native/meta-thread.c:288:18: error: 'RLIMIT_RTTIME' undeclared (first use in this function); did you mean 'RLIMIT_RTPRIO'?
> 288 | if (setrlimit (RLIMIT_RTTIME, &rl) != 0)
> | ^~~~~~~~~~~~~
> | RLIMIT_RTPRIO
>../src/backends/native/meta-thread.c:288:18: note: each undeclared identifier is reported only once for each function it appears in
>[753/767] Linking target clutter/clutter/libmutter-clutter-13.so.0.0.0
>[754/767] Generating cogl/cogl-pango/CoglPango-13.gir with a custom command (wrapped by meson to set env)
>[755/767] Generating cogl/cogl/Cogl-13.typelib with a custom command
>ninja: build stopped: subcommand failed.
>
>```
next reply other threads:[~2024-01-26 23:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 23:48 chrysos349 [this message]
2024-01-27 0:22 ` oreo639
2024-01-27 0:26 ` oreo639
2024-01-27 9:00 ` oreo639
2024-01-27 9:05 ` oreo639
2024-01-27 12:12 ` [ISSUE] [CLOSED] " chrysos349
2024-01-27 12:12 ` chrysos349
2024-01-29 11:32 ` oreo639
2024-01-29 12:09 ` chrysos349
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48391@inbox.vuxu.org \
--to=chrysos349@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).