From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19243 invoked by alias); 21 Feb 2002 04:17:25 -0000 Mailing-List: contact sourcenav-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sourcenav-owner@sources.redhat.com Received: (qmail 19134 invoked from network); 21 Feb 2002 04:17:17 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 21 Feb 2002 04:17:17 -0000 Received: from redhat.com (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id UAA00923; Wed, 20 Feb 2002 20:17:13 -0800 (PST) Message-ID: <3C74865C.3F1EB59A@redhat.com> Date: Wed, 20 Feb 2002 21:13:00 -0000 From: Ian Roxborough X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: Mo DeJong CC: sourcenav Subject: Re: Fixing build bustage under VC++ References: <20020220175911.48e153f5.supermo@bayarea.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-q1/txt/msg00089.txt.bz2 Mo DeJong wrote: > > Hi all. > > I took a quick look at why sourcenav fails to build under VC++ these days. > The first problem I found showed up when Itcl tried to load tclConfig.sh and > pulled it out of the tcl/unix subdirectory instead of tcl/win. After poking > around for a bit, I found that the following change was to blame for this: > > 2001-09-12 Ian Roxborough > > * win/configure.in: Set DL_LIBS and MATH_LIBS. Create > unix/tclConfig.sh. > > Index: configure.in > =================================================================== > RCS file: /cvs/src/src/tcl/win/configure.in,v > retrieving revision 1.4 > retrieving revision 1.5 > diff -u -r1.4 -r1.5 > --- configure.in 2001/09/09 23:56:10 1.4 > +++ configure.in 2001/09/13 00:38:49 1.5 > @@ -230,5 +235,5 @@ > AC_SUBST(MAKE_DLL) > AC_SUBST(MAKE_EXE) > > -AC_OUTPUT(Makefile tclConfig.sh tcl.hpj) > +AC_OUTPUT(Makefile tclConfig.sh tcl.hpj ../unix/tclConfig.sh) > > My question is, why would the tcl/win configure script need to generate > a tclConfig.sh in the ../unix directory? The ChangeLog message seems to > indicate that it has something to do with getting the build working with > the Cygwin compiler. We can't really have two tclConfig.sh scripts like > this because it breaks the m4 macro that searches for either unix/tclConfig.sh > or win/tclConfig.sh. This is because some apps need a pure cygwin/UNIX version of Tcl to work correctly. It was kind of pain to learn that since I'd already done the upgrade in source.redhat.com and found a dejagnu and friends wouldn't work.... Ian.