Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 7 May 2003 10:11:22 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: SV: Tracing down problem when compiling GCC 3.3 under cygwin PR 10626 Message-ID: <20030507141122.GB26264@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <41D1051F31A2674C99E41CA28EE73498018C63 AT isp-ex2k DOT intellimade DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41D1051F31A2674C99E41CA28EE73498018C63@isp-ex2k.intellimade.net> User-Agent: Mutt/1.4.1i On Wed, May 07, 2003 at 08:46:26AM +0200, ?yvind Harboe wrote: >>AFAICT, install-sh should never be asked to install an executable which >>lacks an .exe when the executable was built with a .exe extension. So, >>the fact that sometimes it "works" is a red herring. > >I don't understand what you mean when you say that it is a "red >herring". Did you read what I WROTE? If you have tracked this down to the fact that install-sh is getting programs which should have .exe extension on its command line THAT IS THE BUG. That is NOT SUPPOSED TO HAPPEN. I don't know how to (re)say it any more clearly than that. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/