On Sat, 18 Sep 1999, George Woltman wrote:
> At 03:01 PM 9/18/99 -0400, Darxus wrote:
> >I have a question though. Why make the Linux source dependant on code
> >which needs to be assembled under DOS, when there is an assembler for
> >Linux (as) ?
>
> There is a ton of assembly source code. Converting it from one syntax
> to another would be a great deal of work - and possibly error prone.
> As of two years ago there was not a tool to do the conversion automatically.
It would be easier to convert the source from MASM to NASM. Both use
intel syntax. NASM is free and its source code available. This is a list
of the object formats it supports.
* bin flat-form binary files (e.g. DOS .COM, .SYS)
aout Linux a.out object files
aoutb NetBSD/FreeBSD a.out object files
coff COFF (i386) object files (e.g. DJGPP for DOS)
elf ELF32 (i386) object files (e.g. Linux)
as86 Linux as86 (bin86 version 0.3) object files
obj MS-DOS 16-bit/32-bit OMF object files
win32 Microsoft Win32 (i386) object files
oldrdf Relocatable Dynamic Object File Format v1.1
rdf Relocatable Dynamic Object File Format v2.0
ieee IEEE-695 (LADsoft variant) object file format
The NASM homepage is http://www.web-sites.co.uk/nasm/index.html
There are several programs that can convert between intel and gas, but
usually require some help in converting. One that can convert between
NASM or MASM or Gas is at http://hermes.terminal.at/intel2gas/
Though if the object file is available and can be converted, I don't
see the advantage of compiling from the source.
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers