From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: No definition of PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP in musl
Date: Mon, 20 Feb 2017 17:24:19 +0100 [thread overview]
Message-ID: <20170220162419.dxpcdbp23up3iopr@voyager> (raw)
In-Reply-To: <CACCP0Gp59ghH1t-=ixSApgjhL6A56WkVu2LXH_K5VUJCF9C2KA@mail.gmail.com>
On Mon, Feb 20, 2017 at 03:22:41PM +0000, Raphael Cohn wrote:
> Hi,
>
> Whilst trying to compile ReOpenLDAP (https://github.com/ReOpen/ReOpenLDAP),
> a fork of OpenLDAP, I'm running into a wall. Some of the code wants a
> definition of PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP. musl doesn't define
> this; I suspect this is a non-portable glibc extension in pthread.h. Does
> any one have any ideas how I might workaround this? Is there an alternative
> construction that the code could use?
>
Well, not directly.
PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP is an initializer that makes a
mutex recursive. What you could do is look for a single use
initialization function. Then you could replace
static pthread_mutex_t mut = PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP;
with
static pthread_mutex_t mut;
...
pthread_mutexattr_t mutattr = {0};
pthread_mutexattr_init(&mutattr);
pthread_mutexattr_settype(&mutattr, PTHREAD_MUTEX_RECURSIVE);
pthread_mutex_init(&mut, &mutattr);
pthread_mutexattr_destroy(&mutattr);
...
That's the portable way to do it. However, the nonportable solution is
generally used to avoid the one-time initialization otherwise necessary.
As such, there may not be a place for you to put the above snippet. In
that case you may have to introduce such a function.
Alternatively, you could look up the effects the above snippet has on
the mutex under musl, at least at the moment, and declare the
nonportable initializer yourself. At the moment, I think it would be
#define PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP {{PTHREAD_MUTEX_RECURSIVE}}
> Any help gladly appreciated.
>
Hope it helps.
> Raph
>
Ciao,
Markus
next prev parent reply other threads:[~2017-02-20 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 15:22 Raphael Cohn
2017-02-20 16:24 ` Markus Wichmann [this message]
2017-02-20 17:03 ` Rich Felker
2017-02-20 17:21 ` Raphael Cohn
2017-02-20 17:03 ` 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=20170220162419.dxpcdbp23up3iopr@voyager \
--to=nullplan@gmx.net \
--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).