May 14 2024
Thanks, I confirm that this new commit is fixing the issue.
May 13 2024
Thank you for testing. Now, I can see the exact reason by your npth log.
Pushed another change: rPTH75c68399ef3b: Fix previous commit.
May 12 2024
Build is still failing even with this commit, here is an extract of npth log:
May 7 2024
Could you show us the build log of nPth, please?
May 6 2024
May 5 2024
Apr 1 2024
On Mac OS X 10.5.8, PPC Leopard, it built with the patch, gpg-agent works.
Mar 27 2024
Thank you for your quick testing.
Mar 26 2024
I've reported the success to MacPorts. My test was performed on only one platform, Mac OS X 10.4.11 or "Tiger". Since there exists a problem with building recent version of GPGME testing on Mac OS X 10.5.8 or "Leopard" will have to wait a few days…
With the unified patch all works fine (again), even the test target succeeds!
Performing the patch manually the "port" (package) built and installed. Starting then gpg-agent worked too, killing it (with gpgconf) worked as well.
The patches looks too large to merge (than actually needed), and not enough/clean like not having detection of the system.
Mar 25 2024
Mar 24 2024
Mar 1 2024
Apply the change in: rPTH417abd56fd7b: Fix INSERT_EXPOSE_RWLOCK_API for musl C library.
Feb 29 2024
@gniibe Thank you very much! That works.
@thesamesam Thank you for the report.
This seems to have regressed musl support, per https://bugs.gentoo.org/925443.
Fixed in npth 1.7.
Feb 23 2024
The patch is part of 1.7 - please test and in case of problems feel free to re-open.
Jan 30 2024
After applying patch to nPth 1.6 no semaphore leaks detected. Tested with GnuPG-2.3.3.
There has been positive feedback from production environment as well.
Jan 29 2024
Jan 23 2024
Jan 22 2024
Jan 20 2024
Aug 4 2023
npth_t is untouched for Windows 64-bit.
Oct 5 2022
Sep 22 2022
Jul 22 2022
@gniibe Thanks!
In the repo, for all related software, it's done.
Note that versions since 2020-11-07 to 2021-07-03 have major problem with non-POSIX shell, which doesn't support $(..) construct.
Jul 18 2022
Thank you.
May 27 2022
May 10 2022
Mar 24 2022
Indeed, different versions of MinGW use different symbols to guard the declaration, and using those symbols in not future-proof enough, IME.
Removing the declaration is definitely the best solution.