From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Build inf-ptrace.o when ptrace available
Date: Mon, 04 Oct 2004 14:34:00 -0000 [thread overview]
Message-ID: <20041004143443.GB6653@nevyn.them.org> (raw)
In-Reply-To: <41615EA5.8050803@gnu.org>
On Mon, Oct 04, 2004 at 10:31:01AM -0400, Andrew Cagney wrote:
> >On Fri, Oct 01, 2004 at 04:39:57PM -0400, Andrew Cagney wrote:
> >
> >>>Hello,
> >>>
> >>>This modifies GDB's configure to build inf-ptrace.o whenever the ptrace
> >>>call is available. Thoughts?
> >
> >
> >I think this only makes sense as part of the removal of NATDEPFILES,
> >and that it doesn't make sense without the context of how you plan to
> >remove the other members of NATDEPFILES. Since we're still going to
> >need a way to specify the native configuration files, why bother?
>
> See Mark's e-mail (and it is easier than remembering which NATDEPFILES
> need it).
I think that's a non-issue. You don't need to remember it - either
it's there or it isn't.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-10-04 14:34 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
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 [this message]
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=20041004143443.GB6653@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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