>> /usr/bin/ld: error: Source object asm.o has EABI version 0, but target
>> program has EABI version 5
>
> Asasm is not yet fully EABI compliant and this is high on my todo list.
> You can do a temporary hack by defining ELF_EABI (see src/output.c) and
> see how far you get with this in your project.
I've been running into a few other troubles, starting with the fact that
quite a lot of the ARMv6 opcodes don't seem to have been implemented yet
(any idea when they're likely to appear?). I thought I'd work around it by
defining the ones I needed as macros, but then I find that :CC_ENCODING: has
been implemented inconsistently with armasm and objasm, so for example:
! 0, :STR::CC_ENCODING:"AL"
should output "E0000000", but outputs "0000000E" instead.
I thought I'd update to the head of subversion to see if either of those had
been addressed, but instead I found that the EABI hack had stopped working,
I now get:
output.c:592:19: error: 'EF_ARM_EABI_VER5' undeclared
when building asasm (with ELF_EABI defined). Is there a way to get this back
please?
Thanks,
Ben
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
No comments:
Post a Comment