From: Vladimir Serbinenko <phcoder@gmail.com>
To: grub-devel@gnu.org
Cc: Vladimir Serbinenko <phcoder@gmail.com>
Subject: [PATCH v13 03/13] b64dec: Add harness for compilation in GRUB environment
Date: Sat, 24 May 2025 20:22:55 +0000 [thread overview]
Message-ID: <20250524202424.840406-4-phcoder@gmail.com> (raw)
In-Reply-To: <20250524202424.840406-1-phcoder@gmail.com>
Signed-off-by: Vladimir Serbinenko <phcoder@gmail.com>
---
grub-core/lib/gpgrt-int.h | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
create mode 100644 grub-core/lib/gpgrt-int.h
diff --git a/grub-core/lib/gpgrt-int.h b/grub-core/lib/gpgrt-int.h
new file mode 100644
index 000000000..45d63580b
--- /dev/null
+++ b/grub-core/lib/gpgrt-int.h
@@ -0,0 +1,24 @@
+#include <grub/crypto.h>
+
+struct _gpgrt_b64state
+{
+ int idx;
+ int quad_count;
+ char *title;
+ unsigned char radbuf[4];
+ unsigned int crc;
+ gpg_err_code_t lasterr;
+ unsigned int flags;
+ unsigned int stop_seen:1;
+ unsigned int invalid_encoding:1;
+ unsigned int using_decoder:1;
+};
+
+#define _gpgrt_b64dec_start gpgrt_b64dec_start
+#define xtrystrdup grub_strdup
+#define xtrycalloc grub_calloc
+#define xfree grub_free
+#define _gpgrt_b64dec_finish gpgrt_b64dec_finish
+#define gpgrt_assert(expr) ((expr)? (void)0 \
+ : _gcry_assert_failed (#expr, __FILE__, __LINE__, __FUNCTION__))
+#define _gpgrt_b64dec_proc gpgrt_b64dec_proc
--
2.49.0
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2025-05-24 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 20:22 [PATCH v13 00/13] Upgrade to libgcrypt 1.11 Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 01/13] Import " Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 02/13] Import b64dec from gpg-error Vladimir Serbinenko
2025-05-24 20:22 ` Vladimir Serbinenko [this message]
2025-05-24 20:22 ` [PATCH v13 04/13] Adjust import script, definitions and API users for libgcrypt 1.11 Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 05/13] Add DSA and RSA SEXP tests Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 06/13] keccak: Disable acceleration with SSE asm Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 07/13] libgcrypt: Fix coverity warnings Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 08/13] Remove now unneeded gcrypt compilation flag Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 09/13] gcry: Ignore sign-compare warnings Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 10/13] libgcrypt: Import blake family of hashes Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 11/13] import_gcry: Make compatible with python 3.4 Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 12/13] import_gcry: Fix pylint warnings Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 13/13] libgcrypt: Don't use 64-bit division on platforms where it's slow Vladimir Serbinenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250524202424.840406-4-phcoder@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.