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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 10 Jan 2002 20:58:38 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Compiling apps to Mingw32 with cygwin Message-ID: <20020111015838.GA2631@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <05ea01c19a42$907377d0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <05ea01c19a42$907377d0$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Fri, Jan 11, 2002 at 12:52:01PM +1100, Robert Collins wrote: >----- Original Message ----- >From: "Jon Leichter" > >>AC_CHECK_TOOL checks for tools with a ${host} prefix. AC_CHECK_PROG >>does not. >> >>In my opinion, this serves as another example that one cannot count on >>a configure script being up-to-date. > >Ouchies. I agree - yet another reason for cygwin ports to be updated >by the maintainer :}. If I am reading this correctly, this is not really a cygwin issue. It's a cross-build issue, right? I build all of the stuff that I support on linux. For most packages, I have to do a lot of extra stuff (like set CC, LD, AR, RANLIB on the command line) to get things built. cgf -- 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/