public inbox for [email protected]
help / color / mirror / Atom feedLibpq linked statically linked to OpenSSL/LibreSSL
10+ messages / 4 participants
[nested] [flat]
* Libpq linked statically linked to OpenSSL/LibreSSL
@ 2022-12-04 13:22 Marco Bambini <[email protected]>
2022-12-05 12:48 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
0 siblings, 1 reply; 10+ messages in thread
From: Marco Bambini @ 2022-12-04 13:22 UTC (permalink / raw)
To: [email protected]
Hi all,
After several attempts, I am asking for help with how to compile libpq with OpenSSL statically linked.
I need to have libpq linked with LibreSSL, but if I could statically link OpenSSL, I think I could switch the TLS libraries at compile time.
Any help would be really appreciated.
Thanks,
Marco
^ permalink raw reply [nested|flat] 10+ messages in thread
* RE: Libpq linked statically linked to OpenSSL/LibreSSL
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
@ 2022-12-05 12:48 ` ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 13:10 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
0 siblings, 1 reply; 10+ messages in thread
From: ALBERTO CABELLO SÁNCHEZ @ 2022-12-05 12:48 UTC (permalink / raw)
To: Marco Bambini <[email protected]>; [email protected] <[email protected]>
> Hi all,
>
> After several attempts, I am asking for help with how to compile libpq with OpenSSL
> statically linked.
> I need to have libpq linked with LibreSSL, but if I could statically link OpenSSL, I think
> I could switch the TLS libraries at compile time.
Hi,
I'm not sure if it will work this way, but I think you could build libpq from source, then
enter src/interfaces/libpq and rebuild the final libpq manually including libssl.a, so redo
the step which creates libpq.so
gcc (blah blah blah) -o libpq.so.5.15 (more blah blah)
appending your libssl.a location (mine is /usr/lib/x86_64-linux-gnu/libssl.a) at the end.
It look prettier if you add it to the list of input ".o" files. You'll end with a bigger libpq.so.
That "15" is the PostgreSQL major version number. Yours could be different.
Hope that helps.
^ permalink raw reply [nested|flat] 10+ messages in thread
* RE: Libpq linked statically linked to OpenSSL/LibreSSL
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-05 12:48 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
@ 2022-12-05 13:10 ` ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 16:47 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
0 siblings, 1 reply; 10+ messages in thread
From: ALBERTO CABELLO SÁNCHEZ @ 2022-12-05 13:10 UTC (permalink / raw)
To: Marco Bambini <[email protected]>; [email protected] <[email protected]>
>> Hi all,
>>
>> After several attempts, I am asking for help with how to compile libpq with OpenSSL
>> statically linked.
>> I need to have libpq linked with LibreSSL, but if I could statically link OpenSSL, I think
>> I could switch the TLS libraries at compile time.
>
> redo the step which creates libpq.so appending your libssl.a location
> (mine is /usr/lib/x86_64-linux-gnu/libssl.a) at the end.
Just wanted to correct: you also have to remove "-lssl". So I guess you can just
substitute "-lssl" for libssl.a location in src/interfaces/libpq/Makefile (two occurrences)
and build as usual.
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Libpq linked statically linked to OpenSSL/LibreSSL
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-05 12:48 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 13:10 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
@ 2022-12-05 16:47 ` Marco Bambini <[email protected]>
2022-12-06 10:05 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
0 siblings, 1 reply; 10+ messages in thread
From: Marco Bambini @ 2022-12-05 16:47 UTC (permalink / raw)
To: ALBERTO CABELLO SÁNCHEZ <[email protected]>; +Cc: [email protected] <[email protected]>
Thanks Alberto,
This is a very promising approach.
I tried to modify the Makefile in src/interfaces/libpq/Makefile and I replaced the occurrences of -lssl and -lcrypto with:
/root/rothsoft/libressl-3.6.1/ssl/.libs/libssl.a
/root/rothsoft/libressl-3.6.1/crypto/.libs/libcrypto.a
The compilation process is OK but when I tried to execute the test app I receive a link error:
Error loading DLL: /root/rothsoft/engines/postgreSQL/Linux/postgresql/libpq.so: undefined symbol: GENERAL_NAME_free
GENERAL_NAME_free usually means that libcrypto is missed.
Any help would be really appreciated.
Please note that I also tried with:
-l:/root/rothsoft/libressl-3.6.1/ssl/.libs/libssl.a
-l:/root/rothsoft/libressl-3.6.1/crypto/.libs/libcrypto.a
Thanks,
Marco
> On 5 Dec 2022, at 14:10, ALBERTO CABELLO SÁNCHEZ <[email protected]> wrote:
>
>>> Hi all,
>>>
>>> After several attempts, I am asking for help with how to compile libpq with OpenSSL
>>> statically linked.
>>> I need to have libpq linked with LibreSSL, but if I could statically link OpenSSL, I think
>>> I could switch the TLS libraries at compile time.
>>
>> redo the step which creates libpq.so appending your libssl.a location
>> (mine is /usr/lib/x86_64-linux-gnu/libssl.a) at the end.
>
> Just wanted to correct: you also have to remove "-lssl". So I guess you can just
> substitute "-lssl" for libssl.a location in src/interfaces/libpq/Makefile (two occurrences)
> and build as usual.
>
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Libpq linked statically linked to OpenSSL/LibreSSL
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-05 12:48 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 13:10 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 16:47 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
@ 2022-12-06 10:05 ` Marco Bambini <[email protected]>
2022-12-06 18:01 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Andres Freund <[email protected]>
0 siblings, 1 reply; 10+ messages in thread
From: Marco Bambini @ 2022-12-06 10:05 UTC (permalink / raw)
To: ALBERTO CABELLO SÁNCHEZ <[email protected]>; +Cc: [email protected] <[email protected]>
Hi,
I made some progresses, especially in understanding where the issue can be.
I started with a fresh postgresql-15.1 source code installation:
# ./configure --with-openssl --without-readline
I then modified the Makefile.global in the src directory by replacing the occurrences of -lssl and -lcrypto with:
/root/rothsoft/libressl-3.6.1/ssl/.libs/libssl.a /root/rothsoft/libressl-3.6.1/crypto/.libs/libcrypto.a
in the LIBS entry.
Then from src/interfaces/libpq I executed:
# make
libpq was successfully created but when I perform a:
# nm -D libpq.so
the output looks like:
000000000001f110 T appendBinaryPQExpBuffer
000000000001f000 T appendPQExpBuffer
000000000001f0d0 T appendPQExpBufferChar
000000000001f150 T appendPQExpBufferStr
U ASN1_STRING_data
U ASN1_STRING_length
U BIO_clear_flags
U BIO_int_ctrl
U BIO_new
U BIO_set_flags
U BIO_s_socket
U calloc
U close
U connect
000000000001ecd0 T createPQExpBuffer
U CRYPTO_get_id_callback
U CRYPTO_get_locking_callback
U CRYPTO_num_locks
U CRYPTO_set_id_callback
U CRYPTO_set_locking_callback
U __ctype_b_loc
U __ctype_tolower_loc
U __ctype_toupper_loc
w __cxa_finalize
000000000001ed30 T destroyPQExpBuffer
U ENGINE_by_id
U ENGINE_finish
U ENGINE_free
U ENGINE_init
U ENGINE_load_private_key
000000000001ed90 T enlargePQExpBuffer
U ERR_clear_error
U ERR_get_error
U __errno_location
U ERR_put_error
U ERR_reason_error_string
U EVP_DigestFinal_ex
U EVP_DigestInit_ex
...
Please notice all the U entries in the crypto/ssl functions, so it looks like that they are NOT statically linked inside the libpq.so shared library, even if I replaced the LIBS in the Makefile.
Anyone can help me with this issue?
Thanks,
Marco
> On 5 Dec 2022, at 17:47, Marco Bambini <[email protected]> wrote:
>
> Thanks Alberto,
>
> This is a very promising approach.
>
> I tried to modify the Makefile in src/interfaces/libpq/Makefile and I replaced the occurrences of -lssl and -lcrypto with:
> /root/rothsoft/libressl-3.6.1/ssl/.libs/libssl.a
> /root/rothsoft/libressl-3.6.1/crypto/.libs/libcrypto.a
>
> The compilation process is OK but when I tried to execute the test app I receive a link error:
> Error loading DLL: /root/rothsoft/engines/postgreSQL/Linux/postgresql/libpq.so: undefined symbol: GENERAL_NAME_free
>
> GENERAL_NAME_free usually means that libcrypto is missed.
>
> Any help would be really appreciated.
>
> Please note that I also tried with:
> -l:/root/rothsoft/libressl-3.6.1/ssl/.libs/libssl.a
> -l:/root/rothsoft/libressl-3.6.1/crypto/.libs/libcrypto.a
>
> Thanks,
> Marco
>
>
>> On 5 Dec 2022, at 14:10, ALBERTO CABELLO SÁNCHEZ <[email protected]> wrote:
>>
>>>> Hi all,
>>>>
>>>> After several attempts, I am asking for help with how to compile libpq with OpenSSL
>>>> statically linked.
>>>> I need to have libpq linked with LibreSSL, but if I could statically link OpenSSL, I think
>>>> I could switch the TLS libraries at compile time.
>>>
>>> redo the step which creates libpq.so appending your libssl.a location
>>> (mine is /usr/lib/x86_64-linux-gnu/libssl.a) at the end.
>>
>> Just wanted to correct: you also have to remove "-lssl". So I guess you can just
>> substitute "-lssl" for libssl.a location in src/interfaces/libpq/Makefile (two occurrences)
>> and build as usual.
>>
>
>
>
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Libpq linked statically linked to OpenSSL/LibreSSL
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-05 12:48 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 13:10 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 16:47 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-06 10:05 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
@ 2022-12-06 18:01 ` Andres Freund <[email protected]>
2022-12-06 18:24 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Bruce Momjian <[email protected]>
2022-12-08 06:07 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
0 siblings, 2 replies; 10+ messages in thread
From: Andres Freund @ 2022-12-06 18:01 UTC (permalink / raw)
To: Marco Bambini <[email protected]>; +Cc: ALBERTO CABELLO SÁNCHEZ <[email protected]>; [email protected] <[email protected]>
Hi,
On 2022-12-06 11:05:49 +0100, Marco Bambini wrote:
> I made some progresses, especially in understanding where the issue can be.
>
> I started with a fresh postgresql-15.1 source code installation:
> # ./configure --with-openssl --without-readline
>
> I then modified the Makefile.global in the src directory by replacing the occurrences of -lssl and -lcrypto with:
> /root/rothsoft/libressl-3.6.1/ssl/.libs/libssl.a /root/rothsoft/libressl-3.6.1/crypto/.libs/libcrypto.a
> in the LIBS entry.
I think this is completely the wrong path. You should add libressl's include
and library directories to --with-includes=, --with-libraries=.
> Please notice all the U entries in the crypto/ssl functions, so it looks like that they are NOT statically linked inside the libpq.so shared library, even if I replaced the LIBS in the Makefile.
If there's also a shared version of libressl, you possibly would need to
specify that you'd want to link statically. Something like
-Wl,-Bstatic -lssl -lcrypto -Wl,-Bdynamic
But I suspect that you're better of linking dynamically, specifying
--with-includes= --with-libraries= should provide a path towards that. It's
possible that you should add -Wl,-rpath,/path/to/libressl/lib to the LDFLAGS,
so that the dynamic version can be found at runtime.
Greetings,
Andres Freund
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Libpq linked statically linked to OpenSSL/LibreSSL
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-05 12:48 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 13:10 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 16:47 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-06 10:05 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-06 18:01 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Andres Freund <[email protected]>
@ 2022-12-06 18:24 ` Bruce Momjian <[email protected]>
1 sibling, 0 replies; 10+ messages in thread
From: Bruce Momjian @ 2022-12-06 18:24 UTC (permalink / raw)
To: Andres Freund <[email protected]>; +Cc: Marco Bambini <[email protected]>; ALBERTO CABELLO SÁNCHEZ <[email protected]>; [email protected] <[email protected]>
On Tue, Dec 6, 2022 at 10:01:00AM -0800, Andres Freund wrote:
> > I then modified the Makefile.global in the src directory by replacing the occurrences of -lssl and -lcrypto with:
> > /root/rothsoft/libressl-3.6.1/ssl/.libs/libssl.a /root/rothsoft/libressl-3.6.1/crypto/.libs/libcrypto.a
> > in the LIBS entry.
>
> I think this is completely the wrong path. You should add libressl's include
> and library directories to --with-includes=, --with-libraries=.
The big point is that a compile-compatible library is not necessarily a
link-compatible library, and that LibreSSL is probably only
compile-compatible with OpenSSL, hence the need to use the LibreSSL
includes.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Embrace your flaws. They make you human, rather than perfect,
which you will never be.
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Libpq linked statically linked to OpenSSL/LibreSSL
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-05 12:48 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 13:10 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 16:47 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-06 10:05 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-06 18:01 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Andres Freund <[email protected]>
@ 2022-12-08 06:07 ` Marco Bambini <[email protected]>
2022-12-09 08:00 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
1 sibling, 1 reply; 10+ messages in thread
From: Marco Bambini @ 2022-12-08 06:07 UTC (permalink / raw)
To: Andres Freund <[email protected]>; +Cc: ALBERTO CABELLO SÁNCHEZ <[email protected]>; [email protected] <[email protected]>
Hi all,
I tried to follow the advices from Andreas but without any luck.
I added the --with-includes=, --with-libraries= arguments to the configure command (with path to my static LibreSSL libraries) and I also modified the Makefile.global with:
-Wl,-Bstatic -lssl -lcrypto -Wl,-Bdynamic
The resulting libpq.so is bigger (in size) than the previous one but it continues to try to dynamically load the SSL functions.
# nm -D libpq.so
the output looks like:
000000000001f110 T appendBinaryPQExpBuffer
000000000001f000 T appendPQExpBuffer
000000000001f0d0 T appendPQExpBufferChar
000000000001f150 T appendPQExpBufferStr
U ASN1_STRING_data
U ASN1_STRING_length
U BIO_clear_flags
U BIO_int_ctrl
U BIO_new
U BIO_set_flags
U BIO_s_socket
U calloc
U close
U connect
000000000001ecd0 T createPQExpBuffer
U CRYPTO_get_id_callback
U CRYPTO_get_locking_callback
U CRYPTO_num_locks
U CRYPTO_set_id_callback
U CRYPTO_set_locking_callback
U __ctype_b_loc
U __ctype_tolower_loc
U __ctype_toupper_loc
w __cxa_finalize
000000000001ed30 T destroyPQExpBuffer
U ENGINE_by_id
U ENGINE_finish
U ENGINE_free
U ENGINE_init
U ENGINE_load_private_key
000000000001ed90 T enlargePQExpBuffer
U ERR_clear_error
U ERR_get_error
U __errno_location
U ERR_put_error
U ERR_reason_error_string
U EVP_DigestFinal_ex
U EVP_DigestInit_ex
I really don't know why it is so difficult to have the SSL libraries statically linked to libpq.
Any help would be greatly appreciated.
Thanks,
Marco
> On 6 Dec 2022, at 19:01, Andres Freund <[email protected]> wrote:
>
> Hi,
>
> On 2022-12-06 11:05:49 +0100, Marco Bambini wrote:
>> I made some progresses, especially in understanding where the issue can be.
>>
>> I started with a fresh postgresql-15.1 source code installation:
>> # ./configure --with-openssl --without-readline
>>
>> I then modified the Makefile.global in the src directory by replacing the occurrences of -lssl and -lcrypto with:
>> /root/rothsoft/libressl-3.6.1/ssl/.libs/libssl.a /root/rothsoft/libressl-3.6.1/crypto/.libs/libcrypto.a
>> in the LIBS entry.
>
> I think this is completely the wrong path. You should add libressl's include
> and library directories to --with-includes=, --with-libraries=.
>
>
>> Please notice all the U entries in the crypto/ssl functions, so it looks like that they are NOT statically linked inside the libpq.so shared library, even if I replaced the LIBS in the Makefile.
>
> If there's also a shared version of libressl, you possibly would need to
> specify that you'd want to link statically. Something like
> -Wl,-Bstatic -lssl -lcrypto -Wl,-Bdynamic
>
> But I suspect that you're better of linking dynamically, specifying
> --with-includes= --with-libraries= should provide a path towards that. It's
> possible that you should add -Wl,-rpath,/path/to/libressl/lib to the LDFLAGS,
> so that the dynamic version can be found at runtime.
>
> Greetings,
>
> Andres Freund
^ permalink raw reply [nested|flat] 10+ messages in thread
* RE: Libpq linked statically linked to OpenSSL/LibreSSL
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-05 12:48 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 13:10 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 16:47 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-06 10:05 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-06 18:01 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Andres Freund <[email protected]>
2022-12-08 06:07 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
@ 2022-12-09 08:00 ` ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-10 07:55 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
0 siblings, 1 reply; 10+ messages in thread
From: ALBERTO CABELLO SÁNCHEZ @ 2022-12-09 08:00 UTC (permalink / raw)
To: Marco Bambini <[email protected]>; Andres Freund <[email protected]>; +Cc: [email protected] <[email protected]>
> Marco Bambini <[email protected]> wrote:
>
> I tried to follow the advices from Andreas but without any luck.
> I added the --with-includes=, --with-libraries= arguments to the configure
> command (with path to my static LibreSSL libraries) and I also modified the Makefile.global with:
> -Wl,-Bstatic -lssl -lcrypto -Wl,-Bdynamic
>
> The resulting libpq.so is bigger (in size) than the previous one but it continues
> to try to dynamically load the SSL functions.
This was also the result I got, -lssl seems to leave without effect the "-with-*" options.
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Libpq linked statically linked to OpenSSL/LibreSSL
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-05 12:48 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 13:10 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 16:47 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-06 10:05 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-06 18:01 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Andres Freund <[email protected]>
2022-12-08 06:07 ` Re: Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-09 08:00 ` RE: Libpq linked statically linked to OpenSSL/LibreSSL ALBERTO CABELLO SÁNCHEZ <[email protected]>
@ 2022-12-10 07:55 ` Marco Bambini <[email protected]>
0 siblings, 0 replies; 10+ messages in thread
From: Marco Bambini @ 2022-12-10 07:55 UTC (permalink / raw)
To: ALBERTO CABELLO SÁNCHEZ <[email protected]>; +Cc: Andres Freund <[email protected]>; [email protected] <[email protected]>
What sounds really odd is that I replaced all the occurrences of -lssl -lcrypto with the full path to the static libraries in all involved Makefile, but the resulting libpq.so library still has undefined links to the SSL functions.
> On 9 Dec 2022, at 09:00, ALBERTO CABELLO SÁNCHEZ <[email protected]> wrote:
>
>> Marco Bambini <[email protected]> wrote:
>>
>> I tried to follow the advices from Andreas but without any luck.
>> I added the --with-includes=, --with-libraries= arguments to the configure
>> command (with path to my static LibreSSL libraries) and I also modified the Makefile.global with:
>> -Wl,-Bstatic -lssl -lcrypto -Wl,-Bdynamic
>>
>> The resulting libpq.so is bigger (in size) than the previous one but it continues
>> to try to dynamically load the SSL functions.
>
> This was also the result I got, -lssl seems to leave without effect the "-with-*" options.
^ permalink raw reply [nested|flat] 10+ messages in thread
end of thread, other threads:[~2022-12-10 07:55 UTC | newest]
Thread overview: 10+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-12-04 13:22 Libpq linked statically linked to OpenSSL/LibreSSL Marco Bambini <[email protected]>
2022-12-05 12:48 ` ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 13:10 ` ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-05 16:47 ` Marco Bambini <[email protected]>
2022-12-06 10:05 ` Marco Bambini <[email protected]>
2022-12-06 18:01 ` Andres Freund <[email protected]>
2022-12-06 18:24 ` Bruce Momjian <[email protected]>
2022-12-08 06:07 ` Marco Bambini <[email protected]>
2022-12-09 08:00 ` ALBERTO CABELLO SÁNCHEZ <[email protected]>
2022-12-10 07:55 ` Marco Bambini <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox