Alright: Call gettext_use_utf8 (3) to set the current thread to utf8 and init all new threads to utf8 as well. This function with that value (actually bit 1 is relevant) can be used several times but it will never switch back the initialization to utf8. However, switching back and force to utf8 per threads is still possible.

Noticed this again that it was very slow. I guess how fast it is depends on your wine configuration. I worked it around by disabling winepath for me again. But do we want to change anything here or just move this to wontfix?

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.

I think we should close this bug or re-purpose it to silence those warnings in common cases.

That could be fixed in src/argparse.c:set_opt_arg by adding and endptr to the strtol calls and check that only white space follows. However, there is some risk of regression with this approach. Maybe just display a warning?

With today's release of npth everything should be set.

Thank you for the fix. Pushed the change modifying the commit log for the ChangeLog entry.

Alright.

Push the change as rE4a9def77488f: estream: Fix call to string filter for estream-printf..

I see your point: allocating STRINGBUF to make sure nul-terminated string.
The code itself doesn't work well in a test case of tests/t-prinntf.c, because it assumes string filter should be called with NULL for string.

Like this:

@@ -1196,10 +1196,25 @@ pr_string (estream_printf_out_t outfnc, void *outfncarg,
    future, when breaking API/ABI is OK, we can change signature of
    gpgrt_string_filter_t to have another argument for precision.  */
   int allow_non_nul_string = (arg->precision >= 0);
+  char *stringbuf = NULL;

We could also pass a nul terminated copy to the filter function in pr_string.

@item handling with @table has been pushed.

I learned about how @item is handled by TeX. By @table command, user specifies how to handle the item line. In the case of GnuPG, it is like:

@table @gnupgtabopt
@item --version
...
@item --help

(Emacs uses @table @samp, while GCC uses @table @gcctabopt.)
And @gnupgtabopt is a macro which is expanded to @code{\body\}

Possible approach for source texinfo files and yat2m would be:

I found a regression for @item --version; It emits \[en]version for roff.

Pushed my fix to support them.

I guess we should add an extended API to set the filter.

I guess we should follow the GNU standards and provide only info files ;-)

Other problems of yat2m transformation:
https://bugs.debian.org/1050886

Not easy do decide whether something is a PIN or a PUK and we will need to check a lot of places. So, not now.

I found a troff reference: https://www.quut.com/berlin/ms/troff.html

Ideally, we should change the source document to use @minus{} for a minus sign, and keep - only when it means a hyphen. But we cannot do that blindly; We need to handle it with care, in a way of case by case (Texinfo manual suggests no use of @minus{} with @code or @example, but it is needed for groff man pages in many cases).... We would need to consider each occurrence of - in our document. That's too much (if it were me to fix).