Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Mon, 21 Jan 2002 22:53:27 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: gcc v3 issue -- hacky solution Message-ID: <20020122035327.GA24224@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20020122032839 DOT GA23746 AT redhat DOT com> <08d401c1a2f4$d2d66370$0200a8c0 AT lifelesswks> <20020122034231 DOT GA23893 AT redhat DOT com> <08e601c1a2f7$35b39d30$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <08e601c1a2f7$35b39d30$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Tue, Jan 22, 2002 at 02:45:17PM +1100, Robert Collins wrote: >Or maybe Danny Smith can provide details on what it takes to build said >library, and one of the folk that keep building gcc for-the-hell-of-it >and talking on cygwin@ can become the maintainer? It's easy enough to build the library for mingw. There's no trick there. The trick is typing '/whatever/configure; make' at the top of a build directory; where the source tree contains gdb, binutils, gcc, cygwin, etc, and ensuring that both a cygwin and a mingw version of the library are generated so that both i686-pc-cygwin/winsup/cinstall/setup.exe and i686-pc-cygwin/utils/mount.exe link correctly. cgf