From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Eliminate write_register from solib-sunos.c
Date: Mon, 14 May 2007 20:28:00 -0000 [thread overview]
Message-ID: <200705142028.l4EKSnKW008389@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070514152149.GA15148@caradoc.them.org> from "Daniel Jacobowitz" at May 14, 2007 11:21:49 AM
Daniel Jacobowitz wrote:
> On Mon, May 14, 2007 at 05:00:12PM +0200, Ulrich Weigand wrote:
> > Interestingly enough, it would appear that none of the Solaris targets
> > are actually using solib-sunos.o. The only references I can find are
> > in various bsd *native* target's .mh files.
> >
> > In fact, this is very weird as those same bsd targets have solib-svr4.o
> > in their .mt files. Which one is getting used in that case? I'll try
> > to find out what's going on here ...
>
> Don't confuse SunOS and Solaris :-) I believe that solib-sunos.c is
> for a.out shared libraries. However I don't know which one ends up
> used... maybe they're getting lucky with link order?
That's it: the TDEP files come *before* NAT files in link order,
thus the _initialize_svr4_solib function is called before
_initialize_sunos_solib in init.c, and as both set the
current_target_so_ops variable, the second call wins.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2007-05-14 20:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 0:31 Ulrich Weigand
2007-05-13 23:55 ` Daniel Jacobowitz
2007-05-14 15:01 ` Ulrich Weigand
2007-05-14 15:15 ` Mark Kettenis
2007-05-14 20:53 ` Ulrich Weigand
2007-06-04 18:53 ` Ulrich Weigand
2007-06-15 16:46 ` Mark Kettenis
2007-06-15 16:58 ` Ulrich Weigand
2007-06-15 21:22 ` Mark Kettenis
2007-06-15 21:28 ` Daniel Jacobowitz
2007-06-15 22:13 ` Ulrich Weigand
2007-05-14 15:21 ` Daniel Jacobowitz
2007-05-14 20:28 ` Ulrich Weigand [this message]
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=200705142028.l4EKSnKW008389@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--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