ECX bootstrap codes on MOS and OS4 using VAsm

[Samurai_Crow]

I'm in the process of starting a new fork of ECX, the AmigaE compiler for PPC and 68020+. I've run into a snag. The startup codes are bootstrapped in Assembly and I don't know what the settings should be for MorphOS and OS4 on VAsm.

I've already gotten the PAsm PPC sources massaged into VAsmPPC format and the AsmOne sources massaged into VAsm68k. What settings do I need to get the right object file formats? I know OS4 uses an ELF derivative. I think MorphOS does too for that matter. Yet the startup codes are different for OS4 and MorphOS.

[phx]

Sorry, missed that. For urgent questions use email.

Originally Posted by Samurai_Crow

I've already gotten the PAsm PPC sources massaged into VAsmPPC format and the AsmOne sources massaged into VAsm68k.

That was certainly already most of the work.

Is PAsm Sam Jordan's PPC assembler? I remember it used a kind of 68k Motorola syntax. Maybe compiling a vasmppc_mot with mot-syntax module would have made things easier.

What settings do I need to get the right object file formats? I know OS4 uses an ELF derivative. I think MorphOS does too for that matter.

Correct. Just assemble with -Felf, so vasm outputs ELF object files.

Yet the startup codes are different for OS4 and MorphOS

Of course. Two very different systems!

[Samurai_Crow]

My question was answered on AmigaWorld.net by directing me to a tutorial on Morph.zone .

To make a long story short I found conditional Assembly for OS4 startup code by defining a macro from the command line. It builds ok but I still need to test it.

Thanks!

[Samurai_Crow]

@phx
Hypexed found the PAsm sources on your website. It's one of your precursors to VAsm.

http://phoenix.owl.de/pasm.tar.gz

He has figured that ECX and therefore our EEC compiler require the object file be written in Extended HUNK format rather than ELF. VAsm doesn't appear to support that feature but now that I have PAsm, I'm reverting to the unmodified sources.

[phx]

Sorry. Missed that again. The "vasm" was cut from the thread title in my view, so I didn't take notice...

Originally Posted by Samurai_Crow

He has figured that ECX and therefore our EEC compiler require the object file be written in Extended HUNK format rather than ELF. VAsm doesn't appear to support that feature but now that I have PAsm, I'm reverting to the unmodified sources.

Ok. Hope you got it running, and I'm only 17 months too late, but vasm always supported Extended Hunk Format. You only have to select

-Fhunk

as output format, and vasm's hunk output module automatically knows that it has to use the EHF PPC extensions to it, when using the PPC backend.

[Samurai_Crow]

Thanks! I'll get things updated when I get the chance!