From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Robust shared mutexes?
Date: Mon, 28 Nov 2016 16:53:09 -0500 [thread overview]
Message-ID: <20161128215309.GY1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <651EE05A-C592-45C3-BAB6-A6CDDDAF98A4@gmail.com>
On Mon, Nov 28, 2016 at 01:36:50PM -0800, Khem Raj wrote:
>
> > On Nov 26, 2016, at 2:56 PM, Rich Felker <dalias@libc.org> wrote:
> >
> > On Sat, Nov 26, 2016 at 11:51:05PM +0100, Sebastian Kemper wrote:
> >> On Sat, Nov 26, 2016 at 05:24:43PM -0500, Rich Felker wrote:
> >>> On Sat, Nov 26, 2016 at 10:49:44PM +0100, Sebastian Kemper wrote:
> >>>> Hello all,
> >>>>
> >>>> I'm cross-compiling for OpenWRT/LEDE and have this variable
> >>>> apr_cv_mutex_robust_shared. Should I set it to yes or no with musl? I've
> >>>> searched around but found conflicting infos. One post said there's no
> >>>> shared mutex support in musl
> >>>
> >>> Do you have a link for that? If there's incorrect information I'd like
> >>> to reply and see if it can be corrected.
> >>
> >> Hello Rich,
> >>
> >> Thank you very much for the reply!
> >>
> >> I looked for the link and it turns out it was an error on my part. The
> >> post wasn't referring to robust shared mutexes. It was regarding process
> >> shared mutexes
> >>
> >> http://lists.openembedded.org/pipermail/openembedded-core/2016-March/119214.html
> >>
> >> It says musl doesn't have process shared mutexes so one should set
> >> apr_cv_process_shared_works=no. I take it that is correct?
> >
> > No, it's incorrect and I have no idea where that idea came from. I'll
> > ask Khem.
> >
>
> IIRC it was not musl but papering over apr specific issue. I never got time to really dig in
> to root cause it.
Indeed, that's what it seems to be here too. They don't support the
standard API, only some ancient glibc _NP version of it, and they
don't even do anything to handle the case of ownerdied correctly...
Rich
prev parent reply other threads:[~2016-11-28 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 21:49 Sebastian Kemper
2016-11-26 22:24 ` Rich Felker
2016-11-26 22:51 ` Sebastian Kemper
2016-11-26 22:56 ` Rich Felker
2016-11-26 23:01 ` Szabolcs Nagy
2016-11-27 10:54 ` Sebastian Kemper
2016-11-27 11:37 ` Szabolcs Nagy
2016-11-27 11:51 ` Alexander Monakov
2016-11-27 16:26 ` Sebastian Kemper
2016-11-26 23:02 ` Sebastian Kemper
2016-11-28 21:36 ` Khem Raj
2016-11-28 21:53 ` Rich Felker [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=20161128215309.GY1555@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).