Home Original page

sparc/h8300 errors when converting binary to .o

Joel Sherrill joel.sherrill@oarcorp.com
Fri Jun 22 14:25:00 GMT 2007 
Hi,

To get the initial filesystem image for an
RTEMS application, we perform the following:

+ create a tarfile
+ objcopy it to a .o
+ link against the resulting .o

I added a new test to the RTEMS automated
test suite which includes this and now we
get failures on the sparc and h8300 which
are different but follow from the same sequence
so I am reporting this in one email.  I
can file PRs if you like.

The tar file is nothing special but I attached
it in case the actual data makes any difference.

This is with "2.17.50.20070522." I cc'ed Ralf
since he builds our RPMs and can answer questions.
I am on vacation after today.

sparc-rtems (aka sparc-elf)
=======================
cd rootfs ; tar cf ../o-optimize/tarfile web etc
cp o-optimize/tarfile .
sparc-rtems4.8-objcopy -I binary -O elf32-sparc tarfile o-optimize/tarfile.o
BFD: BFD (GNU Binutils) 2.17.50.20070522 internal error, aborting at 
../../binutils-2.17.50/bfd/elf32-sparc.c line 148 in 
elf32_sparc_final_write_processing

BFD: Please report this bug.
=======================

h8300-rtems (aka h8300-elf)
=======================
cd rootfs ; tar cf ../o-optimize/tarfile web etc
cp o-optimize/tarfile .
h8300-rtems4.8-objcopy -I binary -O elf32-h8300 tarfile o-optimize/tarfile.o
h8300-rtems4.8-ld -r -o o-optimize/temp.o  o-optimize/init.o 
o-optimize/tarfile.o
h8300-rtems4.8-ld: Relocatable linking with relocations from format 
elf32-h8300 (o-optimize/init.o) to format elf32-h8300 
(o-optimize/temp.o) is not supported
=======================

Thanks.

--joel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: tarfile.bz2
Type: application/x-bzip
Size: 925 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20070622/7a405f8b/attachment.bin>
More information about the Binutils mailing list