Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Wed, 16 Jun 2004 17:27:25 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: tcltk-20030901-1 packaging bug?
In-Reply-To: <Pine.CYG.4.58.0406161557430.3804@fordpc.vss.fsi.com>
Message-ID: <Pine.GSO.4.58.0406161716450.424@slinky.cs.nyu.edu>
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
X-Scanned-By: MIMEDefang 2.39

On Wed, 16 Jun 2004, 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.
>
> Most configure scripts that "test" for packages that have pkgconfig
> style scripts (like tcl's tclConfig.sh) due not actually test anything at
> all.  They just invoke the pkgconfig script to retrieve the correct
> paths, compilation flags, link flags, etc. for the particular
> installation.
>
> tclConfig.sh does not acurately convey those paths for the Cygwin
> installation.  It reports those that would be correct for your netrel
> installation location.
>
> Does that help?

I believe it's actually both a broken configure script and a packaging bug
in tcltk.  The configure script *is* broken, since it uses
TCL_BUILD_LIB_SPEC instead of TCL_LIB_SPEC.

However, the Cygwin /usr/lib/tclConfig script doesn't define TCL_LIB_SPEC
and TCL_LIB_FLAG correctly:

| # -l flag to pass to the linker to pick up the Tcl library
| TCL_LIB_FLAG=''
|
| # String to pass to linker to pick up the Tcl library from its
| # installed directory.
| TCL_LIB_SPEC=''

Whereas the /usr/lib/tclConfig.sh script on a Linux machine does define
them, so that passing those to the linker will pick up the TCL library:

| # -l flag to pass to the linker to pick up the Tcl library
| TCL_LIB_FLAG='-ltcl8.3${TCL_DBGX}'
|
| # String to pass to linker to pick up the Tcl library from its
| # installed directory.
| TCL_LIB_SPEC='-L/usr/lib -ltcl8.3${TCL_DBGX}'

In other words, even after fixing the configure script, the link will
still fail.  I was wrong about the exact nature of the packaging bug
before, but the above looks correct.  BTW, same goes for
/usr/lib/tkConfig.sh.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/