gpg 2.2.8: mainproc.c:686: error: 'GPGRT_LOGLVL_INFO' undeclared

Claus Assmann ca+gnupg-devel at
Fri Jun 8 19:35:38 CEST 2018

On Fri, Jun 08, 2018, Damien Goutte-Gattat via Gnupg-devel wrote:

> > mainproc.c:686: error: 'GPGRT_LOGLVL_INFO' undeclared (first use in this function)

> It is defined in libgpg-error. You need at least libgpg-error >= 1.28.

Hmm, all the other calls use GPGRT_LOG_*, not GPGRT_LOGLVL_*

./g10/keyedit.c:                     ? GPGRT_LOG_INFO : GPGRT_LOG_ERROR,
./g10/call-agent.c:             GPGRT_LOG_INFO : GPGRT_LOG_ERROR,
./g10/tofu.c:      log_string (GPGRT_LOG_INFO, msg);
./g10/tofu.c:  log_string (GPGRT_LOG_INFO, text);
./sm/certchain.c:      log_logv (is_error? GPGRT_LOG_ERROR: GPGRT_LOG_INFO, format, arg_ptr);
./dirmngr/dirmngr.c:    log_logv_with_prefix (GPGRT_LOG_INFO, "ntbtls: ", fmt, argv);
./kbx/kbxutil.c:    case GCRY_LOG_INFO: level = GPGRT_LOG_INFO; break;
./common/logging.h:    GPGRT_LOG_INFO,
./common/miscellaneous.c:    case GCRY_LOG_INFO: level = GPGRT_LOG_INFO; break;
./common/logging.c:    case GPGRT_LOG_INFO: break;
./common/logging.c:  do_logv (GPGRT_LOG_INFO, 0, NULL, NULL, fmt, arg_ptr);

and log_string() is defined common/logging.c, so using a different
"value" doesn't seem to make much sense... (but I don't the source
well enough).

More information about the Gnupg-devel mailing list