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: <02ee01c2d13f$506fbc40$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>,
   "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc: <cygwin AT cygwin DOT com>
References: <000001c2d13b$d5c30a40$5c1306d5 AT BRAMSCHE>
Subject: Re: [avail for test] libtool-devel-20030121-1
Date: Mon, 10 Feb 2003 20:02:17 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

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

Ralf Habacker wrote:
> May be, but like Max has stated, I don't like to be forced to make
> every static lib as shared lib. This would break the whole kde build
> system, because often convenience librarys are build and assembled
> together into a dll. May be, that's the reason, why on linux and
> other systems "pass_all" is used, because it overrides this police.

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.



Max.


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