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_THREAD -DUSE_OPENSSL -DUSE_SYSCALL_FUTEX -DUSE_SYSTEMD -DUSE_PCRE -I/usr/include -DUSE_TFO -DCONFIG_HAPROXY_VERSION=\"1.8.0\" -DCONFIG_HAPROXY_DATE=\"2017/11/26\" -c -o src/ssl_sock.o src/ssl_sock.c src/ssl_sock.c:61:10: fatal error: openssl/async.h: No such file or directory #include <openssl/async.h> ^~~~~~~~~~~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma-systemd_libressl-test_20171129-194156 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python3.5 (fallback) [4] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv net-proxy/haproxy [ebuild N ] net-proxy/haproxy-1.8.0 USE="crypt libressl pcre ssl systemd threads zlib (-51degrees) -device-atlas -doc -examples (-lua) -net_ns -pcre-jit -pcre2 -pcre2-jit -slz -tools -vim-syntax (-wurfl)"
Created attachment 507398 [details] emerge-info.txt
Created attachment 507400 [details] emerge-history.txt
Created attachment 507402 [details] environment
Created attachment 507404 [details] etc.portage.tbz2
Created attachment 507406 [details] net-proxy:haproxy-1.8.0:20171130-152342.log
Created attachment 507408 [details] temp.tbz2
@Toral: Could you try that with OpenSSL please? Someone with libressl would have to take a look.
(In reply to Christian Ruppert (idl0r) from comment #7) no problem so far with OpenSSL , this is a LibreSSL thingy
(In reply to Toralf Förster from comment #8) > (In reply to Christian Ruppert (idl0r) from comment #7) > no problem so far with OpenSSL , this is a LibreSSL thingy I'm afraid I can't help right now. We probably have to ask the one who added libressl support into the HAProxy ebuild, which seems to be blueness.
Can you verify if this is still a thing with 1.8.3 ?
(In reply to Bertrand Jacquin from comment #10) yes: x86_64-pc-linux-gnu-gcc -Iinclude -Iebtree -Wall -O2 -pipe -march=native -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_THREAD -DUSE_OPENSSL -DUSE_SYSCALL_FUTEX -DUSE_PCRE -I/usr/include -DUSE_TFO -DCONFIG_HAPROXY_VERSION=\"1.8.3-205f675\" -DCONFIG_HAPROXY_DATE=\"2017/12/30\" -c -o src/ssl_sock.o src/ssl_sock.c src/ssl_sock.c:61:10: fatal error: openssl/async.h: No such file or directory #include <openssl/async.h> ^~~~~~~~~~~~~~~~~ compilation terminated.
Is this still an issue with e.g. 1.9.6? If yes, then we probably need to Cc/assign it to the libressl guys and if necessary fixing it together with HAProxy upstream.
(In reply to Christian Ruppert (idl0r) from comment #12) > Is this still an issue with e.g. 1.9.6? If yes, then we probably need to > Cc/assign it to the libressl guys and if necessary fixing it together with > HAProxy upstream. +1 still a problem
