From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Dennis Clarke <dclarke@blastwave.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kernel Build System <linux-kbuild@vger.kernel.org>,
Linux Kernel Keyrings <keyrings@vger.kernel.org>
Cc: David Howells <dhowells@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: Fwd: sign-file.c:149:17: warning: implicit declaration of function ‘ENGINE_load_builtin_engines’
Date: Thu, 23 Nov 2023 09:53:02 -0500 [thread overview]
Message-ID: <164a4d4434e77ba1b65624a081799a073a3aced7.camel@HansenPartnership.com> (raw)
In-Reply-To: <e110cfff-08f9-4bbc-6b69-0d67ae6562b6@blastwave.org>
On Fri, 2023-11-17 at 00:34 -0500, Dennis Clarke wrote:
> On 11/16/23 18:41, Bagas Sanjaya wrote:
> > Hi,
> >
> > I notice a bug report on Bugzilla [1]. Quoting from it:
> >
> <snip>
> > > Not related to
> > > https://bugzilla.kernel.org/show_bug.cgi?id=215750 but I *feel*
> > > that this code needs a hug.
> >
> > See Bugzilla for the full thread.
> >
> > AFAIK, this looks like a bug when the kernel is compiled against
> > custom (non-system) version of OpenSSL library.
> >
>
> I do not know what you could possibly mean. There is nothing "custom"
> about OpenSSL. For that matter the gcc compiler I am using was also
> built by me. Works fine. The sign-file.c source compiles fine.
This has all the hallmarks of an openssl compiled without engine
support; is the symbol OPENSSL_NO_ENGINE set? And which distro did you
get this library from?
James
next prev parent reply other threads:[~2023-11-23 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 23:41 Bagas Sanjaya
2023-11-17 5:34 ` Dennis Clarke
2023-11-22 4:55 ` Bagas Sanjaya
2023-11-23 14:37 ` Dennis Clarke
2023-11-23 14:53 ` James Bottomley [this message]
2023-11-23 23:42 ` Dennis Clarke
2023-11-24 1:05 ` James Bottomley
2023-11-30 20:30 ` Dennis Clarke
2023-11-24 2:28 ` Dennis Clarke
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=164a4d4434e77ba1b65624a081799a073a3aced7.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=bagasdotme@gmail.com \
--cc=dclarke@blastwave.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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
all inboxes | Powered by JetHome®