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:16:00 -0000 [thread overview]
Message-ID: <003a01c2bc09$d06fca70$0202040a@catdog> (raw)
In-Reply-To: <20030114200152.GA31810@nevyn.them.org>
> On Tue, Jan 14, 2003 at 02:44:24PM -0500, Kris Warkentin wrote:
> > When trying to build the head branch of gdb on Cygwin I keep getting
this
> > error in the gdb subdir:
> >
> > checking for Tcl private headers. dir=unix... checking for tclInt.h...
no
> > configure: error: Can't find Tcl private headers
> > make: *** [configure-gdb] Error 1
> >
> > Obviously it wants tcl/tk but the question is, is there any configure
option
> > to make it NOT want tcl/tk? If not, then shouldn't the gdb module in
cvs be
> > updated to include the tcl/tk subdirs?
>
> What directory is configuring when you get this?
>
gdb
next prev parent reply other threads:[~2003-01-14 20:16 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 [this message]
2003-01-14 20:20 ` Daniel Jacobowitz
2003-01-14 20:27 ` Kris Warkentin
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='003a01c2bc09$d06fca70$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