Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFC] Unconditionally include shared library code
Date: Sun, 08 May 2005 14:24:00 -0000	[thread overview]
Message-ID: <20050508135839.GA7384@nevyn.them.org> (raw)
Message-ID: <20050508142400.GllYyj4M9FGqLaH44Wt4Nm4BROEOcXg1Mue4-yTPqJ8@z> (raw)
In-Reply-To: <200505081315.j48DF8AG030440@elgar.sibelius.xs4all.nl>

On Sun, May 08, 2005 at 03:15:08PM +0200, Mark Kettenis wrote:
>    Date: Mon, 2 May 2005 14:51:59 +0200 (CEST)
>    From: Mark Kettenis <mark.kettenis@xs4all.nl>
> 
>    This patch is an attempt to be able to link in the generic shared
>    library code in solib.c while attempting to keep the shared library
>    implementations that have not yet been converted to use the generic
>    code (Windows, coff) working.  It allows me to get rid of
>    DEPRECATED_TM_FILE in basically every *BSD target.
> 
>    I introduce two new files shlib.c, shlib.h.  I need these because
>    solib.h contains both the prototypes and macro defenitions for the
>    shared library stuff.  In the long run, I should be able to get rid of
>    either shlib.[ch] or solib.[ch] again.  I took the opportunity to give
>    various functions a somewhat more logical name.
> 
>    Comments are welcome.  It'd also be great if this could be tested on
>    Cygwin.
> 
> Hmm, no comments yet.  If this is really so uncontroversial, I'm going
> to check it in next weekend ;-).

My only comment is that I really don't like having both shlib* and
solib* (files and interface names).  Could you explain a little more
why shlib.h is necessary?

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-05-08 13:59 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 [this message]
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
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=20050508135839.GA7384@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb-patches@sourceware.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