public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Carl Lowenstein <carl.lowenstein@gmail.com>
To: RAYAPROL Raja <Raja.RAYAPROL@swift.com>
Cc: Keith Seitz <keiths@redhat.com>,
	"insight@sourceware.org" <insight@sourceware.org>
Subject: Re: cannot build on RHEL 6
Date: Wed, 05 Sep 2012 20:18:00 -0000	[thread overview]
Message-ID: <CAOgEH+N4e=KiiQhdOMOX-RGv=dUWSHHexw02oGDzJ83zVERB6w@mail.gmail.com> (raw)
In-Reply-To: <514883D0F12DEF4788558064C95ECAA332B29C26EE@BE-EXCHANGE-09.swift.corp>

On Wed, Sep 5, 2012 at 12:43 PM, RAYAPROL Raja <Raja.RAYAPROL@swift.com> wrote:
> Keith,
>
> If I go to the source file directory (/tmp/insight-6.8) and issue
> ./configure, all I get is
>
> -bash: ./configure /bin/sh^M: bad interpreter: No such file or directory
>

Your source file (/.configure) must have originated from a
Windows-type system, which uses control-M (^M) as part of the line
terminator.  So when the script is interpreted by bash, it tries to
find a file named "/bin/sh^M" which doesn't exist.

Google search for "bad interpreter" will give you plenty of advice
about how to cure this problem.

    carl
-- 
    carl lowenstein         marine physical lab     u.c. san diego
                                                 clowenstein@ucsd.edu

  reply	other threads:[~2012-09-05 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2B3152C6-06A1-46FF-9A3F-444A16935920@hp.com>
2012-09-05 19:15 ` RAYAPROL Raja
2012-09-05 19:26   ` Keith Seitz
2012-09-05 19:44     ` RAYAPROL Raja
2012-09-05 20:18       ` Carl Lowenstein [this message]
2012-09-05 20:22         ` RAYAPROL Raja
2012-09-05 20:26       ` Keith Seitz
2012-09-06 17:57         ` RAYAPROL Raja
2012-09-06 18:08           ` Keith Seitz
2012-09-07 13:56             ` RAYAPROL Raja

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

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

  git send-email \
    --in-reply-to='CAOgEH+N4e=KiiQhdOMOX-RGv=dUWSHHexw02oGDzJ83zVERB6w@mail.gmail.com' \
    --to=carl.lowenstein@gmail.com \
    --cc=Raja.RAYAPROL@swift.com \
    --cc=insight@sourceware.org \
    --cc=keiths@redhat.com \
    /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.
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).