From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31394 invoked by alias); 14 Jan 2003 20:20:55 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 31348 invoked from network); 14 Jan 2003 20:20:54 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 209.249.29.67 with SMTP; 14 Jan 2003 20:20:54 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18YZQy-0000sZ-00 for ; Tue, 14 Jan 2003 16:21:24 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18YXYk-0008Or-00 for ; Tue, 14 Jan 2003 15:21:18 -0500 Date: Tue, 14 Jan 2003 20:20:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: problem with building head branch gdb Message-ID: <20030114202117.GA32261@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <002c01c2bc05$57340300$0202040a@catdog> <20030114200152.GA31810@nevyn.them.org> <003a01c2bc09$d06fca70$0202040a@catdog> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003a01c2bc09$d06fca70$0202040a@catdog> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-01/txt/msg00234.txt.bz2 On Tue, Jan 14, 2003 at 03:16:25PM -0500, Kris Warkentin wrote: > > 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 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. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer