^~~~~~~~~~~~ /var/tmp/portage/net-misc/freerdp-2.0.0_rc4/work/freerdp-2.0.0-rc4/libfreerdp/crypto/tls.c: In function ‘tls_send_alert’: /var/tmp/portage/net-misc/freerdp-2.0.0_rc4/work/freerdp-2.0.0-rc4/libfreerdp/crypto/tls.c:1048:15: error: ‘struct ssl3_state_st’ has no member named ‘alert_dispatch’ tls->ssl->s3->alert_dispatch = 1; ^~ /var/tmp/portage/net-misc/freerdp-2.0.0_rc4/work/freerdp-2.0.0-rc4/libfreerdp/crypto/tls.c:1049:15: error: ‘struct ssl3_state_st’ has no member named ‘send_alert’ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_libressl_20190417-202422 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) [4] pypy (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) Available Rust versions: [1] rust-1.34.0 * emerge -qpvO net-misc/freerdp [ebuild R ] net-misc/freerdp-2.0.0_rc4 USE="client libressl -X -alsa -cups -debug -doc -ffmpeg -gstreamer -jpeg -libav (-neon) -openh264 -pulseaudio -server -smartcard -systemd -test -usb -wayland -xinerama -xv"
Created attachment 574014 [details] emerge-info.txt
Created attachment 574016 [details] emerge-history.txt
Created attachment 574018 [details] environment
Created attachment 574020 [details] etc.portage.tbz2
Created attachment 574022 [details] logs.tbz2
Created attachment 574024 [details] net-misc:freerdp-2.0.0_rc4:20190424-075120.log
Created attachment 574026 [details] temp.tbz2
Created attachment 574162 [details, diff] freerdp-libre291.patch well, some small set of compatibility bindings inside LibreSSL caught up to OpenSSL again. Had to update "defined(LIBRESSL_VERSION_NUMBER)" to "LIBRESSL_VERSION_NUMBER < 0x2090000f" and expand the logic to avoid the confusion the compiler will have with undefined (LIBRE/OPEN)SSL_VERSION_NUMBER variables. Time to talk to upstream again.
Looks like upstream has already caught the issue in their master branch. This patchfile still works.
If you link me to the upstream commits, I will backport them. Otherwise, I'll just wait for the next release candidate.
(In reply to Mike Gilbert from comment #10) > If you link me to the upstream commits, I will backport them. Otherwise, > I'll just wait for the next release candidate. Here it is: https://github.com/FreeRDP/FreeRDP/commit/0c83efa753d0457eb319624f87b491badf75105f Works for me.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6b4e5c994bbd5233a937240df9a3ff6c522703ac commit 6b4e5c994bbd5233a937240df9a3ff6c522703ac Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2019-09-29 20:48:11 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2019-09-29 20:48:11 +0000 net-misc/freerdp: another libressl fix Closes: https://bugs.gentoo.org/684294 Package-Manager: Portage-2.3.75_p7, Repoman-2.3.17_p49 Signed-off-by: Mike Gilbert <floppym@gentoo.org> net-misc/freerdp/files/2.0.0-rc4-libressl.patch | 31 +++++++++++++++++++++++++ 1 file changed, 31 insertions(+)
