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 Message-ID: <095701c1a2f9$3ce79190$0200a8c0@lifelesswks> From: "Robert Collins" To: 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> <20020122035327 DOT GA24224 AT redhat DOT com> Subject: Re: gcc v3 issue -- hacky solution Date: Tue, 22 Jan 2002 14:59:48 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 22 Jan 2002 04:01:42.0090 (UTC) FILETIME=[7FFC92A0:01C1A2F9] === ----- Original Message ----- From: "Christopher Faylor" To: Sent: Tuesday, January 22, 2002 2:53 PM Subject: Re: gcc v3 issue -- hacky solution > 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. At the top of the tree, could the following pseudo code be included? if (target=i686-pc-cygwin) also build opcode, binutils, gcc with target=i686-pc-mingw fi ? Rob