From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22581 invoked by alias); 4 Aug 2002 17:44:28 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 22573 invoked from network); 4 Aug 2002 17:44:26 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 4 Aug 2002 17:44:26 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 48A123CAD; Sun, 4 Aug 2002 13:44:22 -0400 (EDT) Message-ID: <3D4D67F6.10605@ges.redhat.com> Date: Sun, 04 Aug 2002 10:44:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020802 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa/i386] Consolidate i386 targets References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00081.txt.bz2 > On Sat, 3 Aug 2002, Andrew Cagney wrote: > > >> This patch replaces a number of explicit i386 (-aout, -coff, -elf, -pe) >> targets with a generic ``i386-*'' pattern. >> >> It then updates the MAINTAINERS file so that only one i386 target is >> listed or building: i386-elf. This should cut down on the number of >> targets that need building. > > > Why is this part a good idea? DJGPP is still supported, right? Yes, DJGPP is definitly still supported. DJGPP is a native configuration though, and the above list applies to the cross debuggers. >> * MAINTAINERS: Drop i386-aout and i586-pc-msdosdjgpp from target >> list. > > > Did I miss something? I don't think so. My understanding of the thread: http://sources.redhat.com/ml/gdb-patches/2002-05/msg00774.html > Date: Fri, 17 May 2002 13:21:46 -0400 >> From: Daniel Jacobowitz > >> > >> > Sorry, I still don't understand: does this mean a remote debugger with >> > some stub on the remote DOS/Windows machine? Or maybe the stub (or >> > gdbserver) running inside DOSEmu on the GNU/Linux box? > >> >> Those are both valid. >> > >> > My point is that DJGPP debugging is very special: there's no OS >> > provision for system calls like ptrace etc., so the only way to debug >> > a DJGPP inferior is to run it natively under a specially built program >> > that is linked against the DJGPP debug support library. I'm curious >> > how does your cross build achieve that, since I believe neither >> > gdbserver nor any of the remote-* modules support DJGPP as of now. > >> >> I didn't say it would be useful. But consult MAINTAINERS; everything >> listed in the "Targets" section on a --target= line is currently >> "expected" to be buildable as a cross debugger, to sanity check >> changes. That's all I was doing. > > > Then I don't think you (or anyone else on this list) should be > concerned with these problems: IMHO, a failure to build a > dysfunctional version of GDB is not a failure at all. is that trying to ensure that a cross DJGPP debugger always builds isn't useful. enjoy, Andrew