On 10/12/18 7:15 AM, Ádám Maracska wrote:
Hi,
Currently I am trying to compile my pqlib with SSL version 1.1.0, but I
get the following errors:
/
/
/fe-secure-openssl.c(1582): error C2037: left of 'ptr' specifies
undefined struct/union 'bio_st'/
/fe-secure-openssl.c(1582): error C2198: 'pqsecure_raw_read': too few
arguments for call/
/fe-secure-openssl.c(1612): error C2037: left of 'ptr' specifies
undefined struct/union 'bio_st'/
/fe-secure-openssl.c(1612): error C2198: 'pqsecure_raw_write': too few
arguments for call/
/fe-secure-openssl.c(1670): error C2027: use of undefined type
'bio_method_st'/
/fe-secure-openssl.c(1673): error C2027: use of undefined type
'bio_method_st'/
/fe-secure-openssl.c(1674): error C2037: left of 'bread' specifies
undefined struct/union 'bio_method_st'/
/fe-secure-openssl.c(1675): error C2037: left of 'bwrite' specifies
undefined struct/union 'bio_method_st'/
/fe-secure-openssl.c(1701): error C2037: left of 'ptr' specifies
undefined struct/union 'bio_st'/
As I was checking the issue on google I found the following two message
thread about it:
- From 2016: Based on this the ssl version 1.1 is supported, but the
message thread had not so promising end:
https://www.postgresql.org/message-id/flat/E1bkVG3-0000L8-Ln%40gemulon.postgresql.org
- From 2018: It had even more worse end. The questioner went back to
1.0.2 ssl version, which is not an option for me, because that version
will not be supported shortly by openssl itself.
https://www.postgresql.org/message-id/CAAw-Mseg9JYpp%3DA%3D51HR3rKiQtbvT0MWw%2BaYFwNeJEbdNr%3DCDA%40mail.gmail.com
Also I checked the source files and I saw these kind of comments:
/ They are also not needed with OpenSSL 1.1.0 anymore.
(fe-secure-openssl.c)/
/
/
I suppose it is possible to compile the pqlib with ssl 1.1, but I can
not wrap my head around it. Maybe I should set some ifdefs for the
precompiler beforehand?
I appreciate any help.
What OS and version of same are you compiling in?
Do you have the SSL dev libraries installed?
Best Regards,
Adam
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
