From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update Glew to 2.2.0
Date: Mon, 28 Sep 2020 01:41:15 +0200 [thread overview]
Message-ID: <20200927234115.txQH1RuvGt2s4teu6qnHdKO4YaTN9YjF9mOFNn8FQLY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25078@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/25078#issuecomment-699704027
Comment:
"It's alive!"
On Wayland, Clementine simply segfaults on musl, on glibc it complains about not knowing the current backend. @Johnnynator have you ever noticed this issue? It does work if I let it choose its backend, so I'd say this PR is ready. It pulls in stuff from #25135 , so imma close that.
next prev parent reply other threads:[~2020-09-27 23:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 5:35 [PR PATCH] [WIP] " ericonr
2020-09-25 5:41 ` ericonr
2020-09-25 6:35 ` ericonr
2020-09-25 7:26 ` [PR PATCH] [Updated] " ericonr
2020-09-25 7:26 ` ericonr
2020-09-25 7:50 ` ericonr
2020-09-25 8:07 ` [PR PATCH] [Updated] " ericonr
2020-09-25 11:36 ` pullmoll
2020-09-25 11:39 ` pullmoll
2020-09-25 14:38 ` ericonr
2020-09-25 14:56 ` pullmoll
2020-09-25 15:01 ` pullmoll
2020-09-25 15:02 ` pullmoll
2020-09-25 15:19 ` ahesford
2020-09-25 15:51 ` ahesford
2020-09-25 17:20 ` [PR PATCH] [Updated] " ericonr
2020-09-25 17:23 ` ericonr
2020-09-25 18:57 ` ericonr
2020-09-25 19:02 ` ericonr
2020-09-25 21:41 ` hippi777
2020-09-27 21:49 ` ericonr
2020-09-27 23:37 ` [PR PATCH] [Updated] " ericonr
2020-09-27 23:41 ` ericonr [this message]
2020-09-27 23:42 ` ericonr
2020-09-27 23:43 ` ericonr
2020-09-28 2:22 ` [PR PATCH] [Updated] " ericonr
2020-09-28 2:56 ` ericonr
2020-09-28 2:56 ` [PR PATCH] [Merged]: " ericonr
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=20200927234115.txQH1RuvGt2s4teu6qnHdKO4YaTN9YjF9mOFNn8FQLY@z \
--to=ericonr@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).