From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22979 invoked by alias); 30 Apr 2007 15:05:49 -0000 Received: (qmail 22602 invoked by uid 22791); 30 Apr 2007 15:05:47 -0000 X-Spam-Check-By: sourceware.org Received: from vms048pub.verizon.net (HELO vms048pub.verizon.net) (206.46.252.48) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 30 Apr 2007 16:05:44 +0100 Received: from ultsol.com ([72.74.243.178]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JHB00LMQGLDGXAA@vms048.mailsrvcs.net> for gdb@sourceware.org; Mon, 30 Apr 2007 10:05:38 -0500 (CDT) Date: Mon, 30 Apr 2007 15:05:00 -0000 From: "Fahd Abidi" Subject: trying to build gdb with renamed cygwin1.dll To: Message-id: <071DB0C788671B48940BC79F8B4930691181F4@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/msg00166.txt.bz2 Hello, I was trying to build a gdb version that would use a renamed version of cygwin1.dll and some of the other dll's that gdb seem to depend on. I determined all the dll's that gdb relies on using the "cygcheck" command My purpose is to try and build a gdb that so I can move it across different windows platforms with out worrying about newer or older versions of the cygwin dll interfering. I already looked at the MinGW option but the newer versions of gdb do not build against mingw32. My procedure was something like so, copied and renamed the dll's cygwin1, cygiconv-2,cygitl-3,cygcurses-8,tcl84,tk84 into another directory. Then tried to compile gdb against these renamed dll's by using the --libdir configure option. Unfortunately the resulting gdb executable totally ignores these renamed libraries and still links against the original dlls. Is this going to be possible to do? Thanks allot in advance. Fahd =20