x86_64-pc-linux-gnu-gcc -Iinclude -Iebtree -Wall -O2 -pipe -march=native -Wall -fno-strict-aliasing -DCONFIG_HAP_LINUX_SPLICE -DTPROXY -DCONFIG_HAP_LINUX_TPROXY -DCONFIG_HAP_CRYPT -DUSE_GETADDRINFO -DUSE_ZLIB -DENABLE_POLL -DENABLE_EPOLL -DUSE_CPU_AFFINITY -DASSUME_SPLICE_WORKS -DUSE_ACCEPT4 -DNETFILTER -DUSE_GETSOCKNAME -DUSE_OPENSSL -DUSE_SYSCALL_FUTEX -DUSE_PCRE -I/usr/include -DUSE_TFO -DCONFIG_HAPROXY_VERSION=\"1.7.2\" -DCONFIG_HAPROXY_DATE=\"2017/01/13\" -c -o src/ssl_sock.o src/ssl_sock.c src/ssl_sock.c: In function ‘ssl_sock_load_ocsp’: src/ssl_sock.c:796:28: error: ‘SSL_CTX {aka struct ssl_ctx_st}’ has no member named ‘tlsext_status_cb’ *cb = (void (*) (void))ctx->tlsext_status_cb; ^ src/ssl_sock.c:798:2: note: in expansion of macro ‘SSL_CTX_get_tlsext_status_cb’ ----------------------------------------------------------------- This is an unstable amd64 chroot image (named 13.0-systemd-libressl-unstable_20170130-102323) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * llvm-config --version: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: -----------------------------------------------------------------
Created attachment 462588 [details] emerge-info.txt
Created attachment 462590 [details] emerge-history.txt
Created attachment 462592 [details] environment
Created attachment 462594 [details] etc.portage.tbz2
Created attachment 462596 [details] net-proxy:haproxy-1.7.2:20170205-231000.log
Created attachment 492158 [details, diff] haproxy-1.7.9-libressl.patch This patch solve the problem https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218637
Can you verify if this bug is still a thing with 1.7.10 ?