public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Quanah Gibson-Mount <quanah@symas.com>
To: Achim Gratz <Stromeko@nexgo.de>, cygwin@cygwin.com
Subject: Re: openldap on Cygwin
Date: Thu, 25 Jul 2019 19:04:00 -0000	[thread overview]
Message-ID: <B2DE5486F870C120CA731D7E@[192.168.1.39]> (raw)
In-Reply-To: <87tvba7yqx.fsf@Rainer.invalid>

--On Thursday, July 25, 2019 9:30 PM +0200 Achim Gratz <Stromeko@nexgo.de> 
wrote:

> Quanah Gibson-Mount writes:
> […]
>
> Sorry for wedging in sideways, but I've looked into building a more
> up-to-date openldap and there's missing detection / configuration for
> Cygwin.  Specifically, there's code trying to use robust POSIX mutexes,
> which Cygwin doesn't have.  As there is no configure option (that I
> could find), the solution is a bit invasive: either feeding in a number
> of preprocessor defines or patching in the recognition of Cygwin into
> libraries/liblmdb/mdb.c to define the correct options there.
>
> Any chance the upcoming release would have a fix for that?

Hi Achim,

I would suggest filing a report in the OpenLDAP issue tracker at:

<https://www.openldap.org/its>

I use MSYS2 for my OpenLDAP on windows builds, so haven't any direct 
experience at the moment with building it via cygwin.

Regards,
Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-07-25 19:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 17:32 Bug report: Killing a native process may not actually kill it Quanah Gibson-Mount
2019-07-25 18:30 ` openldap on Cygwin (was: Bug report: Killing a native process may not actually kill it) Achim Gratz
2019-07-25 19:04   ` Quanah Gibson-Mount [this message]
2019-08-28 15:46 ` Bug report: Killing a native process may not actually kill it Quanah Gibson-Mount
2019-08-28 15:59   ` Corinna Vinschen
2019-08-28 16:02     ` Quanah Gibson-Mount
2019-08-28 20:33       ` Corinna Vinschen
2019-08-28 22:43       ` Kaz Kylheku
2019-08-29  0:02         ` Quanah Gibson-Mount
2019-08-29  1:01           ` Steven Penny
2019-09-03  5:38             ` Ray Donnelly

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='B2DE5486F870C120CA731D7E@[192.168.1.39]' \
    --to=quanah@symas.com \
    --cc=Stromeko@nexgo.de \
    --cc=cygwin@cygwin.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).