pawel@freebsd.org writes:
> FreeBSD bug report (with patches):
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218736
> Build error:
> cc -O2 -pipe -march=native -fstack-protector -fno-strict-aliasing -Wall
> -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement
> -Wendif-labels -Wmissing-format-attribute -Wformat-security
> -fno-strict-aliasing -fwrapv -I../../../src/include -I/usr/local/include
> -I/usr/local/include/libxml2 -I/usr/include -I/usr/local/include
> -I/usr/local/include -c -o be-secure.o be-secure.c
> be-secure.c:341:19: error: no member named 'state' in 'struct ssl_st'
> if (port->ssl->state != SSL_ST_OK)
> ~~~~~~~~~ ^
> be-secure.c:345:15: error: no member named 'state' in 'struct ssl_st'
> port->ssl->state |= SSL_ST_ACCEPT;
> ~~~~~~~~~ ^
> be-secure.c:347:19: error: no member named 'state' in 'struct ssl_st'
> if (port->ssl->state != SSL_ST_OK)
> ~~~~~~~~~ ^
> 3 errors generated.
> gmake[2]: *** [<builtin>: be-secure.o] Error 1
> gmake[2]: Leaving directory
> '/usr/ports/databases/postgresql92-server/work/postgresql-9.2.20/src/backend/libpq'
This looks like it was probably addressed by the changes we made last
month to support OpenSSL 1.1.0 in our pre-9.5 branches. However, since
LibreSSL isn't identical to OpenSSL, it would sure be nice if someone
would verify compatibility before next week's update releases. Could
you test against our git branch tips or nightly snapshot tarballs?
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
