Compiling my own 'yasm' executable
Robert Riebisch
rr at bttr-software.de
Wed May 31 03:43:24 PDT 2006
Peter Johnson wrote:
> For Unix systems, the easiest way to do this is to edit the Makefile.inc's
> to un-include the modules you don't want included in the build. With
> DJGPP, it's almost easier; just edit Mkfiles/Makefile.dj and remove the
> modules you don't want; just be sure to remove both the _OBJS and the
> YASM_MODULES portions for each module.
Thanks! Works fine. :-)
> Yes, we will. Currently yasm only supports the old-style nasm bin, which
OK :-)
> only allowed 3 sections (.text, .data, .bss). NASM at one point added
> enhanced bin support, which allows other section names and positioning
> flags. We'll do the same; look for it in 0.6.
I found another small 'nasm'-thing, that 'yasm' doesn't support:
.hd: Db '1' - 80h, ':', ' ' + 80h
or
badtext: Db 'Bad partition table!', ' ' + 80h
This will result in error message "label or instruction expected at
start of line".
Seems like '' constants mathematics are not allowed so far.
Another problem:
I cannot build our http://www.bttr-software.de/products/bootmgr/#down
:-(
I get "Exiting due to signal SIGABRT" with my minimized
yasm-r1546.tar.gz DJGPP build or with yasm-r1546-dos.exe/yasm-r1546.exe
it is:
***
c:\tmp\2\yasm.exe -o..\..\bootmgr.com bootmgr.asm
INTERNAL ERROR at libyasm/bytecode.c, line 284: written length does not
match op
timized length
Abort!
***
Robert Riebisch
--
BTTR Software
http://www.bttr-software.de/
More information about the yasm-devel
mailing list