From: Keith Seitz <keiths@cygnus.com>
To: <peter.betts@hmse.com>
Cc: <insight@sources.redhat.com>
Subject: Re: Building Insight on Cygwin (bad interpreter)
Date: Wed, 26 Sep 2001 10:51:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0109261048220.14843-100000@makita.cygnus.com> (raw)
In-Reply-To: <3BB04E1D.5E068E9E@hmse.com>
Sorry for the delay... I've been out of town (yes, I actually took an
airplane), and I'm just getting up to speed again.
On Tue, 25 Sep 2001 peter.betts@hmse.com wrote:
> I have insight-5_0.tar.gz un-tarred within Cygwin using "tar zxvf
> insight-5_0_tar.gz" to insight-5.0 and am now ready to install.
Please try checking out the 5.1 branch and building it. Believe me when I
say you'll be much, much happier that you did.
> "It is now possible to automatically configure and build a variety of
> tools with one command. To build all of the tools contained herein,
> run the ``configure'' script here, e.g.:
>
> ./configure
> make
> "
>
> but I get the following 'bad interpreter" error whenever I try to run
> configure, config.sub or any such install proceedures.
I don't know where the above quote comes from, and it may work, but I
never do it that way. I _always_ build in a separate directory. This keeps
the source directories unaltered, which allows me to build multiple
Insights/gdbs for different targets/hosts.
> $ ./configure
> bash: ./configure: bad interpreter: No such file or directory
What does "ls -l /bin/sh" show?
Keith
next prev parent reply other threads:[~2001-09-26 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 2:27 peter.betts
2001-09-26 10:51 ` Keith Seitz [this message]
2001-09-26 11:20 ` Andrew Cagney
2001-09-26 12:01 ` Keith Seitz
2001-09-27 0:17 ` peter.betts
2001-09-27 7:15 ` Keith Seitz
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=Pine.GSO.4.33.0109261048220.14843-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sources.redhat.com \
--cc=peter.betts@hmse.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).