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 Message-ID: <001f01c2d79c$9d26f040$78d96f83@pomello> From: "Max Bowsher" To: "Robert Collins" Cc: References: <3E519478.6050108@ece.gatech.edu> <007f01c2d797$5fb5d1e0$78d96f83@pomello> <1045605153.1099.49.camel@localhost> Subject: Re: [avail for test] libtool-devel-20030216-1 Date: Tue, 18 Feb 2003 22:25:17 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Robert Collins wrote: > On Wed, 2003-02-19 at 08:47, Max Bowsher wrote: > > >> 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, if you have time, could you build a 'release' setup + included > libs (libgetopt + gzip + bzip2) with the new libtool? I'd really > appreciate > that. Yep, works fine. 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/