Please remember to add a comment to the code describing the reason for this renaming.

The issue is the routines of regcomp, regexec, regerror and regfree are in C library and the sanitizer library replaces them (and it's not compatible for the use case of GnuPG).

Thanks, that was the only issue building there.

Note: The Kleopatra in upcoming versions of Gpg4win 5 will have AboutData::version set to gpg4win-5.0.0 (or gpg4win-5.0.0-beta190 for beta versions). See T7666: Kleopatra: Rework versioning.

Tools / Refresh OpenPGP certificates runs gpg --refresh-keys. I don't think that this command knows anything about WKD.

For vsd on Windows this will be solved due to the use of gnupg-vsd as default homedir. We already tested this with a beta MSI installer

This should compare the gpg4win version number:

I updated the github issue. The suggested change seems to have had no effect.

If you are experience problems with the test suite on NetBSD, please see T7634

Thank you @alexk

I made a comment on github.

Please re-open if you find other Cygwin related build problems.

You know that Cygwin is not supported but if that is the only place it should not arm to fix it.

Another possible change will be use of KEM interface for gpgsm.
Not high priority, but for long term code maintenance.

Thanks for the quick fix. I feel a bit silly for not notcing that macro myself...

Fixed in all branches but there is no potential for exploiting. See also gnupg-devel@ ML.

This should do the trick (master) but have not yet tested it:

Fixed. Thanks for the report!

The classic NIST P521 pitfall ;-)

Done by T7649: gnupg: Use KEM interface for encryption/decryption

Thank you.