From: Po Lu <luangruo@yahoo.com>
To: emacs-devel@gnu.org
Cc: Nikolaos Chatzikonstantinou <nchatz314@gmail.com>
Subject: Re: master e9983b1b63: Add :pass and :flags to gnutls-boot for :keylist
Date: Sat, 31 Dec 2022 09:13:48 +0800 [thread overview]
Message-ID: <878riol6ib.fsf@yahoo.com> (raw)
In-Reply-To: <20221230163910.F15FBC00A7F@vcs2.savannah.gnu.org> (Robert Pluim's message of "Fri, 30 Dec 2022 11:39:10 -0500 (EST)")
Robert Pluim <rpluim@gmail.com> writes:
> branch: master
> commit e9983b1b635cbbc5402279dbbe42878902b151db
> Author: Nikolaos Chatzikonstantinou <nchatz314@gmail.com>
> Commit: Robert Pluim <rpluim@gmail.com>
>
> Add :pass and :flags to gnutls-boot for :keylist
>
> * lisp/net/gnutls.el (gnutls-boot-parameters): Add the keys :pass and
> :flags, and update the documentation.
> * src/gnutls.c (gnutls-boot): Add the keys :pass and :flags, and
> update the documentation.
> (syms_of_gnutls): Add the symbols :pass, :flags, and the symbols that
> correspond to the enumeration constants of the GnuTLS enum
> `gnutls_pkcs_encrypt_flags_t'.
> (key_file2_aux): Private helper function that translates a list of
> symbols to its corresponding `unsigned int' value of the GnuTLS C enum
> `gnutls_pkcs_encrypt_flags_t'.
This breaks the build, complaining about GNUTLS_PKCS_PBES2_GOST_TC26Z,
GNUTLS_PKCS_PBES2_GOST_CPA, GNUTLS_PKCS_PBES2_GOST_CPB,
GNUTLS_PKCS_PBES2_GOST_CPC, being undefined, among others.
next parent reply other threads:[~2022-12-31 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167241835062.27962.3766135889228953493@vcs2.savannah.gnu.org>
[not found] ` <20221230163910.F15FBC00A7F@vcs2.savannah.gnu.org>
2022-12-31 1:13 ` Po Lu [this message]
2022-12-31 7:28 ` master e9983b1b63: Add :pass and :flags to gnutls-boot for :keylist Eli Zaretskii
2022-12-31 10:07 ` Po Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878riol6ib.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=nchatz314@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).