From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28990 invoked by alias); 6 Dec 2003 17:39:38 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 28982 invoked from network); 6 Dec 2003 17:39:38 -0000 Received: from unknown (HELO garm.central.cmich.local) (141.209.15.48) by sources.redhat.com with SMTP; 6 Dec 2003 17:39:38 -0000 Received: from leon.phy.cmich.edu ([141.209.165.20]) by egate1.central.cmich.local with Microsoft SMTPSVC(5.0.2195.6713); Sat, 6 Dec 2003 12:39:27 -0500 Received: from localhost (unknown [127.0.0.1]) by leon.phy.cmich.edu (Postfix) with ESMTP id 715527001F; Sat, 6 Dec 2003 12:39:21 -0500 (EST) Date: Sun, 07 Dec 2003 00:16:00 -0000 From: Eric McDonald To: Tom Low-Shang Cc: Xconq list Subject: Re: Cannot build Xconq on Debian Linux In-Reply-To: <20031206162443.GA25918@low-shang.homelinux.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 06 Dec 2003 17:39:27.0878 (UTC) FILETIME=[E59CEA60:01C3BC1F] X-SW-Source: 2003/txt/msg00980.txt.bz2 Hi Tom, Lincoln, I just checked in some changes which might address your Tcl/Tk configuration hassles. Please let me know how they work. On Sat, 6 Dec 2003, Tom Low-Shang wrote: > On Fri, Dec 05, 2003 at 09:35:58PM -0800, Lincoln Peters wrote: > > > > On Debian unstable, the files tclConfig.sh and tkConfig.sh in > > /usr/lib/tcl8.2 and /usr/lib/tk8.2 respectively. Right. And the configuration logic correctly finds those. What it does (or doesn't do, to put it more accurately) with the contents of these is/was the problem. > Since I have used tcl/tk 8.2, 8.3 and 8.4 on debian unstable, > here is what worked for me. With 8.2 I always used: > > make CFLAGS=-I/usr/include/8.2 Do you mean "-I/usr/include/tcl8.2"? I hope so. Otherwise things just got even more convoluted. > 8.3 had similar requirements. Since 8.4, the arguments are no > longer needed. Whether this is due to changes in > tclConfig.sh/tkConfig.sh or the configure script, I cannot say. Well if your 8.4 tclConfig.sh/tkConfig.sh files contain 'TCL_INC_DIR' and 'TK_INC_DIR', repsectively, then this was handled by an enhancement to the configure system. If tclConfig.sh contains a 'TCL_INCLUDE_SPEC' var, then Debian finally decided to do something more mainstream.... Thanks, Eric