Bug #11883: Endless loop when installing bundle gems

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-cygwin]
• Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN

[duerst (Martin Dürst)]

When trying to compile/install ruby with "make up; make install", everything stalls when trying to install bundle gems (see below for output). An instance of ruby can be observed taking up all CPU time available. This is usually a very fast step, but I had to kill it every time I tried (the longest after more than 15 minutes). Similar problems with endless loops occurred earlier in the build process, but I was able to eliminate them with "./configure --with-baseruby=/usr/bin/ruby.exe.

-------------- Last part of output:
installing default gems: /usr/local/lib/ruby/gems/2.4.0 (build_info, cache, doc, extensions, gems, specifications)
bigdecimal 1.2.8
io-console 0.4.5
json 1.8.3
psych 2.0.17
rdoc 4.2.1
installing bundle gems: /usr/local/lib/ruby/gems/2.4.0 (build_info, cache, doc, extensions, gems, specifications)
-------------- The line above is the last line of input, where the build process gets stuck.

[duerst (Martin Dürst)]

The value in "ruby -v" is what I get back when just typing that command. However, the process I have to kill is clearly marked as "Ruby interpreter (CUI) 2.4.0dev [x86_64-cygwin]".

[duerst (Martin Dürst)]

• Status changed from Open to Closed
• Assignee deleted (nobu (Nobuyoshi Nakada))

Problem disappeared. Maybe fixed by r53324 or r53325, but unclear why.