From: takashikkbn@... Date: 2019-08-18T06:55:20+00:00 Subject: [ruby-core:94414] [Ruby master Feature#15171] [patch] Use OpenSSL 1.1.1 for Appveyor MinGW build Issue #15171 has been updated by k0kubun (Takashi Kokubun). Status changed from Open to Closed Closing https://github.com/ruby/ruby/pull/1998#issuecomment-437700528 ---------------------------------------- Feature #15171: [patch] Use OpenSSL 1.1.1 for Appveyor MinGW build https://bugs.ruby-lang.org/issues/15171#change-80836 * Author: MSP-Greg (Greg L) * Status: Closed * Priority: Normal * Assignee: * Target version: ---------------------------------------- @nobu Thanks for your work with the Appveyor testing. It took three revisions, but MSYS2 has jumped from OpenSSL 1.0.2 to 1.1.1. The package release 1.1.1-4 should build fine on Appveyor MinGW. I don't think it has hit the MSYS2 repository yet, but certainly in the next 24 hours. If you've got MSYS2 installed, `pacman -Ss mingw-w64-x86_64-openssl` should show availability. But you knew that. Hence, line 122 of the current Appveyor.yml file would need mingw-w64-x86_64-openssl added to it. At present, Appveyor has got 1.0.2p. Lastly, given any thought to moving the VC builds to Azure? I may see if I can make both VC12 and VC14 OpenSSL packages. Seems inappropriate to load different runtimes with (I think) VC12. Greg ---Files-------------------------------- av_openssl_1.1.1.patch (2.09 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: