From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: Sebastian Kemper <sebastian_ml@gmx.net>
Subject: Re: Robust shared mutexes?
Date: Sat, 26 Nov 2016 17:24:43 -0500 [thread overview]
Message-ID: <20161126222443.GV1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <20161126214943.GA2635@hotdamn.lan>
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.
> and the other said there is. And if there
> is support for it then I'm not sure how robust it is :D
musl fully supports robust mutexes, process-shared or not. They are a
requirement for current POSIX.
> Other variables that I think are set correctly but if you disagreed I'd
> be happy to hear about:
>
> ac_cv_va_copy=yes
Yes. This is true for any conforming C implementation.
> ac_cv_func_realloc_0_nonnull=yes
> ac_cv_func_malloc_0_nonnull=yes
Yes. These are not strict requirements, but if malloc(0) returns a
null pointer, behavior of realloc becomes a huge mess. All reasonable
implementations should return a unique pointer for each malloc(0)
call.
> ac_cv_func_setpgrp_void=yes
Yes, this is a POSIX requirement.
> ac_cv_func_pthread_rwlock_init=yes
Yes. So is this.
> Please keep me on CC if you reply as I'm not subscribed to this list.
OK.
Rich
next prev parent reply other threads:[~2016-11-26 22:24 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 [this message]
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
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=20161126222443.GV1555@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=sebastian_ml@gmx.net \
/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).