Re: undefined symbol when installing pgcrypto on 16.1

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Nolan <htfoot(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: undefined symbol when installing pgcrypto on 16.1
Date: 2024-01-18 11:03:04
Message-ID: F8FD4AF2-AE6A-4D6F-9B1A-F2121F294E47@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On 18 Jan 2024, at 00:59, Michael Nolan <htfoot(at)gmail(dot)com> wrote:
> On Wed, Jan 17, 2024 at 5:32 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>>
>>> On 18 Jan 2024, at 00:24, Michael Nolan <htfoot(at)gmail(dot)com> wrote:

>>> I reinstalled the devel package, still get the same unresolved symbol error.
>>
>> My memory is failing me, but isn't CAST5 only available when loading the legacy
>> provider in OpenSSL 3? Which providers are loaded in your openssl config?
>
> The legacy providers were enabled, disabling them worked. (The build
> took a lot longer, too, but there were no obvious messages about
> problems with the legacy providers enabled untilI ran the check.)

That's surprising, I expected that it would require the legacy provider be
loaded, not the other way around. OpenSSL works in mysterious ways though.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2024-01-18 12:34:56 Re: Nested-Internal Functions
Previous Message Rossana Ocampos 2024-01-18 08:47:06 AW: Nested-Internal Functions