From: ajtcode71 <ajtcode71@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: yabridge-4.0.2
Date: Sat, 01 Oct 2022 09:51:16 +0200 [thread overview]
Message-ID: <20221001075116.vtg0L6B11RRlzUfFooo4WMEb_hRtH6jx7MQtAGg1rWE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39475@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
New comment by ajtcode71 on void-packages repository
https://github.com/void-linux/void-packages/pull/39475#issuecomment-1264280272
Comment:
yabridge does not compile for i686 and x86_64-musl fails with following error:
/builddir/yabridge-4.0.2/build/../src/plugin/../common/utils.cpp:65:69: warning: missing initializer for member 'sched_param::__reserved3' [-Wmissing-field-initializers]
/builddir/yabridge-4.0.2/build/../src/plugin/../common/utils.cpp: In function 'std::optional<long long unsigned int> get_rttime_limit()':
/builddir/yabridge-4.0.2/build/../src/plugin/../common/utils.cpp:81:19: error: 'RLIMIT_RTTIME' was not declared in this scope; did you mean 'RLIMIT_NOFILE'?
81 | if (getrlimit(RLIMIT_RTTIME, &limits) == 0) {
| ^~~~~~~~~~~~~
| RLIMIT_NOFILE
/builddir/yabridge-4.0.2/build/../src/plugin/../common/utils.cpp:86:1: warning: control reaches end of non-void function [-Wreturn-type]
86 | }
| ^
next prev parent reply other threads:[~2022-10-01 7:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 8:12 [PR PATCH] " ajtcode71
2022-09-27 0:14 ` [PR PATCH] [Updated] " ajtcode71
2022-10-01 7:51 ` ajtcode71 [this message]
2022-10-01 8:47 ` ajtcode71
2022-10-01 10:57 ` [PR REVIEW] " paper42
2022-10-01 21:27 ` ajtcode71
2022-10-01 21:32 ` paper42
2022-10-01 21:32 ` paper42
2022-10-01 21:34 ` [PR PATCH] [Updated] " ajtcode71
2022-10-01 21:34 ` ajtcode71
2022-10-02 0:05 ` ajtcode71
2022-10-02 0:05 ` ajtcode71
2022-10-02 0:06 ` [PR REVIEW] " ajtcode71
2022-10-02 0:25 ` paper42
2022-10-02 0:42 ` [PR PATCH] [Updated] " ajtcode71
2022-10-02 0:45 ` ajtcode71
2022-10-02 0:48 ` [PR REVIEW] " ajtcode71
2022-10-02 9:45 ` paper42
2022-10-02 13:56 ` robbert-vdh
2022-10-03 2:08 ` [PR PATCH] [Updated] " ajtcode71
2022-10-03 2:08 ` ajtcode71
2022-10-03 2:14 ` [PR REVIEW] " ajtcode71
2022-10-03 2:20 ` [PR PATCH] [Updated] " ajtcode71
2022-10-03 2:20 ` ajtcode71
2022-10-03 2:20 ` [PR REVIEW] " ajtcode71
2022-10-03 2:22 ` [PR PATCH] [Updated] " ajtcode71
2022-10-03 2:22 ` ajtcode71
2022-10-10 2:07 ` ajtcode71
2022-10-27 8:48 ` [PR PATCH] [Updated] " ajtcode71
2022-10-27 21:14 ` ajtcode71
2022-10-27 21:23 ` ajtcode71
2022-10-27 21:28 ` ajtcode71
2022-11-10 11:08 ` ajtcode71
2023-02-09 2:35 ` github-actions
2023-02-24 2:00 ` [PR PATCH] [Closed]: " github-actions
2023-03-04 12:17 ` prez
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=20221001075116.vtg0L6B11RRlzUfFooo4WMEb_hRtH6jx7MQtAGg1rWE@z \
--to=ajtcode71@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).