Re: Fwd: sign-file.c:149:17: warning: implicit declaration of function ‘ENGINE_load_builtin_engines’

[Dennis Clarke <dclarke@blastwave.org>]

On 11/21/23 23:55, Bagas Sanjaya wrote:
> On 11/17/23 12:34, 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.
>>
>> It fails to compile in the usual way when trying to build the kernel.
>>
> 
> Hi Thorsten and all,
> 
> AFAIK there is no reply from kbuild people (maybe they missed this bug?).

I suspect no one is even looking at it. Just us :)

> 
> As for the error itself, let me clarify. The reporter (Dennis) have a build
> problem with /usr/local version of OpenSSL library. He installed it
> (presumably) alongside with system version (which is installed to /usr),
> hence I called the /usr/local version as custom one (IDK if that version
> is vanilla OpenSSL or not). Maybe am I missing something?
> 

Well, today we have OpenSSL 3.2.0 published :

     https://www.openssl.org/source/

So I will try again and this time I will begin with a very stripped down
install of Debian stable. When I mean stripped down I mean there will be
nothing in the base install except reasonable TCP/IP network support and
the ability to FTP a file into it. I can extract a tarball of a decent
compiler that I bootstrapped myself with excellent results :

     https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/794816.html

This will be done on real hardware. Not a virtual machine of any type
where that should make no difference at all. Anyone running ESXi would
see that same results I am seeing anyways.

I want to see if the old sign-file.c code is simply using deprecated
calls and then rewrite/patch as needed. This means the OpenSSL involved
will be the production 3.2.0 release published today.



Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken