Issue #7427 has been updated by jonforums (Jon Forums).


Don't worry about installing a toolchain and double check that you have a minimal PATH and clean env vars; no pointers to an existing cygwin or mingw install.

We've made the build recipes self-contained so you don't have to worry about installing toolchains, using env vars to influence configure, etc. The `rake ruby19 ...` command first downloads all it needs into a download cache and then extracts, configures, and builds everything in a sandbox. There's other things (`rake -T`) you can do (build with a toolchain listed in `rake devkit:ls`) but my quick start should work.

re: WinXP 32bit...I don't have an XP system any more but I believe Hiroshi has semi-recently built on XP. If you run into compile/link errors with mingw64-32-4.7.2, do a `rake clean` (keeps the file download cache) followed by `rake ruby19 local=c:\projects\ruby dkver=mingw-32-4.6.2` to build with the mingw.org toolkit rather than the mingw-w64 toolkit. They both should work even though there are header differences. The key (irrelevant to your scenario but an fyi) is to not mix-n-match building ruby with one toolkit while building a native gem with a different toolkit.

Good luck.

Hiroshi...any issues you've had building on XP 32bit I've forgotten?
----------------------------------------
Feature #7427: Update Rubygems
https://bugs.ruby-lang.org/issues/7427#change-34245

Author: mame (Yusuke Endoh)
Status: Closed
Priority: Urgent
Assignee: drbrain (Eric Hodel)
Category: 
Target version: 2.0.0


Eric Hodel is planning to update Rubygems by the end of November.
See [ruby-core:48212].

Eric, what's the status?

-- 
Yusuke Endoh <mame / tsg.ne.jp>


-- 
http://bugs.ruby-lang.org/