From: Kevin Buettner <kevinb@redhat.com>
To: Elena Zannoni <ezannoni@cygnus.com>, Andrew Cagney <ac131313@cygnus.com>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Define SVR4 link map offset fetcher for Linux/PPC
Date: Mon, 03 Dec 2001 10:26:00 -0000 [thread overview]
Message-ID: <1011203182614.ZM32534@ocotillo.lan> (raw)
In-Reply-To: Elena Zannoni <ezannoni@cygnus.com> "Re: [PATCH] Define SVR4 link map offset fetcher for Linux/PPC" (Dec 3, 12:38am)
On Dec 3, 12:38am, Elena Zannoni wrote:
> Andrew Cagney writes:
> > > I've tested this patch on AIX (to make sure I didn't break the build
> > > or cause any regressions) and also in a Linux/x86 cross Linux/PPC test
> > > environment.
> >
> > Kevin, did you try this with --target=powerpc-eabi as listed in the
> > MAINTAINERS? I'm seeing a -Werror of solib_add() undefined:
> >
> > > /home/scratch/PENDING/rm-obsolete/src/gdb/solib-svr4.c:912: warning: implicit declaration of function `solib_add'
> > > gmake[1]: *** [solib-svr4.o] Error 1
> > > gmake[1]: Leaving directory `/home/scratch/PENDING/rm-obsolete/carp/X-powerpc-eabi/gdb'
> > > gmake: *** [all-gdb] Error 2
> >
> > enjoy,
> > Andrew
> >
>
>
> With powerpc-eabi I am also getting these:
>
> /bart/ezannoni/uberbaum/src/gdb/solib-svr4.c:857: undefined reference to `remove_solib_event_breakpoints'
> /bart/ezannoni/uberbaum/src/gdb/solib-svr4.c:984: undefined reference to `create_solib_event_breakpoint'
> libgdb.a(solib.o): In function `clear_solib':
> /bart/ezannoni/uberbaum/src/gdb/solib.c:732: undefined reference to `disable_breakpoints_in_shlibs'
> collect2: ld returned 1 exit status
>
> I guess it is missing the SOLIB_ADD macro definition.
> Should an
> #include "solib.h" be added to the config/powerpc/*.h files?
Yeah, I guess so. I was trying to think of a better way to handle this,
but this seems like the best solution for now.
Ultimately, we'd like to *not* have ``#include "solib.h"'' in *any*
config/*/{tm,nm}-*.h files. Rather, this include statement should either
be placed directly in defs.h, or even better still, in just those files
which require it. But to get to the point where we'll be able to do this,
we'll need to convert the other files which implement solib support over
to using the new mechanisms. The files which need to be converted are
coff-solib.c, irix5-nat.c, pa64solib.c, somsolib.c, and xcoffsolib.c.
(Thanks to Nick Duffek, osfsolib.c has already been converted. It
just needs to be marked as obsolete.)
Kevin
prev parent reply other threads:[~2001-12-03 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 8:55 Kevin Buettner
2001-11-30 16:35 ` Kevin Buettner
2001-12-02 10:02 ` Andrew Cagney
2001-12-02 21:32 ` Elena Zannoni
2001-12-03 10:26 ` Kevin Buettner [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=1011203182614.ZM32534@ocotillo.lan \
--to=kevinb@redhat.com \
--cc=ac131313@cygnus.com \
--cc=ezannoni@cygnus.com \
--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