Issue #15171 has been updated by jaruga (Jun Aruga).


> At the bottom is the info output for the current trunk build. It's more than is needed, but, in addition to OpenSSL, there are packages that have version info that might be helpful when comparing builds...

I saw the ruby-loco's log now.
I am not sure how much the additional version info is useful.

Because we can check default gems' version from `ext/bigdecimal/bigdecimal.gemspec`, `ext/json/json.gemspec` and etc, and bundled gems' version from `gems/bundled_gems`.

In the case of openssl, as we might want to see actual built openssl's version, I thought above command was useful.


----------------------------------------
Feature #15171: OpenSSL 1.1.1 soon available from MSYS2
https://bugs.ruby-lang.org/issues/15171#change-74445

* 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>