Messages in this thread | | | Date | Thu, 23 Nov 2023 18:42:27 -0500 | Subject | Re: Fwd: sign-file.c:149:17: warning: impli cit declaration of function ‘ENGINE load builtin en gines’ | From | Dennis Clarke <> |
| |
On 11/23/23 09:53, James Bottomley wrote: > 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 >
I am looking into this. The code will likely age into some deprecated calls and I think that I may be way out on the edge here. However the code will need a pile of ifndef stuff and then call the correct future looking calls for OpenSSL 3.x etc etc etc ... the usual stuff
Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken
| |