mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] Musl gentoo development: browsers
Date: Fri, 14 Feb 2020 16:14:06 -0500	[thread overview]
Message-ID: <20200214211406.GN1663@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAGw6cBsMw7aA2n80ud4fvJGtaNdQTLPLhrmFpS_0LYHYZXLgcA@mail.gmail.com>

On Fri, Feb 14, 2020 at 12:51:25PM -0800, Michael Forney wrote:
> Recently, I've been spending some time writing upstreamable patches
> for long standing musl incompatibilities in Firefox (and the parts it
> imports from chromium), and pushing to get them fixed finally.
> 
> So far, I've had some good success:
> https://hg.mozilla.org/mozilla-central/rev/1acc873aa118
> https://hg.mozilla.org/mozilla-central/rev/660da1ec99c0
> https://hg.mozilla.org/mozilla-central/rev/3ec8c96f4d53
> https://hg.mozilla.org/mozilla-central/rev/7c6f9f854cfc
> https://hg.mozilla.org/mozilla-central/rev/a3096ca24124
> 
> All but the last one should be available in the next Firefox release (74).
> 
> I believe the last remaining remaining issue is usage of getcontext in
> tools/profiler. I've just filed a bug at
> https://bugzilla.mozilla.org/show_bug.cgi?id=1615713. I have a couple
> ideas for a fix (outlined in that bug), but haven't written a patch
> yet. If anyone has suggestions, please let me know!
> 
> In one of the reviews, the reviewer mentioned about the existence of
> build target support tiers:
> https://developer.mozilla.org/en-US/docs/Mozilla/Supported_build_configurations
> 
> I was thinking that once Firefox can build with musl out of the box,
> it would be really great to see if we can get Mozilla to consider musl
> to be a Tier 3 target (at least x86_64), so we can avoid any musl
> regressions in the future.

There's a third-party libucontext that can be used with musl, but it's
nonconforming in that it doesn't save/restore signal mask. That
probably doesn't matter for their usage so it might make sense to just
build against that. (Have you checked what Alpine and Adélie and Void
are doing?)

Rich

  reply	other threads:[~2020-02-14 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 12:12 Brian Peregrine
2020-02-14 17:15 ` A. Wilcox
2020-02-14 20:51 ` Michael Forney
2020-02-14 21:14   ` Rich Felker [this message]
2020-02-14 21:32     ` A. Wilcox
2020-02-14 21:35   ` A. Wilcox
2020-02-15 14:20 ` [musl] " Brian Peregrine
2020-02-15 17:29   ` Rich Felker
2020-02-15 17:45     ` Milan P. Stanić
2020-02-15 18:56     ` A. Wilcox
2020-05-20 16:30     ` Brian Peregrine
2020-02-15 18:54   ` A. Wilcox

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=20200214211406.GN1663@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).