Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <3E488E18.1060100@ece.gatech.edu>
Date: Tue, 11 Feb 2003 00:46:00 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Max Bowsher <maxb AT ukf DOT net>
CC: Ralf Habacker <Ralf DOT Habacker AT freenet DOT de>, cygwin AT cygwin DOT com
Subject: Re: [avail for test] libtool-devel-20030121-1
References: <000001c2d13b$d5c30a40$5c1306d5 AT BRAMSCHE> <02ee01c2d13f$506fbc40$78d96f83 AT pomello>
In-Reply-To: <02ee01c2d13f$506fbc40$78d96f83@pomello>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Max Bowsher wrote:
>>>ARGH.  This defeats the whole purpose of the policy change -- and it
>>>is a policy change driven by the libtool development
> 
> 
> I've been hunting for the relevant threads on the libtool list - can't find
> them. Can anyone offer URLs or search terms that would help?

I think it was actually described in the code/comments/changelogs/NEWS 
or somesuch.  But if you're really curious, ask on the libtool list. 
I'm sure one of the PowersThatBe will clue us all in.

> I think that in some cases, libtool tries to do too much. I've run into a
> number of cases which would have just worked if libtool had passed the
> arguments to gcc without modification, but it insists on filtering stuff in
> complex ways. For example, gcc -print-search-dirs doesn't admit to searching
> /usr/lib/w32api, so any attempt to link with a w32api library when
> cross-compiling with -mno-cygwin (which means the Cygwin-specific hack in
> libtool.m4 doesn't get activated) fails. Now, admittedly, gcc is probably
> wrong in not showing all its search dirs correctly, but sometimes I wish
> libtool trusted the compiler more.

mebbe. But that's another discussion.

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/