From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8307 invoked by alias); 18 Jan 2008 19:27:37 -0000 Received: (qmail 8296 invoked by uid 22791); 18 Jan 2008 19:27:37 -0000 X-Spam-Check-By: sourceware.org Received: from ctb-mesg-1-2.saix.net (HELO ctb-mesg-1-2.saix.net) (196.25.240.80) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 18 Jan 2008 19:27:08 +0000 Received: from [192.168.0.8] (dsl-242-9-220.telkomadsl.co.za [41.242.9.220]) by ctb-mesg-1-2.saix.net (Postfix) with ESMTP id A76B5AD1A; Fri, 18 Jan 2008 21:27:04 +0200 (SAST) From: "Gerrit van Niekerk" To: Jim Blandy Date: Fri, 18 Jan 2008 19:27:00 -0000 MIME-Version: 1.0 Subject: Re: Problem building cross-debugger Reply-to: gerritvn@gpvno.co.za,gpvno@telkomsa.net CC: gdb@sourceware.org Message-ID: <479119AB.8493.2781D98@gerritvn.gpvno.co.za> In-reply-to: References: <47908F14.31772.5AD24E@gerritvn.gpvno.co.za>, <4790EF3A.8104.1D28BDA@gerritvn.gpvno.co.za> (Gerrit van Niekerk's message of "Fri, 18 Jan 2008 18:26:02 +0200"), X-mailer: Pegasus Mail for Windows (4.41) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body 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: 2008-01/txt/msg00178.txt.bz2 On 18 Jan 2008 at 10:52, Jim Blandy wrote: > I think the reason you haven't gotten much interaction is that you may > be the only person on the list who's working with such a > configuration. If you could figure out the source of the problem and > suggest a patch, that would get things rolling. It is not really such an abnormal configuration. I tried building a standard Cygwin build, host and target using the current Cygwin release and latest CVS GDB and get the same problem. Trying to just figure out the makefiles generated by configure makes me dizzy! I already spent more than a week just getting it to produce an exe by hacking the screen output. I would love to supply a patch if somebody can just direct me to the place to start looking. Well I know it is somewhere in the bfd directory and that cpu-i386.o should probably be part of libbfd.a, but is not because objdump tells me so. Somebody familiar with the GDB build process can probably tell me in a few seconds what to look for and I am more than willing to assist to generate a patch for the gdb community at large even though my problem is currently resolved. -- Gerrit van Niekerk GP van Niekerk Ondernemings BK Roosstraat 211, Meyerspark, 0184, South Africa Tel: +27(12)8036501 Fax SA: 0866 413 555 Cell: +27(73)6891370 Fax Int'l: +1(206)2034139 Email: gerritvn@gpvno.co.za Web: http://www.gpvno.co.za