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: <3E502A5B.7060408@ece.gatech.edu>
Date: Sun, 16 Feb 2003 19:18:35 -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
CC: Max Bowsher <maxb AT ukf DOT net>, 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> <3E488E18 DOT 1060100 AT ece DOT gatech DOT edu>
In-Reply-To: <3E488E18.1060100@ece.gatech.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Charles Wilson wrote:

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

Your larger point is still subject for a (different) discussion, but one 
small issue: a *very* recent patch to libtool CVS allows passing 
arguments to gcc.  so, CC='gcc -mno-cygwin -L/usr/lib/w32api' is okay 
now.  [there was an earlier patch that specifically allowed -mXXXXX 
options; the newer one lets anything go]

However, I tend to just add -L/usr/lib/w32api directly to my spec file 
anyway (although a cross compiler would be subtly different, I know).

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