We will therefore have to form an idea of ​​the kind of person one must be, to be able to deliberately put oneself in a position of not being able to answer, by using a rather dubious pretext, insinuating the ignorance of a third audience about the inconsistency which, however, anyone could independently state. Thus, in this path you have chosen to persevere. Well then, you alone know the rules of your game.

Wouldn't anyone suspect that you are in the habit of dispensing the ''Invalid'' label without discernment for reports that, however, have no basis as such? But what on earth could you possibly be trying to achieve by acting in this way?

I wonder how common this practice of splitting development material into a separate file might be? It is in place at Alpine, since the file libgpg-error-dev exists. Once the related component is instaled, these messages/strings are printed:; output filtered:

checking for GPG Error - version >= 1.49... expr: warning: '^x-L': using '^' as the first character of a basic regular expression is not portable; it is ignored  yes (1.49)

Updates for projects' scripts related to GnuPG for building from source may be needed; So it is at least for libgcrypt; illustration (output filtered):

Reported.

You may.. Comments were relevant. Bye.

"more specific about what you think is wrong"; From https://bugs.kde.org/show_bug.cgi?id=412569 copied)/pasted:

Hey. As reference – Complete set of features while run in Windows.

I was able to avoid reported behaviour; then n not a bug.