From: Kevin Buettner <kevinb@redhat.com>
To: Michal Ludvig <mludvig@suse.cz>, gdb <gdb@sources.redhat.com>
Subject: Re: cross-target gdb compilation problems
Date: Mon, 01 Jul 2002 10:52:00 -0000 [thread overview]
Message-ID: <1020701175210.ZM14609@localhost.localdomain> (raw)
In-Reply-To: Michal Ludvig <mludvig@suse.cz> "cross-target gdb compilation problems" (Jul 1, 6:17pm)
On Jul 1, 6:17pm, Michal Ludvig wrote:
> When I add '#include "solib.h"' directly to breakpoints.c it compiles
> and links just fine. Also it seems like most targets use it anyway. If
> we would wrap all #defines in solib.h between #ifndef...#endif it would
> remain backward compatible for targets that define their own macros. Or
> am I wrong?
For targets with shared library support, I think you're right. I
think there may be problems, however, on targets without shared
library support. (In breakpoint.c, the SOLIB_ADD macro is being used
as a flag which indicates that the target has shared library support.)
> Like this:
>
> [solib.h]
> + #ifndef SOLIB_ADD
> #define SOLIB_ADD(filename, from_tty, targ, readsyms) \
> solib_add (filename, from_tty, targ, readsyms)
> + #endif
>
> Or is there another way to solve my compilation problems?
We've had this problem in the past for other pure multiarch targets.
I think we ended up creating (or recreating) a tm-*.h file for these
targets.
Kevin
prev parent reply other threads:[~2002-07-01 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 9:17 Michal Ludvig
2002-07-01 9:29 ` Andrew Cagney
2002-07-01 14:16 ` Michal Ludvig
2002-07-01 14:52 ` Andrew Cagney
2002-07-01 10:52 ` 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=1020701175210.ZM14609@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mludvig@suse.cz \
/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