From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3330 invoked by alias); 21 Feb 2002 09:51:24 -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 3248 invoked from network); 21 Feb 2002 09:51:23 -0000 Received: from unknown (HELO shell4.bayarea.net) (209.128.82.1) by sources.redhat.com with SMTP; 21 Feb 2002 09:51:23 -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 BAA08674 for ; Thu, 21 Feb 2002 01:51:22 -0800 (envelope-from supermo@bayarea.net) Date: Thu, 21 Feb 2002 11:00:00 -0000 From: Mo DeJong To: sourcenav Subject: Re: Fixing build bustage under VC++ Message-Id: <20020221015013.3081808e.supermo@bayarea.net> In-Reply-To: <3C74BC7E.DE723733@redhat.com> References: <20020220175911.48e153f5.supermo@bayarea.net> <3C74865C.3F1EB59A@redhat.com> <20020220231348.4c9bb314.supermo@bayarea.net> <3C74BC7E.DE723733@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/msg00094.txt.bz2 On Thu, 21 Feb 2002 01:23:10 -0800 Ian Roxborough wrote: ... > > I was under the impression that the tcl/cygwin directory was where > > this "pure Cygwin" layer was going to live. ... > Well, the apps being built think they are being built under UNIX > and look in the ../unix location. > > A more correct solution would be to create a ../cygwin/tclConfig.sh > and make all the apps currently using the ../unix/tclConfig.sh > cygwin aware so they know to look in the ../cygwin directory. Well, that should be a simple matter of adding some code to the CYG_AC_PATH_TCLCONFIG macro defined in src/config/acinclude.m4. Expect uses this macro so it should be a simple matter of updating the m4 file and running autoconf in the expect dir. A tcl/cygwin/tclConfig.sh already exists so that should not be a problem. > What are your feelings on VC++ vs gcc for building SN? > > I'm left with the distinct impression building gcc > would be easier, but then again, I'm just talk about > compiling, I've yet to get it to run. I think we should shoot for getting the VC++ build working again before working on further gcc support under Windows. The main point of a SN 5.1 release is to get the bug fixes and Tcl/Tk 8.3 upgrade out to folks. I don't think that switching the release compiler at the same time is such a good idea. Last I remember, the VC++ build was working and SN was running (but, that was many moons ago). I seem to remember that I had 90% of the packages compiling with mingw, but there were a couple (perhaps Tix, db, or grep) that were not yet ported. I know that at least Tcl, Tk, Incr Tcl, and Incr Tk compiled with gcc. cheers Mo