[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <164a4d4434e77ba1b65624a081799a073a3aced7.camel@HansenPartnership.com>
Date: Thu, 23 Nov 2023 09:53:02 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Dennis Clarke <dclarke@...stwave.org>,
Bagas Sanjaya <bagasdotme@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Kernel Build System <linux-kbuild@...r.kernel.org>,
Linux Kernel Keyrings <keyrings@...r.kernel.org>
Cc: David Howells <dhowells@...hat.com>,
David Woodhouse <dwmw2@...radead.org>,
Masahiro Yamada <masahiroy@...nel.org>
Subject: Re: Fwd: sign-file.c:149:17: warning: implicit declaration of
function ‘ENGINE_load_builtin_engines’
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
Powered by blists - more mailing lists