From: Andrew Cagney <ac131313@redhat.com>
To: Sophie <sophiesong@eyou.com>
Cc: gdb@sources.redhat.com
Subject: Re: About bfd_elf32_xx_vec
Date: Tue, 17 Jun 2003 19:47:00 -0000 [thread overview]
Message-ID: <3EEF6F83.3000700@redhat.com> (raw)
In-Reply-To: <20030617223059.35928.qmail@eyou.com>
>>This looks like more of a BINUTILS (binutils@sources.redhat.com)
>>question. Can you, for instance, get OBJDUMP to build?
>>
>>Andrew
>>
>
> I'm so grateful for your response and sorry to bother you again.
> Do you mean that GDB needs BINUTILS's support? So if I want to port gdb ,I
> should make some changes to BINUTILS first?Is there some other special
> support gdb requires? And how can I get OBJDUMP? What kind of file is it?
GDB and BINUTILS share a common repository and much code so it is
possible to CO either or both together. See:
http://sources.redhat.com/binutils/. Also see:
http://sources.redhat.com/gdb/current/ (use gdb+binutils).
Andrew
next prev parent reply other threads:[~2003-06-17 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 14:30 Sophie
2003-06-17 19:47 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 13:09 songhui
2003-06-13 15:48 ` 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=3EEF6F83.3000700@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=sophiesong@eyou.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).