From: Alan Modra <amodra@bigpond.net.au>
To: Richard Henderson <rth@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: elfNN-foo-fbsd hackery?
Date: Mon, 14 Oct 2002 21:28:00 -0000 [thread overview]
Message-ID: <20021015135845.K22176@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <20021015012721.GA24112@redhat.com>; from rth@redhat.com on Mon, Oct 14, 2002 at 06:27:21PM -0700
On Mon, Oct 14, 2002 at 06:27:21PM -0700, Richard Henderson wrote:
> * Makefile.am (BFD64_BACKENDS): Remove elf64-alpha-fbsd.lo
> (BFD64_BACKENDS_CFILES): Remove elf64-alpha-fbsd.c
> * elf64-alpha-fbsd.c: Remove file. Move code ...
> * elf64-alpha.c: ... here.
Exactly what I intended doing when I found a spare moment. x86 has
qnx to contend with as well.
Of course, the bloat only happens when you enable multiple bfd
targets, and I have a nagging suspicion that certain operations
(*) might bomb with "File format is ambiguous" if you provide
two bfd vectors.
*) Like "objcopy -O binary blah.o blah.bin". Hmm, here's an
example:
$ .../all/binutils/objcopy -O binary powerpc-linux/libiberty/hex.o blah.bin
all/binutils/objcopy: powerpc-linux/libiberty/hex.o: File format not recognized
$ .../x86/binutils/objcopy -O binary powerpc-linux/libiberty/hex.o blah.bin
$
The "all" objcopy is --target=i686-linux --enable-targets=all,
while the "x86" objcopy is --target=i686-linux
--enable-targets=i686-linuxaout,i686-coff,hppa-linux,powerpc-linux
The first case fails because we're reading a non-default object which
matches multiple powerpc targets, while the second case works because
we only have one matching target. Not that I think this is
particularly worrying. I'm just illustrating the point that providing
two targets may not be desirable in all situations.
Gack, and that's a terrible error message from objcopy. Fixing..
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2002-10-15 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 18:27 Richard Henderson
2002-10-14 21:28 ` Alan Modra [this message]
2002-10-15 9:41 ` Richard Henderson
2002-10-15 16:46 ` Alan Modra
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=20021015135845.K22176@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=rth@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).