From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16208 invoked by alias); 21 Feb 2002 07:14:53 -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 16133 invoked from network); 21 Feb 2002 07:14:49 -0000 Received: from unknown (HELO shell4.bayarea.net) (209.128.82.1) by sources.redhat.com with SMTP; 21 Feb 2002 07:14:49 -0000 Received: from modrick (209-128-79-218.BAYAREA.NET [209.128.79.218]) by shell4.bayarea.net (8.9.3/8.9.3) with SMTP id XAA17255 for ; Wed, 20 Feb 2002 23:14:48 -0800 (envelope-from supermo@bayarea.net) Date: Thu, 21 Feb 2002 00:08:00 -0000 From: Mo DeJong To: sourcenav Subject: Re: Fixing build bustage under VC++ Message-Id: <20020220231348.4c9bb314.supermo@bayarea.net> In-Reply-To: <3C74865C.3F1EB59A@redhat.com> References: <20020220175911.48e153f5.supermo@bayarea.net> <3C74865C.3F1EB59A@redhat.com> Organization: House of Mirth X-Mailer: Sylpheed version 0.4.99cvs6 (GTK+ 1.2.7; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2002-q1/txt/msg00091.txt.bz2 On Wed, 20 Feb 2002 21:32:12 -0800 Ian Roxborough wrote: ... > > -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? ... > 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.... What does that have to do with the win/ subdir and the VC++ build? I was under the impression that the tcl/cygwin directory was where this "pure Cygwin" layer was going to live. I took a peek and it appears there is a tclConfig.sh.in file in there too, so why would you want to also create one in the ../unix directory? I think it is just plain wrong to create a ../unix/tclConfig.sh file from the win subdirectory. For one thing, the @VAR@ variable names are not always the same. Also, it breaks the macros that load tclConfig.sh. There must be some other way to solve the problem, it is just that I don't understand what the problem was. Mo