From: eregontp@... Date: 2016-01-03T11:37:42+00:00 Subject: [ruby-core:72686] [Ruby trunk - Bug #11937] did_you_mean and other bundled gems are not installed by make install Issue #11937 has been updated by Benoit Daloze. Nobuyoshi Nakada wrote: > Doesn't `make up` do it? I guess it would, however I think there are two problems: 1) Why and when should I do a `make up`? And where is it documented it should be part of the the build process? (make help does not mention it for instance) 2) It does currently not work for me: $ make up Network connection closed unexpectedly: Unable to connect to a repository at URL 'svn+ssh://svn@ci.ruby-lang.org/ruby': To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. at /usr/share/perl5/vendor_perl/Git/SVN.pm line 712. Makefile:465: recipe for target 'up' failed make: *** [up] Error 1 ---------------------------------------- Bug #11937: did_you_mean and other bundled gems are not installed by make install https://bugs.ruby-lang.org/issues/11937#change-55935 * Author: Benoit Daloze * Status: Feedback * Priority: Normal * Assignee: * ruby -v: ruby 2.4.0dev (2015-12-30 trunk 53388) [x86_64-linux] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- did_you_mean and other bundled gems are not installed when doing a regular local build: autoconf ./configure --prefix=... make install .../bin/ruby -e 'require "did_you_mean"' => LoadError `make update-gems` before `make install` will make it work, but this should be automatic (if no gems in gems/, download them and when gems/bundled_gems change fetch the new ones) or at least documented. -- https://bugs.ruby-lang.org/ Unsubscribe: