X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:date:message-id:subject:from:to :content-type; q=dns; s=default; b=mz3ntFYazU2eK60f85L6wCZ8iYRhX wqMg91QOh0Ct/wMihP9AZRh1TyryYr0YuhkZizkOozk1O5gWLp6RYgFDGaztxrpS IwO+y0pyaiBMku8UHjOLIuoywzb+iKTOaBmjIgZ884bx8XLnUkeOu/AKpyjbagOG IBmHN4VKOvqHCo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:date:message-id:subject:from:to :content-type; s=default; bh=P0uVvq4WdPONIf6IdJ+gzGzudPQ=; b=Iz7 OO/oRRwbAbHHOEEIlaXJF8+wpnSfZ17xqLYNgeZqcIl1iQrl5l+qBuAGJYuG5Gwe l5rflK0/QH1TBY5a0AF3O2kM7KSITjHDV+f7EkGccSsDGXSC5tq0J8jRlaUwfK2x re4NgQ2IbqbilvYywOTKBSM0QUeSFnpjisNR8dU8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-yk0-f181.google.com MIME-Version: 1.0 X-Received: by 10.170.135.216 with SMTP id b207mr11415522ykc.109.1416037139832; Fri, 14 Nov 2014 23:38:59 -0800 (PST) Date: Sat, 15 Nov 2014 08:38:59 +0100 Message-ID: Subject: Ruby issue: Installed gems are not in path From: Tallak Tveide To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 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 $ 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