Ruby issue: Installed gems are not in path
Kevin Connor Arpe
Sat Nov 15 18:02:00 GMT 2014
Command "gem environment" should tell you where the binaries are installed.
I had the same issue on Friday. All the Googling I did couldn't help.
With a bit of luck, I discovered the binaries are usually installed in
"~/bin" for Cygwin.
Does it work for you?
On Sat, Nov 15, 2014 at 3:38 PM, Tallak Tveide <email@example.com> wrote:
> 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
> $ 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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin