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 16:06:13 -0500 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: tcltk-20030901-1 packaging bug? In-Reply-To: <20040616204657.GA32378@coe.casa.cgf.cx> Message-ID: 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 X-IsSubscribed: yes 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? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/