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: <007f01c2d797$5fb5d1e0$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>, <cygwin AT cygwin DOT com>
References: <3E519478 DOT 6050108 AT ece DOT gatech DOT edu>
Subject: Re: [avail for test] libtool-devel-20030216-1
Date: Tue, 18 Feb 2003 21:47:46 -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

Charles Wilson wrote:
> I've updated libtool-devel to the 20030216 CVS, plus a rewritten
> win32_libid() function that should speed up linking libraries that
> have many dependencies.
>
> So, test and enjoy; I will probably make this the official cygwin
> libtool-devel very soon.  Unless there are significant bugs reported,
> I do not expect to update our libtool-devel again until libtool-1.5 is
> released, which may be in a month -- or it may be in June.  For now, I
> am happy with the status of libtool-devel (the friendly error message
> is just a simple cosmetic fix; I'm too swamped right now to worry
> about cosmetics; functionality only.)
>
> [IMPORTANT]
> Translation: this will be the basic behavior of official libtool-1.5
> on cygwin.  If you don't like it, now is the time to yell.

I've discovered something which is only a problem when doing a
CC='gcc -mno-cygwin' compile - namely, that the new wrapper executables do
execv("/bin/bash",...), which quite obviously, msvcrt doesn't understand.

Now, I don't think that many people do weird cross-compile tricks, and this
issue probably should not block a new Cygwin release of libtool, but I just
wanted to raise the issue. I can't think of any good solution to it, either.


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/