From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: Git 2.54.0-rc0 Breaks on OpenSSL 3.0
Date: Sun, 5 Apr 2026 15:05:25 -0400 [thread overview]
Message-ID: <029f01dcc52f$2c8b8c70$85a2a550$@nexbridge.com> (raw)
Sadly, OpenSSL 3.0 is still out in the wild for those who have extended
support contracts with OpenSSL. The following errors happen using OpenSSL
3.0 when built with c99:
"/home/jenkinsbuild/.jenkins/workspace/Git_Pipeline/imap-send.c", line 274:
error(252):
argument of type "const X509_NAME_ENTRY *" is incompatible with
parameter of type "X509_NAME_ENTRY *" (aka "struct
X509_name_entry_st
*")
ASN1_STRING_get0_data(cname),
hostname);
^
"/home/jenkinsbuild/.jenkins/workspace/Git_Pipeline/imap-send.c", line 279:
error(114):
identifier "ASN1_STRING_get0_data" is undefined
Sincerely,
Randall
--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.
next reply other threads:[~2026-04-05 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-05 19:05 rsbecker [this message]
2026-04-06 7:07 ` Git 2.54.0-rc0 Breaks on OpenSSL 3.0 René Scharfe
2026-04-06 14:35 ` rsbecker
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='029f01dcc52f$2c8b8c70$85a2a550$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox