This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
binutils 2.17 warns m68k:cpu32 is incompatible with m68k:cpu32
- From: "Matthew R. Dempsky" <mrd at alkemio dot org>
- To: binutils at sourceware dot org
- Date: Fri, 7 Jul 2006 14:00:15 -0500
- Subject: binutils 2.17 warns m68k:cpu32 is incompatible with m68k:cpu32
(I'm not subscribed, so I would appreciate CC's, but I'll watch the
archives anyways just in case.)
When trying to link two or more cpu32 object files with ld from binutils
2.17, I get a warning that the m68k:cpu32 architecture of any input
files beyond the first is incompatible with m68k:cpu32 output, which
seems very nonsensical.
Should I be concerned with these warnings? ld from binutils 2.15 and
2.16.1 do not give this warning. I found a somewhat similar report in
the archive from about a week and a half ago[1], but this seems to
differ enough to be a different problem. (Also, no one appears to have
replied to it yet.)
To reproduce, configure binutils 2.17 with --target=m68k-elf, install,
and proceed as follows:
$ m68k-elf-as -mcpu32 -o start.o << EOF
.globl _start
_start:
jbsr foo
jbra _start
EOF
$ m68k-elf-as -mcpu32 -o foo.o << EOF
.globl foo
foo:
rts
EOF
$ m68k-elf-ld start.o foo.o
m68k-elf-ld: warning: m68k:cpu32 architecture of input file `foo.o' is
incompatible with m68k:cpu32 output
Thanks.
[1] http://sources.redhat.com/ml/binutils/2006-06/msg00402.html