From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Remove ptrace-based Alpha OSF support
Date: Sat, 28 Apr 2007 20:29:00 -0000 [thread overview]
Message-ID: <20070428195500.GA6695@caradoc.them.org> (raw)
In-Reply-To: <200704281850.l3SIobkv014053@d12av02.megacenter.de.ibm.com>
On Sat, Apr 28, 2007 at 08:50:37PM +0200, Ulrich Weigand wrote:
> However, this has been broken a long time ago: CVS revision 1.2
> of procfs.c already no longer has the #ifdef HAVE_OPTIONAL_PROC_FS
> support. In fact, I'm not quite sure what happened there:
>
> revision 1.2
> date: 2000/02/16 08:02:57; author: cagney; state: Exp; lines: +4540 -5031
> From Rodney Brown: Define MERGEPID when needed.
>
> as this revision is basically a re-write of the whole file, which doesn't
> really match the log entry ...
This bit I can explain. The diff between 1.1 and 1.2 is not
interesting; the diff between the last revision on the 1.1.1.x vendor
branch is. A number of GDB snapshots were imported to create the
sourceware repository, and CVS's handling of imports is quirky.
> The following patch implements the above suggestion. It's not
> really tested as I don't have access to an OSF system, but it
> appears to compile (modulo procfs headers), and the configuration
> changes seem to work ...
>
>
> What do you think? Is this reasonable? Did I miss something
> in the above analysis?
This all seems reasonable to me. I believe that Joel has access to an
OSF system at AdaCore; maybe he can test the patch for you?
Someone told me while I was obsoleting targets that osf1 and probably
osf2 could go. I don't recall who.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-04-28 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 19:28 Ulrich Weigand
2007-04-28 19:55 ` Mark Kettenis
2007-04-28 20:29 ` Daniel Jacobowitz [this message]
2007-04-28 23:36 ` Ulrich Weigand
2007-04-29 7:08 ` Joel Brobecker
2007-04-30 12:34 ` Ulrich Weigand
2007-05-05 4:24 ` Joel Brobecker
2007-05-06 21:09 ` Ulrich Weigand
2007-05-06 22:37 ` Joel Brobecker
2007-05-06 23:05 ` Ulrich Weigand
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=20070428195500.GA6695@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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