From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14281 invoked by alias); 30 Apr 2007 20:12:45 -0000 Received: (qmail 14266 invoked by uid 22791); 30 Apr 2007 20:12:44 -0000 X-Spam-Check-By: sourceware.org Received: from mail.artimi.com (HELO mail.artimi.com) (194.72.81.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 30 Apr 2007 21:12:43 +0100 Received: from rainbow ([192.168.8.46]) by mail.artimi.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Apr 2007 21:11:56 +0100 From: "Dave Korn" To: "'Fahd Abidi'" , References: <071DB0C788671B48940BC79F8B4930691181F6@ultsol01.tewks.ultsol.local> Subject: RE: trying to build gdb with renamed cygwin1.dll Date: Mon, 30 Apr 2007 20:12:00 -0000 Message-ID: <046901c78b63$cd990810$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <071DB0C788671B48940BC79F8B4930691181F6@ultsol01.tewks.ultsol.local> 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/msg00178.txt.bz2 On 30 April 2007 17:42, Fahd Abidi wrote: > Actually I am planning on eventually building a cross debugger for > arm/ppc/mips/xscale. But that will be afterwards. Right now I am just > trying to get the gdb binary to be stand alone. Actually I had allot of > success with building with the --disable-shared and --enable-static > option and was able to move the resulting gdb across different versions > of cygwin1.dll without it complain about using an incompatible version > of cygwin1.dll. You're putting an awful lot of effort into a mostly-imaginary problem. Cygwin1.dll attempts to remain backwardly-compatible. The last ABI break I was remember was something to do with the __reent_impure pointer and it happened sometime back around 1.5.3 IIRC. The one thing you can't do is carry around a copy of the cygwin dll that you compiled against, and put gdb and that dll onto a system that already has a different version of the dll installed; they will clash. But you shouldn't need to do that anyway; if there's an exisiting cygwin install, you just need to copy gdb.exe across. Apart from the occasional break, as I mentioned above, /most/ versions of gdb compiled agsinst /most/ versions of the dll should work fine against /most/ other versions of the dll. This is pretty much regardless of --disable-shared and --enable-static, although if you compiled gdb against a very old or very new cygwin and the one you're running it on doesn't have some of the same versions of the support dlls you might find it's missing something, e.g. cygintl-1 vs. cygintl-2. However, there's no compatibility problems between the differently-numbered versions of the support dlls, so you should be able to carry a set of those around and just leave out cygwin1.dll and get what you want. Give it a try if you haven't yet. If you have, plese post the /exact/ error message, so we can be clear precisely what situation you're talking about. cheers, DaveK -- Can't think of a witty .sigline today....