From: Andrew Cagney <ac131313@cygnus.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: peter.betts@hmse.com, insight@sources.redhat.com
Subject: Re: Building Insight on Cygwin (bad interpreter)
Date: Wed, 26 Sep 2001 11:20:00 -0000 [thread overview]
Message-ID: <3BB21C5A.90809@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0109261048220.14843-100000@makita.cygnus.com>
>> 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.
That exact quote, I don't know. However, building in the source tree is
still documented. On some very obscure platforms, VPATH doesn't work
breaking separate source and build directories.
Andrew
next prev parent reply other threads:[~2001-09-26 11:20 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
2001-09-26 11:20 ` Andrew Cagney [this message]
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=3BB21C5A.90809@cygnus.com \
--to=ac131313@cygnus.com \
--cc=insight@sources.redhat.com \
--cc=keiths@cygnus.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).