From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15194 invoked by alias); 30 Apr 2007 15:38:32 -0000 Received: (qmail 15181 invoked by uid 22791); 30 Apr 2007 15:38:31 -0000 X-Spam-Check-By: sourceware.org Received: from vms044pub.verizon.net (HELO vms044pub.verizon.net) (206.46.252.44) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 30 Apr 2007 16:38:29 +0100 Received: from ultsol.com ([72.74.243.178]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JHB00LMQI3ZE2E8@vms044.mailsrvcs.net> for gdb@sourceware.org; Mon, 30 Apr 2007 10:38:23 -0500 (CDT) Date: Mon, 30 Apr 2007 15:38:00 -0000 From: "Fahd Abidi" Subject: RE: trying to build gdb with renamed cygwin1.dll To: "Andrew STUBBS" Cc: Message-id: <071DB0C788671B48940BC79F8B4930691181F5@ultsol01.tewks.ultsol.local> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Content-class: urn:content-classes:message X-Ninja-PIM: Scanned by Ninja X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-04/txt/msg00171.txt.bz2 I tried the -mno-cygwin option but got several compile errors. I didn't want to debug the sources because of time constraints. That is why I thought that compiling against a renamed cygwin1.dll might be an eaisier solution. Fahd =20 -----Original Message----- From: Andrew STUBBS [mailto:andrew.stubbs@st.com]=20 Sent: Monday, April 30, 2007 11:30 AM To: Fahd Abidi Cc: gdb@sourceware.org Subject: Re: trying to build gdb with renamed cygwin1.dll Fahd Abidi wrote: > My purpose is to try and build a gdb that so I can move it across=20 > different windows platforms with out worrying about newer or older=20 > versions of the cygwin dll interfering. I already looked at the MinGW=20 > option but the newer versions of gdb do not build against mingw32. I don't know about the exact solution you had in mind, but .... You might want to investigate the -mno-cygwin GCC option. This builds "MinGW" binaries (Minimum GNU for Windows) which do not depend upon anything not present in a standard Windows installation. This is how our Windows tools are built. Obviously there are issues with doing it this way - no automatic support for Cygwin pathnames being the biggest - but most of these can be overcome with little effort, and all overcome with more effort. Andrew