From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3073 invoked by alias); 5 Sep 2012 20:18:23 -0000 Received: (qmail 3060 invoked by uid 22791); 5 Sep 2012 20:18:20 -0000 X-SWARE-Spam-Status: No, hits=-5.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-vc0-f169.google.com (HELO mail-vc0-f169.google.com) (209.85.220.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 05 Sep 2012 20:18:04 +0000 Received: by vcbfl13 with SMTP id fl13so1627413vcb.0 for ; Wed, 05 Sep 2012 13:18:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.204.197 with SMTP id fn5mr3700829vcb.71.1346876283889; Wed, 05 Sep 2012 13:18:03 -0700 (PDT) Received: by 10.220.212.143 with HTTP; Wed, 5 Sep 2012 13:18:03 -0700 (PDT) In-Reply-To: <514883D0F12DEF4788558064C95ECAA332B29C26EE@BE-EXCHANGE-09.swift.corp> References: <2B3152C6-06A1-46FF-9A3F-444A16935920@hp.com> <514883D0F12DEF4788558064C95ECAA332B29C26EA@BE-EXCHANGE-09.swift.corp> <5047A754.7020809@redhat.com> <514883D0F12DEF4788558064C95ECAA332B29C26EE@BE-EXCHANGE-09.swift.corp> Date: Wed, 05 Sep 2012 20:18:00 -0000 Message-ID: Subject: Re: cannot build on RHEL 6 From: Carl Lowenstein To: RAYAPROL Raja Cc: Keith Seitz , "insight@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2012-q3/txt/msg00010.txt.bz2 On Wed, Sep 5, 2012 at 12:43 PM, RAYAPROL Raja 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