Github messages for voidlinux
 help / color / mirror / Atom feed
From: Clyybber <Clyybber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] fluidsynth: update to 2.1.1
Date: Mon, 01 Jun 2020 17:11:23 +0200	[thread overview]
Message-ID: <20200601151123.xWJhukreFO_bevQ05tYzGg32nasnAlSo1Ll-FuThEJQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22134@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

New comment by Clyybber on void-packages repository

https://github.com/void-linux/void-packages/pull/22134#issuecomment-636914336

Comment:
@Chocimier Thank you for fixing this PR. I just recently compiled ardour6 from git just fine, so not sure what the build error is about. One thing worth mentioning is that ardour6 failed when loading or creating a session, because it fails in pthread_create with "Resource temporarily unavailable" (https://github.com/Ardour/ardour/commit/9e054aff585d626fc663985a2d74e3d7b22ed916).
I debugged together with pauldavisthefirst comparing ulimits, glibc versions, etc. but couldn't find the culprit.
Curiously their precompiled binary works (compiled with gcc 8), while the one I built doesn't (gcc 9).

      parent reply	other threads:[~2020-06-01 15:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 15:11 [PR PATCH] " Clyybber
2020-05-19 23:17 ` fosslinux
2020-05-20 10:11 ` [PR PATCH] [Updated] " Clyybber
2020-05-20 23:23 ` fosslinux
2020-05-21  8:33 ` newbluemoon
2020-05-21  8:38 ` newbluemoon
2020-05-21 10:10 ` [PR PATCH] [Updated] " Clyybber
2020-05-27 20:23 ` Chocimier
2020-05-27 20:24 ` Chocimier
2020-05-27 20:26 ` Chocimier
2020-05-28  5:17 ` newbluemoon
2020-05-28  5:27 ` newbluemoon
2020-05-28 22:56 ` [PR PATCH] [Updated] " Chocimier
2020-05-28 23:02 ` Chocimier
2020-05-28 23:03 ` [PR PATCH] [Updated] [WIP] " Chocimier
2020-06-01 15:11 ` Clyybber [this message]

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=20200601151123.xWJhukreFO_bevQ05tYzGg32nasnAlSo1Ll-FuThEJQ@z \
    --to=clyybber@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).