From: mrcompiler@mrcompiler.com
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Multi-Arch symbol read warning message
Date: Sat, 22 Feb 2003 17:32:00 -0000 [thread overview]
Message-ID: <20030222172627.31225.qmail@admin1.cvtt.net> (raw)
In-Reply-To: <3E56F3A4.3000704@redhat.com>
Andrew Cagney writes:
>
>> I am building a multi-arch version of GDB for handling ELF format core
>> files for the ARM and PowerPC processors running on vxWorks. In order to
>> get everything to build I combined the information from
>
> Hmm, cute.
This sort of sounds like I might using multi-arch in a different from
intended ( or normal to date ). I did notice that most of the other stuff
was supporting a single processor class across multiple OS environments.
Is there any reason this shouldn't work?
I also had an ambiguity problem with --enable-targets=all in bfd and had to
specifically build those with --enable-targets=strongarm-coff, powerpc-elf,
strongarm-elf ( possibly arm-elf, I don't have access to the build tree at
this instant).
> I posted a WIP patch for this several years ago but never got around to
> integrating it (there wasn't sufficient immediate needed). Now that most
> architectures are multi-arch, it is definitly time to integrate such a
> change.
You mean a patch for my symbol read warnings? Can you point me to it?
>
> Can you contribute this stuff?
>
Yes, I was planning on talking to you folks about this once I got it
working. Obviously I don't want to make my first contribution a
brain-damaged hack. Not that I'm necessary opposed to brain-damaged hacks as
anyone who has downloaded my stuff from freshmeat can attest....
Gene
prev parent reply other threads:[~2003-02-22 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 22:30 mrcompiler
2003-02-21 4:23 ` Jim Blandy
2003-02-22 3:23 ` mrcompiler
2003-02-22 16:20 ` Daniel Jacobowitz
2003-02-22 3:46 ` Andrew Cagney
2003-02-22 17:32 ` mrcompiler [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=20030222172627.31225.qmail@admin1.cvtt.net \
--to=mrcompiler@mrcompiler.com \
--cc=ac131313@redhat.com \
--cc=gdb@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