ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: duerst@it.aoyama.ac.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:72502] [Ruby trunk - Bug #11883] [Closed] Endless loop when installing bundle gems
Date: Sun, 27 Dec 2015 02:49:40 +0000	[thread overview]
Message-ID: <redmine.journal-55779.20151227024938.4616a7ffbe78a1fd@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11883.20151227001911@ruby-lang.org

Issue #11883 has been updated by Martin Dürst.

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

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

----------------------------------------
Bug #11883: Endless loop when installing bundle gems
https://bugs.ruby-lang.org/issues/11883#change-55779

* Author: Martin Dürst
* Status: Closed
* Priority: Normal
* Assignee: 
* 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
----------------------------------------
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.



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

      parent reply	other threads:[~2015-12-27  2:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-11883.20151227001911@ruby-lang.org>
2015-12-27  0:19 ` [ruby-core:72499] [Ruby trunk - Bug #11883] [Open] Endless loop when installing bundle gems duerst
2015-12-27  0:21 ` [ruby-core:72500] [Ruby trunk - Bug #11883] " duerst
2015-12-27  2:49 ` duerst [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-55779.20151227024938.4616a7ffbe78a1fd@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).