From:	Mark Blain <mblain AT wizvax DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: MASM coff images
Date:	Sun, 28 May 2000 18:03:32 -0400
Message-ID:	<ut33jsk2dkps46k4dc6tatr25g247p0ko6@4ax.com>
References:	<04039b30 DOT 28983095 AT usw-ex0101-008 DOT remarq DOT com>
X-Newsreader:	Forte Agent 1.8/32.548
MIME-Version:	1.0
NNTP-Posting-Host:	ts2p31.wizvax.net
X-Original-NNTP-Posting-Host:	ts2p31.wizvax.net
X-Trace:	28 May 2000 18:05:59 -0400, ts2p31.wizvax.net
Lines:	24
XPident:	wilson
X-Original-NNTP-Posting-Host:	199.181.141.3
XPident:	news
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

On Sat, 27 May 2000 09:59:08 -0700, Dogansmoobs
<dogansmoobsNOdoSPAM AT hotmail DOT com DOT invalid> wrote:

>I have a lot of code written a while ago when I used MASM that I
>would not like to lose.  I read that you could compile a MASM
>source to a coff image, which I figured out how to do.  I try to
>write a C program to call the asm functions, but no matter what
>I try, I still get undefined refrence to [function].
>....
I'm far from an .asm expert, but I just downloaded the latest beta of
FreeDOS and read the passage below in the docs for NASM .   Maybe it'll be
of interest.
  
"(NASM's) win32 output format generates Microsoft Win32 object files,
suitable for passing to Microsoft linkers... Note that although Microsoft
says that Win32 object files follow the COFF (Common Object File Format)
standard, the object files produced by Microsoft Win32 compilers are not
compatible with COFF linkers such as DJGPP's, and vice versa. This is due
to a difference of opinion over the precise semantics of PC-relative
relocations. To produce COFF files suitable for DJGPP, use NASM's coff
output format; conversely, the coff format does not produce object files
that Win32 linkers can generate correct output from."
http://www.web-sites.co.uk/nasm/

- Raw text -