| From: | Michael Nolan <htfoot(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| 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 14:55:34 |
| Message-ID: | CAOzAquJM5yJiw8JBsE-DnWdNGYqOf+yJcRahiJqPs3d09sWcNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 18, 2024 at 5:03 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > 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:
> >>
>
> 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
>
Turns out that was premature, when I rebuilt postgres to add other
modules I needed, like plperl, the missing symbols issue came back.
So now I'm not sure why it (apparently briefly) worked. I'm assuming
it's an issue with the AlmaLinux 9 version of openssl. I don't know if
compiling it from source would fix the problem, but I may try that
after checking with the AlmaLinux folks.
Would I be correct to assume the postgresql build farm doesn't include
AlmaLinux 9 to test it.
Mike Nolan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-01-18 15:51:48 | Re: undefined symbol when installing pgcrypto on 16.1 |
| Previous Message | Daniel Gustafsson | 2024-01-18 14:27:45 | Re: Obtaining printed copies of the PostgreSQL manual |