From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Unconditionally include shared library code
Date: Sun, 08 May 2005 22:08:00 -0000 [thread overview]
Message-ID: <20050508220141.GA23567@nevyn.them.org> (raw)
In-Reply-To: <200505082146.j48Lk8TZ022794@elgar.sibelius.xs4all.nl>
On Sun, May 08, 2005 at 11:46:08PM +0200, Mark Kettenis wrote:
> Date: Sun, 8 May 2005 10:56:27 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Sun, May 08, 2005 at 04:51:25PM +0200, Mark Kettenis wrote:
> > Hmm, that'd work. We'll have to face the inconsistent interface issue
> > eventually, but it's a seperate issue indeed. Any objection if I
> > introduce a config/tm-solib.h and use that? Its purpose is a bit more
> > clear, and the risk of abuse is smaller. The mechanical update is not
> > without risk, but I'm willing to take it. Deal?
>
> I like it. It is indeed a tm file and shouldn't be used any other way.
>
> I reworked the patch to avoid shlib.[ch]. Looking at the changes I
> think the risk of changing solib.h into tm-solib.h under config/ is
> riskier than leaving config/ alone and simply removing the #defines
> from solib.h. I'm moving towards checking in the attached patch at
> the end of the coming week.
I like this even more! Kevin?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-08 22:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 12:53 Mark Kettenis
2005-05-08 13:15 ` Mark Kettenis
2005-05-08 13:59 ` Daniel Jacobowitz
2005-05-08 14:24 ` Daniel Jacobowitz
2005-05-08 14:40 ` Mark Kettenis
2005-05-08 14:48 ` Daniel Jacobowitz
2005-05-08 17:32 ` Mark Kettenis
2005-05-08 15:33 ` Daniel Jacobowitz
2005-05-08 22:01 ` Mark Kettenis
2005-05-08 22:08 ` Daniel Jacobowitz [this message]
2005-05-09 20:46 ` Kevin Buettner
2005-05-12 20:40 ` Mark Kettenis
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=20050508220141.GA23567@nevyn.them.org \
--to=drow@false.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