MAME4ALL ARM compilation - relocations in generic ELF problem

An update:

On the errors I'm getting when compiling -or more specifically, when linking- MAME4ALL (src/raze/raze/raze_1.o: Relocations in generic ELF (EM: 3)), this is not due to crosscompiling an .o file that was produced for a different architecture. This seems to be produced by modules written in assembler (src/raze/raze/raze_1.asm and more on that subdirectory) that are compiled along with the C and C++ modules upon running "make". Before doing this, there is no .o file in that directory, so these are produced in compilation time.

This puzzles me even more, as the compiler seems to be accepting these modules, but the code produced (the .o files) is producing that error, as if the compiled code was not understood by the CPU.

Does anyone know:
- What this code does?
- Is there any way to produce these .o files in a form acceptable to an ARM processor? (I guess this should've appeared when compiling MAME4ALL for any non-x86 architecture such as the iPhone or iPad?
- Any chance of simply removing these modules and compiling a version without them? How would this be made?

I suppose that XO-Platform uses VIA-C7 x86 processor so Raze Z80 assembler core must compile it. Can you compile Fame M68K assembler core without linking problem? This message appear when you try to add a module for other architecture, for example when you try to link with a ELF module for X86 on ARM target.

Send me your Makefile that you use.

Anyway, you can compile without assembler changing disabling (no defining) M68000_ASM_CORE and Z80_ASM_CORE at Makefile/config.mk.