delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/07/23/02:01:20

Date: Tue, 23 Jul 1996 08:55:12 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: j DOT aldrich6 AT genie DOT com
Cc: ericong AT pacific DOT net DOT sg, djgpp AT delorie DOT com
Subject: Re: [Q] Difference in the Coff format generated by Masm 6.1 ?
In-Reply-To: <199607230249.AA293760168@relay1.geis.com>
Message-Id: <Pine.SUN.3.91.960723084714.9913J-100000@is>
Mime-Version: 1.0

On Tue, 23 Jul 1996 j DOT aldrich6 AT genie DOT com wrote:

> >I can't use my coff obj file generated MASM 6.11 in Djgpp. Is there any
> >difference in both
> >coff in MASM and djgpp ?
> 
> There is a substantial difference.  First, your MASM must be generating
> 32-bit, flat address model code to even have a chance to work with
> DJGPP.  Then I believe you have to use a conversion program to
> fix the formatting.  COFF is not a universal standard; each compiler
> does things anywhere from slightly to totally differently.  Look in the
> FAQ (faq201b.zip) for some hints.

MASM 6.11 has an option that makes it generate COFF files (as the FAQ
explains).  I believe that is what Eric Ong was talking about. 

The flat address space issue is probably the real problem.

Eric, it would also help if you've actually said what are the problems 
that you see when you try using the output of MASM with DJGPP.  Does the 
linker complain?  If so, what is the error message(s)?  Does the program 
link, but crash at runtime?  If so, post the crash stack trace.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019