Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 16 Jun 2004 17:11:15 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
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> <Pine DOT GSO DOT 4 DOT 58 DOT 0406161502280 DOT 424 AT slinky DOT cs DOT nyu DOT edu> <20040616204657 DOT GA32378 AT coe DOT casa DOT cgf DOT cx> <Pine DOT CYG DOT 4 DOT 58 DOT 0406161557430 DOT 3804 AT fordpc DOT vss DOT fsi DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.CYG.4.58.0406161557430.3804@fordpc.vss.fsi.com>
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/