From: Jason Molenda <jsm@cygnus.com>
To: Moses DeJong <dejong@cs.umn.edu>
Cc: insight@sourceware.cygnus.com
Subject: Re: configure problem with insight.
Date: Wed, 11 Aug 1999 11:59:00 -0000 [thread overview]
Message-ID: <19990811115922.A9013@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.05.9908111328490.23318-100000@brin.cs.umn.edu>
On Wed, Aug 11, 1999 at 01:34:13PM -0500, Moses DeJong wrote:
> I tried to configure insight in a a build directory and the configure
> script bombed out on me.
> mkdir build52 ; cd build52
> ../configure --prefix=$HOME/project/insight52
As Jim wrote, this is the best way to configure and build Insight--with
the sources in one directory and the build tree in another. You don't
change anything in the srcdir this way, and so it's easy to wipe the
slate clean and get back to a known state.
> configuring in gdbserver
> running /bin/sh /home/mo/project/insight-19990809/gdb/../configure
[...]
> *** Cannot configure here in
> "/home/mo/project/insight-19990809/build52/gdb/gdbserver" when
> "../../../gdb/gdbserver" is currently configured.
The problem is that you ran a configure in your source tree at some
time in the past, and some remnants of this configure were left behind
in the insight-19990809/gdb/gdbserver directory.
You've got a few options. You could just remove the source directory
altogether and untar the snapshot tarball again--that's the easiest.
You could cd into the insight-19990809/gdb/gdbserver directory and, if
there is a Makefile present, try doing a 'make distclean'. If there
isn't a Makefile, you could try removing the config.status file in
that directory.
Hope that helps,
Jason
next prev parent reply other threads:[~1999-08-11 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-11 11:34 Moses DeJong
1999-08-11 11:51 ` James Ingham
1999-08-11 11:59 ` Jason Molenda [this message]
1999-08-11 12:49 ` Moses DeJong
1999-08-11 14:10 ` Moses DeJong
1999-08-11 16:21 ` Moses DeJong
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=19990811115922.A9013@cygnus.com \
--to=jsm@cygnus.com \
--cc=dejong@cs.umn.edu \
--cc=insight@sourceware.cygnus.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).