My summary here:

• Use of winepath by libtool is correct way for semi-hosted environment to run tests built by cross-build.
• (cross-)Build itself is possible with no winepath (or winepath -> /bin/false), if you don't need make check with semi-hosted environment.
• I don't see that it's too slow, these days. My environment is bookworm Debian (having Wine 8.0 something).

For me each time wine is upgraded I get for the first time an error when building something, but it is not slow anymore. Is this resolved?

Pushed the change: rGaf6c47b2910f: common,kbx,tests: Clean up the PIPE function API.

Using/setting a value of 2 would work for Kleopatra.

That is probably right for gpgme as used by kleopatra. However in gnupg we need to switch utf8 on and off.

The use of putc_unlocked has long been removed. So we should also remove the declaration. Normally this does not harm but in your case you may want to pass CFLAGS="-DHAVE_PUTC_UNLOCKED" to make or remove the above declaration.

Now also done for libksba.

See: MacPorts Ticket 70267 and MacPorts PR #24601

While the above patch worked for MacOS 10.8 and above, MacPorts CI shows a second error for older MacOS versions:

It looks like various flavors of BSD (including macOS just declare environ when needed): environ -- user environment Note: this is a very old MacOS X man page, however the current version is from 2003, and has the same Synopsis.

Didn't you had this problem with 1.10.x ? I can't remember that we changed anything at theat code for years. The only recent change was rC656ca459e which should not have changed anything. Maybe the problem is elsewhere.

It's tested by gnupg master (for gnupg26) for a year. Let us move on.

Thank you. Applied by : rM87061c0260bb: gpgme.m4: Set $host correctly always.

Ditto for ksba and assuan.

The gcrypt change works for me. Thanks!

In general, asking an application change is not good. Migrating to pkg-config should be an option (not requirement).
However, it's usually recommended to use libgpg-error when an application is used with libgcrypt/libksba/libassuan.

Just to clarify: I personally think it would be perfectly fine to say that AM_PATH_* is only supported when AM_PATH_GPG_ERROR is also used. Adding an invocation AM_PATH_GPG_ERROR is not a great hassle and alternatively pkg-config/pkgconf exists and works perfectly fine (and is a lot faster).

I noticed this recently too on some boxes. Thanks for the good decription. This support for pkg-config style .pc files for our config scripts seems to be a never ending story. The alternative name for libgpg-error-config does not make it easier.

Oh yeah the idea to implement aliases is more than 20 years old. I guess it is even older. Thanks.

Along with the monitor we should also implement a domain selection feature.