From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4289 invoked by alias); 5 Oct 2004 22:44:21 -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 4280 invoked from network); 5 Oct 2004 22:44:21 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 5 Oct 2004 22:44:21 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i95MiB7F010031 for ; Tue, 5 Oct 2004 18:44:16 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i95Mi5r02311; Tue, 5 Oct 2004 18:44:05 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 4048428D2; Tue, 5 Oct 2004 18:43:51 -0400 (EDT) Message-ID: <416323A7.2010201@gnu.org> Date: Tue, 05 Oct 2004 22:44:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040831 MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Mark Kettenis , gdb-patches@sources.redhat.com Subject: Re: [patch/rfc] Build inf-ptrace.o when ptrace available References: <415DC09D.2070407@gnu.org> <200410012154.i91Ls6lE001359@elgar.sibelius.xs4all.nl> <41615D1E.8070007@gnu.org> <20041004143416.GA6653@nevyn.them.org> <416179DE.70401@gnu.org> <20041004163533.GA12898@nevyn.them.org> In-Reply-To: <20041004163533.GA12898@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00100.txt.bz2 > We can't "get GNU/Linux [...] using procfs". Is there a technical problem blocking this? >>> Why is it orthogonal? If we assume that configure determines when /proc >>> and ptrace() and provides both to the user it certainly isn't. Idea's >>> such as Mark's and mine would make it easier. > > > Why is it related? How would this make it easier? It's not hard to > add a new backend file to all the Linux targets; it's really not much > different in a lot of little files than in one big one. I've done this > plenty of times. If we used configure.tgt and: switch "$target" *-*-linux* ) "objs=objs symfile-mem.c" esac then all GNU/Linux systems will always and consistently include symtab-mem.c. We don't, they don't ... We've already got configure.tgt checking OSABI and configure.host checking FLOATFORMAT so there's plenty of prior art. Further, modifying/merging just that file is going to be a lot easier than modifying/merging all the individual *.mh files. Andrew