Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: joseph@codesourcery.com, kevinb@redhat.com,
	gdb-patches@sources.redhat.com
Subject: Re: Assume solib.h
Date: Thu, 11 Nov 2004 21:48:00 -0000	[thread overview]
Message-ID: <4193DDCE.7060205@gnu.org> (raw)
In-Reply-To: <200411112005.iABK5FrV098628@elgar.sibelius.xs4all.nl>

Mark Kettenis wrote:
>    Date: Thu, 11 Nov 2004 14:38:08 -0500
>    From: Andrew Cagney <cagney@gnu.org>
> 
>    Joseph, Kevin,
> 
>    The attached patch illustrates the minimum needed to enable solibs for 
>    Solaris.  It just needs to be filled out so that other systems are 
>    updated like I did for PPC linux (hint, hint ;-)
> 
>    Once this is in place we can follow through with other cleanups - much 
>    will fall out!
> 
>    There's just one non-technical nit.
> 
>    It means breaking non solib.[hc] shared library systems.  Kevin 
>    indicated that there were two - AIX and HP/UX remaining.  I think we can 
>    live with that - we've patiently waited for what, more than two years 
>    for nothing to happen, so it is now time to give things that gentle push.
> 
> IIRC (and looking at the code I think I do remember it correctly) this
> also breaks targets without shared library support.

I gave it a full test with PowerPC GNU/Linux and sniff test with 
powerpc-elf.  If there are other problems, I'm sure they'll be sorted out.

Andrew


  reply	other threads:[~2004-11-11 21:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 19:39 Andrew Cagney
2004-11-11 20:06 ` Mark Kettenis
2004-11-11 21:48   ` Andrew Cagney [this message]
2004-11-11 22:24     ` Mark Kettenis
2004-11-12 15:52       ` Andrew Cagney
2004-11-12 17:20         ` Eli Zaretskii
2004-11-15 21:32           ` Kevin Buettner
2004-11-15 23:35             ` Mark Kettenis
2004-11-17 17:35             ` Eli Zaretskii
2004-11-15 23:59           ` Andrew Cagney
2004-11-16  1:20             ` Daniel Jacobowitz
2004-11-16  5:00             ` Eli Zaretskii
2004-11-16  8:37               ` Mark Kettenis
2004-11-16 20:54                 ` Eli Zaretskii
2004-11-16 16:14               ` Andrew Cagney
2004-11-16 19:18                 ` Mark Kettenis
2004-11-18 14:10                   ` Andrew Cagney
2004-11-18 14:37                     ` Mark Kettenis
2004-11-18 17:28                       ` Kevin Buettner
2004-11-19 17:11                       ` Andrew Cagney
2004-11-19 17:25                         ` Randolph Chung
2004-11-19 17:36                           ` Joel Brobecker
2004-11-19 17:40                             ` Randolph Chung
2004-11-19 17:56                               ` Joel Brobecker
2004-11-19 19:29                         ` Joseph S. Myers
2004-11-16 21:06                 ` Eli Zaretskii
2004-11-16 22:27                   ` Andrew Cagney
2004-11-17  4:52                     ` Eli Zaretskii
2004-11-16  1:40         ` Daniel Jacobowitz
2004-11-16  4:54           ` Eli Zaretskii
2004-11-16 16:31           ` Andrew Cagney
2004-11-16 19:45             ` Mark Kettenis
2004-11-16 21:06             ` Eli Zaretskii
2004-11-12  1:11 ` Randolph Chung
2004-11-13  1:10   ` 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=4193DDCE.7060205@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=kevinb@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