Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: ghazel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: "Rainbows! list" <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Subject: Re: /this/will/be/overwritten/or/wrapped/anyways/do/not/worry/ruby
Date: Mon, 13 Dec 2010 10:28:09 -0800	[thread overview]
Message-ID: <AANLkTin7ABGGRuRp9mtW8f3VCY=77zpqpBmvJJ78MeKY@mail.gmail.com> (raw)
In-Reply-To: <81A07824-4000-4E2B-A353-19C6986F526A-wWwMKTv0ClVAfugRpC6u6w@public.gmane.org>

On Mon, Dec 13, 2010 at 2:52 AM, russell muetzelfeldt
<russm-rubyforge-wWwMKTv0ClVAfugRpC6u6w@public.gmane.org> wrote:
> On 13/12/2010, at 8:04 PM, ghazel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
>
>> I installed the rainbows gem and symlinked rainbows-2.0.1/bin/rainbows
>> to /usr/local/bin/rainbows
>> However, running rainbows gives: -bash: /usr/local/bin/rainbows:
>> /this/will/be/overwritten/or/wrapped/anyways/do/not/worry/ruby: bad
>> interpreter: No such file or directory
>>
>> Any ideas what I should have done instead?
>
> what platform are you on? you shouldn't have to link gem executable scripts anywhere for them to work.
>
> when I install gems, the system creates a wrapper executable in an existing bin/ directory (/usr/bin/ on OSX, /var/lib/gems/1.9.1/bin/ on Debian Squeeze) that lets you force a version for the loaded gem and then loads the original executable script without launching a new interpreter - this ignores the supposed #! line in the gem's internal bin/rainbows, which is why that file says its #! will be overwritten or wrapped.
>
> If installing rainbows didn't leave an executable script somewhere in your $PATH you might need to find where your local gem package is putting the wrappers and add that to your search path.

Ah! For me it's /usr/local/ruby-enterprise-1.8.7-2010.01/bin

That makes much more sense. Thanks!

-Greg
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


      parent reply	other threads:[~2010-12-13 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13  9:04 /this/will/be/overwritten/or/wrapped/anyways/do/not/worry/ruby ghazel-Re5JQEeQqe8AvxtiuMwx3w
     [not found] ` <AANLkTikfzyTV4Ymbk2vPHfq2VwYpM9f3mZuL0ep_eZ-O-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-13 10:34   ` /this/will/be/overwritten/or/wrapped/anyways/do/not/worry/ruby Eric Wong
2010-12-13 10:52   ` /this/will/be/overwritten/or/wrapped/anyways/do/not/worry/ruby russell muetzelfeldt
     [not found]     ` <81A07824-4000-4E2B-A353-19C6986F526A-wWwMKTv0ClVAfugRpC6u6w@public.gmane.org>
2010-12-13 18:28       ` ghazel-Re5JQEeQqe8AvxtiuMwx3w [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-all from there: mbox

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

  List information: https://yhbt.net/rainbows/

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

  git send-email \
    --in-reply-to='AANLkTin7ABGGRuRp9mtW8f3VCY=77zpqpBmvJJ78MeKY@mail.gmail.com' \
    --to=ghazel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.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.
Code repositories for project(s) associated with this inbox:

	../../rainbows.git

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).