From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>, <gdb@sources.redhat.com>
Subject: Re: problem with building head branch gdb
Date: Tue, 14 Jan 2003 20:27:00 -0000 [thread overview]
Message-ID: <005501c2bc0b$58233640$0202040a@catdog> (raw)
In-Reply-To: <20030114202117.GA32261@nevyn.them.org>
> Try --disable-gdbtk. You probably updated using cvs up -dP, which got
> you the gdb/gdbtk/ directory that's ordinarily missing in the GDB CVS
> module; that's how I usually hit this problem.
That one did the trick. I don't, however, have the gdbtk directory checked
out. I'm thinking it might be an error in configure because I only checked
out gdb. Michael C suggested checking out gdb+dejagnu which is probably
what most people do which might explain why no-one had seen it yet.
Thanks,
Kris
next prev parent reply other threads:[~2003-01-14 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 19:44 Kris Warkentin
2003-01-14 20:01 ` Daniel Jacobowitz
2003-01-14 20:16 ` Kris Warkentin
2003-01-14 20:20 ` Daniel Jacobowitz
2003-01-14 20:27 ` Kris Warkentin [this message]
2003-01-14 20:13 Michael Elizabeth Chastain
2003-01-14 20:26 ` Kris Warkentin
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='005501c2bc0b$58233640$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=drow@mvista.com \
--cc=gdb@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