Ruby issue: Installed gems are not in path

Tallak Tveide tallak@tveide.net
Sat Nov 15 07:39:00 GMT 2014


When installing gems with the packaged Ruby, any command line binaries
that are included with installed gems are not available in the path.

When the gems have previously (meaning in an earlier installed version
of Ruby) been installed, they work as expected. I suspect this is
because the binaries in /usr/bin/xxx are already present before
installing the gem anew.

I have seen the same behavior on a colleage's machine

Example:

$ gem install t
Fetching: simple_oauth-0.3.0.gem (100%)
Successfully installed simple_oauth-0.3.0
Fetching: naught-1.0.0.gem (100%)
Successfully installed naught-1.0.0
<lots more output>
$ t
-bash: t: command not found

$ ruby --version
ruby 2.0.0p594 (2014-10-27) [i386-cygwin]

$ uname -a
CYGWIN_NT-6.1-WOW64 NOR-4911GS1 1.7.33-2(0.280/5/3) 2014-11-13 15:45 i686 Cygwin

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list