From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] OpenBSD/mips64 target and native support
Date: Sun, 31 Oct 2004 20:07:00 -0000 [thread overview]
Message-ID: <418545F4.8060401@gnu.org> (raw)
In-Reply-To: <200410311945.i9VJjMoG002666@elgar.sibelius.xs4all.nl>
Mark Kettenis wrote:
> Date: Sun, 31 Oct 2004 13:39:08 -0500
> From: Andrew Cagney <cagney@gnu.org>
>
> >>> This part:
> >>>
> >>>
> >>>> +DEPRECATED_TM_FILE= tm-nbsd.h
> >>>
> >>>
> >>> is no longer acceptable.
>
> The situtation we have here is identical to that we encountered when we
> first made it a requirement that not just new architectures, but also
> extensions to exsting architectures, had to be multi-arch. We set the
> standard and then helped developers exceed it.
>
> Our only mistake was to "blink" when it came to the solib problem.
> We've been "blinking" for too many years now.
>
> So should I just commit the attached to get things moving?
If it was committed after 2004-09-13, sure. Oh, it wasn't.
> IMHO, getting the solib h thingy fixed simply isn't top priority.
> There are more important issues in GDB that deserve my attention.
> Scaring away contributors by making unreasonable demands isn't a
> sensible thing to do.
Our situtation here is identical to what we encountered with basic
multi-arch, the frame code, the regcace code, the function call code.
There, with our help and co-operation, people not just stepped up to,
but also exceeded the challenge.
Andrew
next prev parent reply other threads:[~2004-10-31 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 12:16 Mark Kettenis
2004-10-25 15:24 ` Andrew Cagney
2004-10-25 15:29 ` Daniel Jacobowitz
2004-10-25 19:01 ` Andrew Cagney
2004-10-31 18:39 ` Andrew Cagney
2004-10-31 19:45 ` Mark Kettenis
2004-10-31 20:07 ` Andrew Cagney [this message]
2004-10-31 22:28 ` Mark Kettenis
2004-11-01 0:48 ` 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=418545F4.8060401@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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