Low vector RPi ROM build failure

Building a low vector RPi ROM from the current daily source code archive, 2015-12-21, fails here as below, a default high vector build works perfectly. (I did a successful low vector build a couple of months ago.)

The syntax of the Components file has been purloined from iMx6 and the amendments are :-

Kernel -at 0xFC010000 -options ASFLAGS="-PD \"HiProcVecs SETL {FALSE} -PD \"CMOS_Override SETS \\\"= FileLangCMOS,fsnumber_SDFS,CDROMFSCMOS,&C0\\\"\""

FPEmulator -options FPE_APCS=3/32bit FPEANCHOR=Low

Kernel (castle.RiscOS.Sources.Kernel)...
amu -E  install_rom INSTDIR=RAM::RamDisc0.$.ROOL.BCM2835Dev.Install.ROOL.BCM2835.RISC_OS COMPONENT=Kernel TARGET=Kernel ASFLAGS="-PD \"HiProcVecs SETL {FALSE}  -PD \"CMOS_Override SETS \\\"= FileLangCMOS,fsnumber_SDFS,CDROMFSCMOS,&C0\\\"\""
objasm -PD "HiProcVecs SETL {FALSE}  -PD "CMOS_Override SETS \"= FileLangCMOS,fsnumber_SDFS,CDROMFSCMOS,&C0\"" -PD "FreezeDevRel SETL {FALSE}" -depend !Depend    -ihdr -i<Hdr$Dir>.Global -i<Hdr$Dir>.Interface -i<Hdr$Dir>.Interface2 -pd "APCS SETS \"APCS-32\"" -pd "Machine SETS \"RPi\"" -pd "UserIF SETS \"Raspberry\"" -g -o o.RPi.Kernel GetAll.s
ARM AOF Macro Assembler 4.03 (Acorn Computers Ltd) [15 Oct 2015]
Output file already specified
Unrecognised parameter '-o'
AMU: *** exit (1) ***

AMU: *** 'install_rom' not re-made because of errors ***

Error running make install_rom on module 'Kernel'.
Fatal error running make install_rom on module 'Kernel'.
Batched errors...
Error running make install_rom on module 'Kernel'.

Might be missing closing quotes on ‘HiProcVecs SETL {FALSE}’? gobsmacked if it is – don’t even have a copy of objasm!

FPEANCHOR=Low

Can’t it tell this by interrogating the OS?

Might be missing closing quotes on ‘HiProcVecs SETL {FALSE}

It was. Top answer. Built with :-

Kernel -at 0xFC010000 -options ASFLAGS="-PD \"HiProcVecs SETL {FALSE}\" -PD \"CMOS_Override SETS \\\"= FileLangCMOS,fsnumber_SDFS,CDROMFSCMOS,&C0\\\"\""

Many thanks.

A low vector build of the current Pi ROM seems to work OK (not yet tried it, but the compilation worked OK) using the above ‘Kernel’ change.

A bit late to the party, but…

FPEANCHOR=Low

Can’t it tell this by interrogating the OS?

It can be made to interrogate the OS for the FPEAnchor address (or, more likely, modified to stop using FPEAnchor completely), but there’s a lot of scary assembler which will need touching. It’ll get done at some point, but since the current approach works there’s no big rush to change it.