From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: binutils@sourceware.org
Subject: Cross-assembling for AIX/PowerPC64
Date: Fri, 25 Jul 2014 07:22:00 -0000 [thread overview]
Message-ID: <53D205B3.1060904@elis.ugent.be> (raw)
Hi,
I have configured binutils 2.24 using the following configure command
(on OS X 10.9):
../configure --target=powerpc-ibm-aix53 --with-sysroot --disable-werror
The resulting assembler can assemble for AIX/PowerPC (32 bit) fine.
However, when I try to assemble for AIX/PowerPC64 with this command:
powerpc-ibm-aix53-as -a64 -u -o
../../rtl/units/powerpc64-aix/ctypes.o
../../rtl/units/powerpc64-aix/ctypes.s -mpwr5
Then I get the following error:
Assembler messages:
Fatal error: selected target format 'aixcoff64-rs6000' unknown
Looking at "powerpc-ibm-aix53-objdump -i", these are the supported
object file formats:
***
aixcoff-rs6000
(header big endian, data big endian)
powerpc:common
rs6000:6000
aix5coff64-rs6000
(header big endian, data big endian)
powerpc:common
rs6000:6000
srec
(header endianness unknown, data endianness unknown)
powerpc:common
rs6000:6000
symbolsrec
(header endianness unknown, data endianness unknown)
powerpc:common
rs6000:6000
verilog
(header endianness unknown, data endianness unknown)
powerpc:common
rs6000:6000
tekhex
(header endianness unknown, data endianness unknown)
powerpc:common
rs6000:6000
binary
(header endianness unknown, data endianness unknown)
powerpc:common
rs6000:6000
ihex
(header endianness unknown, data endianness unknown)
powerpc:common
rs6000:6000
aixcoff-rs6000 aix5coff64-rs6000 srec symbolsrec verilog
tekhex
powerpc:common aixcoff-rs6000 aix5coff64-rs6000 srec symbolsrec verilog
tekhex
rs6000:6000 aixcoff-rs6000 aix5coff64-rs6000 srec symbolsrec verilog
tekhex
binary ihex
powerpc:common binary ihex
rs6000:6000 binary ihex
***
How can I either add support for aixcoff64-rs6000, or make "-a64" select
aix5coff64-rs6000 as opposed to aixcoff64-rs6000? Additionally, while
I'm almost sure that there must be a command line option for "as" to
explicitly specify the output file format (like there is for ld), I
couldn't find it in its help (although that wouldn't be a final
solution, because then our compiler would have to auto-detect whether
it's using GNU as or native AIX as to determine which command line
options to pass).
Thanks,
Jonas
PS: the command I use to assemble for AIX/PowerPC (32 bit) is the same
as the one for 64 bit, except without the "-a64" (explicitly adding
"-a32" also works in that case).
next reply other threads:[~2014-07-25 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 7:22 Jonas Maebe [this message]
2014-07-25 7:36 ` Tristan Gingold
2014-07-25 8:10 ` Jonas Maebe
2014-07-25 8:26 ` Tristan Gingold
2014-07-25 8:31 ` Tristan Gingold
2014-07-25 9:32 ` Jonas Maebe
2014-07-25 9:36 ` Tristan Gingold
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=53D205B3.1060904@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--cc=binutils@sourceware.org \
/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).