Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: qt5-webengine: broken on musl
Date: Tue, 24 Sep 2019 11:36:46 +0200	[thread overview]
Message-ID: <20190924093646.ApL0dza80GuMGS3M-b6UqyE_fE7jTIMh4aildFfwg-g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-2368@inbox.vuxu.org>

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

New comment by Johnnynator on void-packages repository

https://github.com/void-linux/void-packages/issues/2368#issuecomment-534478218

Comment:
The problem most likely resides in chromium, which does not support (and probably never will) musl, so we (and other musl distros have the fun to patch it all the time). Qt5 also doesn't officially support musl. Also Alpine Linux also struggles with qt5-webengine https://gitlab.alpinelinux.org/alpine/aports/issues/10405

> I'm still suffering of this crashes. Is there any news about it ? Can we help in someway ?

Sure, send us a patch that fixes it :). But well otherwise there is probably nothing you can do currently.


  parent reply	other threads:[~2019-09-24  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-2368@inbox.vuxu.org>
2019-09-24  9:17 ` voidlinux-github
2019-09-24  9:36 ` voidlinux-github [this message]
2019-09-24 10:35 ` voidlinux-github
2019-11-09 18:16 ` voidlinux-github
2019-11-09 18:19 ` voidlinux-github
2019-11-10 10:08 ` voidlinux-github
2019-11-11  0:32 ` voidlinux-github
2019-11-12  0:23 ` voidlinux-github
2019-11-12  4:42 ` voidlinux-github
2019-11-12 10:27 ` voidlinux-github
2020-05-11 22:13 ` ericonr
2020-05-11 23:45 ` Johnnynator
2020-05-11 23:45 ` [ISSUE] [CLOSED] " Johnnynator

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=20190924093646.ApL0dza80GuMGS3M-b6UqyE_fE7jTIMh4aildFfwg-g@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).