From: Keith Seitz <keiths@redhat.com>
To: Kevin Powell <KPowell@sirf.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: RE: Building Insight snapshot on CygWin?
Date: Mon, 23 Jun 2003 23:31:00 -0000 [thread overview]
Message-ID: <1056411606.1574.82.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <C2190B0C813D9E49BBAA0293F900204301C8B22C@sjexchange.sirf.com>
On Mon, 2003-06-23 at 16:15, Kevin Powell wrote:
> configure: error: source directory already configured; run make distclean
> there first
> configure: error:
> /usr/src/insight+dejagnu-20030520/dejagnu/example/calc/configure failed for
> example/calc
> make: *** [configure-dejagnu] Error 1
>
> re-running make seemed to make this go away.
Sigh. I was under the impression that someone had fixed this.
> make[6]: Entering directory `/usr/src/insight/insight/dejagnu/testsuite/libdejagnu'
> c++ -DPACKAGE=\"dejagnu\" -DVERSION=\"1.4.2\" -I. -I../../../../insight+dejagnu-20030621/dejagnu/testsuite/libdejagnu -g -O2 -c ../../../../insight+dejagnu-20030621/dejagnu/testsuite/libdejagnu/unit.cc
> /usr/include/c++/3.2/streambuf: In function `int main(int, char**)':
> /usr/include/c++/3.2/streambuf:416: `std::basic_streambuf<_CharT, _Traits>*
> std::basic_streambuf<_CharT, _Traits>::setbuf(_CharT*, int) [with _CharT =
> char, _Traits = std::char_traits<char>]' is protected
> ../../../../insight+dejagnu-20030621/dejagnu/testsuite/libdejagnu/unit.cc:56: within
> this context
> make[6]: *** [unit.o] Error 1
Of course, this has nothing to do with insight. I would harrass the
dejagnu maintainer about the problems. :-)
> Here's the stackdump:
[snip]
Make sure that you don't build Insight with optimization and run it
under gdb. When the error occurs, gdb will stop the process immediately.
You should have a valid, readable stack backtrace (unless it was
corrupted, of course). Use the distributed gdb to run the "bad" one.
BTW, can you describe what you're doing to crash it? (aka: test case).
Although I have not extensively tested on cygwin in a while, I do some
basic sanity checking, debugging insight with insight.
> I guess that to build my own, I need whatever makes the standard GDB into a cygwin-special gdb.
There is no difference of which I am aware. I think it's just
nomenclature.
I guess I'm just lucky? I still cannot reproduce any of these cygwin
errors (the Win98 and dejagnu problems excepted). Argh. I think this is
at least as frustrating for me as it is for everyone else. :v(
Keith
PS. If you're using CVS snapshots/CVS HEAD: make sure you get my patch
to src/Makefile.in. There was a small configury error which I never saw
because I had installed versions of insight (and tcl, tk, itcl, etc)
available. When configuring the gdb directory, make sure that "looking
for private itcl headers"-like stuff comes from the src directory and
not some random package on the system.
next prev parent reply other threads:[~2003-06-23 23:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 23:18 Kevin Powell
2003-06-23 23:31 ` Keith Seitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-07 19:44 John Lowen
2003-07-07 19:57 ` Keith Seitz
2003-06-24 1:46 Kevin Powell
2003-06-24 2:00 ` Keith Seitz
2003-06-24 0:14 Kevin Powell
2003-06-24 1:09 ` Keith Seitz
2003-06-09 15:53 Schumacher, Gordon
2003-06-09 17:53 ` Keith Seitz
2003-06-09 9:28 vadraj kulkarni
2003-06-11 20:11 ` Keith Seitz
2003-06-03 20:02 Schumacher, Gordon
2003-06-06 20:45 ` Keith Seitz
2003-05-21 20:47 Schumacher, Gordon
2003-05-27 18:30 ` Keith Seitz
2003-05-21 17:18 Schumacher, Gordon
2003-05-21 17:19 ` Keith Seitz
2003-05-21 18:55 ` Keith Seitz
2003-05-21 19:02 ` Martin M. Hunt
2003-05-21 21:37 ` Keith Seitz
2003-05-21 23:08 ` Keith Seitz
2003-05-21 23:49 ` Andrew Cagney
2003-05-21 16:54 Schumacher, Gordon
2003-05-21 17:02 ` Keith Seitz
2003-05-21 19:58 ` Martin M. Hunt
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=1056411606.1574.82.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=KPowell@sirf.com \
--cc=insight@sources.redhat.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).