> On 7 Feb 2024, at 18:53, Marco Aurelio wrote:
>
> I changed the path and now the correct version of openssl appears in the
> config.log, even so, after recompiling and reinstalling both postgresql and
> the pgcrypto contrib, when trying to create the extension in a database I
> continue to r
I changed the path and now the correct version of openssl appears in the
config.log, even so, after recompiling and reinstalling both postgresql and
the pgcrypto contrib, when trying to create the extension in a database I
continue to receive the same error, any further suggestions ?
Marco Aurélio
Marco Aurelio writes:
> I added the include and libraries folders:
> --with-libraries=/usr/local/lib --with-includes=/usr/local/include
> but configure keeps finding the old version of openssl
> configure:14133: checking for openssl
> configure:14151: found /usr/bin/openssl
> configure:14163: res
I added the include and libraries folders:
--with-libraries=/usr/local/lib --with-includes=/usr/local/include
but configure keeps finding the old version of openssl
configure:14133: checking for openssl
configure:14151: found /usr/bin/openssl
configure:14163: result: /usr/bin/openssl
configure:141
> On 7 Feb 2024, at 15:09, Marco Aurelio wrote:
> When I run ./configure I see in config.log that it is always using the base
> version of Freebsd.
You can use the --with-libraries and --with-includes arguments to ./configure
in order to point it to the version you want to build against.
--
Da
Dear Friends,
I have a Freebsd 13.2 server where I installed postgresql 16.1 via source
code, I installed the pgcrypto extension with the gmake install command
without error messages, but when trying to create the extension in a
database I receive the following message:
ERROR: could not load libra
