Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: [avail for test] libtool-devel-20030216-1 From: Robert Collins To: Max Bowsher Cc: Charles Wilson , cygwin@cygwin.com In-Reply-To: <007f01c2d797$5fb5d1e0$78d96f83@pomello> References: <3E519478.6050108@ece.gatech.edu> <007f01c2d797$5fb5d1e0$78d96f83@pomello> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-UXa2ewICUC1RM7m7p8mx" Organization: Message-Id: <1045605153.1099.49.camel@localhost> Mime-Version: 1.0 Date: 19 Feb 2003 08:52:33 +1100 --=-UXa2ewICUC1RM7m7p8mx Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2003-02-19 at 08:47, Max Bowsher wrote: > I've discovered something which is only a problem when doing a > CC=3D'gcc -mno-cygwin' compile - namely, that the new wrapper executables= do > execv("/bin/bash",...), which quite obviously, msvcrt doesn't understand. >=20 > Now, I don't think that many people do weird cross-compile tricks, and th= is > issue probably should not block a new Cygwin release of libtool, but I ju= st > wanted to raise the issue. I can't think of any good solution to it, eith= er. Max, if you have time, could you build a 'release' setup + included libs (libgetopt + gzip + bzip2) with the new libtool? I'd really appreciate that. Rob --=20 GPG key available at: . --=-UXa2ewICUC1RM7m7p8mx Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+UqshI5+kQ8LJcoIRAvsKAKCLmyKhM9sNIXnfxPvgi2Kj4EsGagCgq91b doUQA5CE0dbInRpqusKCefY= =Egu4 -----END PGP SIGNATURE----- --=-UXa2ewICUC1RM7m7p8mx--