From: Greg.mpls@... Date: 2018-10-09T15:35:06+00:00 Subject: [ruby-core:89341] [Ruby trunk Feature#15171] OpenSSL 1.1.1 soon available from MSYS2 Issue #15171 has been updated by MSP-Greg (Greg L). @jaruga I'm not sure what you mean. Whenever I refer to a package, I'm referring to a pre-compiled package. MSYS2/MinGW has added CI on Azure pipelines, so I'm not sure if they build there or on Appveyor. Appveyor's packages are not always current, and as of this morning 2018-10-09, OpenSSL 1.0.2.p is installed. The MYS2/MinGW 'system' currently has 1.1.1 available. So, one can update the package in script using pacman, just like one would for updating any other package. ---------------------------------------- Feature #15171: OpenSSL 1.1.1 soon available from MSYS2 https://bugs.ruby-lang.org/issues/15171#change-74369 * Author: MSP-Greg (Greg L) * Status: Open * 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 -- https://bugs.ruby-lang.org/ Unsubscribe: