Michael Nolan writes:
> Including --with-openssl does include the crypto library, but if I
> don't do a 'make clean' before doing a make, I get errors when
> compiling postgresql. Apparently is it always a good idea to do make
> clean when reconfiguring postgresql.
Indeed. In theory, if you use
No, it wasn't there, because I hadn't included --with-openssl in the
configure. Looking at my history, I had done that once earlier but
dropped it for the reason noted below.
Including --with-openssl does include the crypto library, but if I
don't do a 'make clean' before doing a make, I get erro
Michael Nolan writes:
> Writing or debugging makefiles is something I haven't done much of,
> but as best I can figure out the problem is that the libcrypto.so file
> isn't being linked in, though this line in the Makefile in pgcrypto
> seems to say should be:
> SHLIB_LINK += $(filter -lcrypto -l
Sorry, I meant 'make check'. :sigh:
Writing or debugging makefiles is something I haven't done much of,
but as best I can figure out the problem is that the libcrypto.so file
isn't being linked in, though this line in the Makefile in pgcrypto
seems to say should be:
SHLIB_LINK += $(filter -lcrypto -lz, $(LIBS))
I'm guessing it is s
On Thu, Jan 18, 2024 at 9:51 AM Tom Lane wrote:
>
> Looks like we have aarch64 and ppc64 machines running Alma 8 and 9.
> No x86 though, which might matter for such a low-level failure
> as this.
So I guess that'll be on the list to add to the build farm at some
point? (My Xanthian 'talent' of f
Michael Nolan writes:
> Would I be correct to assume the postgresql build farm doesn't include
> AlmaLinux 9 to test it.
No, you wouldn't:
https://buildfarm.postgresql.org/cgi-bin/show_status.pl
Looks like we have aarch64 and ppc64 machines running Alma 8 and 9.
No x86 though, which might matte
On Thu, Jan 18, 2024 at 5:03 AM Daniel Gustafsson wrote:
>
> > On 18 Jan 2024, at 00:59, Michael Nolan wrote:
> > On Wed, Jan 17, 2024 at 5:32 PM Daniel Gustafsson wrote:
> >>
>
> That's surprising, I expected that it would require the legacy provider be
> loaded, not the other way around. Open
> On 18 Jan 2024, at 00:59, Michael Nolan wrote:
> On Wed, Jan 17, 2024 at 5:32 PM Daniel Gustafsson wrote:
>>
>>> On 18 Jan 2024, at 00:24, Michael Nolan wrote:
>>> I reinstalled the devel package, still get the same unresolved symbol error.
>>
>> My memory is failing me, but isn't CAST5 onl
On Wed, Jan 17, 2024 at 5:32 PM Daniel Gustafsson wrote:
>
> > On 18 Jan 2024, at 00:24, Michael Nolan wrote:
> >
> > Sorry for the delay in responding, network issues kept me offline for
> > several days.
> >
> > These are the openssl packages installed from the Almalinux 9 repositories:
> >
> >
> On 18 Jan 2024, at 00:24, Michael Nolan wrote:
>
> Sorry for the delay in responding, network issues kept me offline for
> several days.
>
> These are the openssl packages installed from the Almalinux 9 repositories:
>
> apr-util-openssl.x86_64 1.6.1-23.el9
>
Sorry for the delay in responding, network issues kept me offline for
several days.
These are the openssl packages installed from the Almalinux 9 repositories:
apr-util-openssl.x86_64 1.6.1-23.el9 @appstream
openssl.x86_641:3.0.7-24.el9
Michael Nolan writes:
> This is on AlmaLinux 9.3, installing postgresql from source code.
> In PG 16.1 when I try to install pgcrypto, the modules compile but I
> get this error when running checks:
> CREATE EXTENSION pgcrypto;
> +ERROR: could not load library
> "/home/postgres/src/postgresql-1
This is on AlmaLinux 9.3, installing postgresql from source code.
In PG 16.1 when I try to install pgcrypto, the modules compile but I
get this error when running checks:
CREATE EXTENSION pgcrypto;
+ERROR: could not load library
"/home/postgres/src/postgresql-16.1/tmp_install/usr/local/pgsql/li
14 matches
Mail list logo
