From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Molenda To: Moses DeJong Cc: insight@sourceware.cygnus.com Subject: Re: configure problem with insight. Date: Wed, 11 Aug 1999 11:59:00 -0000 Message-id: <19990811115922.A9013@cygnus.com> References: X-SW-Source: 1999-q3/msg00042.html 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