Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 16 Jun 2004 17:11:15 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: tcltk-20030901-1 packaging bug? Message-ID: <20040616211115.GA10048@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040616185925 DOT 60096 DOT qmail AT web60301 DOT mail DOT yahoo DOT com> <20040616204657 DOT GA32378 AT coe DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Wed, Jun 16, 2004 at 04:06:13PM -0500, Brian Ford wrote: >On Wed, 16 Jun 2004, Christopher Faylor wrote: >>Why would configure care where I built tcl? It sounds like a broken >>configure script to me. > >It doesn't care where you build tcl, but how/where you configured to >install. I'm sorry. I wasn't really asking for an explanation. I know what tclConfig.sh is supposed to be used for. Did you actually look at tclConfig.sh? # String to pass to linker to pick up the Tcl library from its # build directory. TCL_BUILD_LIB_SPEC='-L/netrel/build/libtcltk/tcl/win -ltcl84' Unless you have my build structure on your system it doesn't make much sense to use this variable. The TCL_INCLUDE_SPEC (and maybe TCL_LIB_SPEC) is obviously wrong however. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/