From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Mark Kettenis <kettenis@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Build inf-ptrace.o when ptrace available
Date: Tue, 05 Oct 2004 22:44:00 -0000 [thread overview]
Message-ID: <416323A7.2010201@gnu.org> (raw)
In-Reply-To: <20041004163533.GA12898@nevyn.them.org>
> 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
next prev parent reply other threads:[~2004-10-05 22:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 20:40 Andrew Cagney
2004-10-01 21:54 ` Mark Kettenis
2004-10-04 14:24 ` Andrew Cagney
2004-10-04 14:34 ` Daniel Jacobowitz
2004-10-04 16:27 ` Andrew Cagney
2004-10-04 16:35 ` Daniel Jacobowitz
2004-10-05 22:44 ` Andrew Cagney [this message]
2004-10-05 22:59 ` Daniel Jacobowitz
2004-10-05 23:42 ` Andrew Cagney
2004-10-11 17:24 ` Andrew Cagney
2004-10-13 13:54 ` Daniel Jacobowitz
2004-10-14 17:14 ` Mark Kettenis
2004-10-04 17:20 ` Mark Kettenis
2004-10-04 17:51 ` Andrew Cagney
2004-10-04 18:23 ` Mark Kettenis
2004-10-03 14:50 ` Daniel Jacobowitz
2004-10-04 14:31 ` Andrew Cagney
2004-10-04 14:34 ` Daniel Jacobowitz
2004-10-04 16:18 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416323A7.2010201@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox