From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: "Jim Blandy" <jimb@redhat.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: multi-arched Linux target
Date: Thu, 05 Aug 2004 00:10:00 -0000 [thread overview]
Message-ID: <004c01c47a80$876fcc30$5169910a@E5A02646> (raw)
In-Reply-To: <vt2oelqo6gy.fsf@zenia.home>
> > > Do I have to use MULTI_ARCH_PARTIAL for Linux target?
>
> I think so. You'll need to have a tm-*.h file, which automatically
> brings you down to MULTI_ARCH_PARTIAL. You don't need to actually
> #define that anywhere, though; just having a tm-*.h file at all
> automatically sets that. Search for GDB_TM_FILE in defs.h.
>
> But I don't think that'll cause you any problems. Since you're not
> overriding them, it won't affect any of the definitions you're
> currently getting from gdbarch.h. Things should just continue to work
> normally.
I see. I'll use MULTI_ARCH_PARTIAL.
Thank you.
===
Kei Sakamoto
Renesas Technology Corp.
sakamoto.kei@renesas.com
prev parent reply other threads:[~2004-08-05 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 15:57 Kei Sakamoto
2004-08-02 1:14 ` Kei Sakamoto
2004-08-04 23:01 ` Jim Blandy
2004-08-05 0:10 ` Kei Sakamoto [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='004c01c47a80$876fcc30$5169910a@E5A02646' \
--to=sakamoto.kei@renesas.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).