From: "Lawrence Rust" <lvr AT NOsoftSPsystemAM DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
References: <Dchc6.1810$Jx5 DOT 65021 AT news2-win DOT server DOT ntlworld DOT com> <5137-Fri26Jan2001195157+0200-eliz AT is DOT elta DOT co DOT il>
Subject: Re: Using MASM with DJGPP
Lines: 16
Organization: Software Systems
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <h9lc6.2458$Jx5.86397@news2-win.server.ntlworld.com>
Date: Fri, 26 Jan 2001 20:29:36 -0000
NNTP-Posting-Host: 62.253.152.242
X-Complaints-To: abuse AT ntlworld DOT com
X-Trace: news2-win.server.ntlworld.com 980541133 62.253.152.242 (Fri, 26 Jan 2001 20:32:13 GMT)
NNTP-Posting-Date: Fri, 26 Jan 2001 20:32:13 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> Perhaps you should have tried the latest Gas's option which lets it
> accept Intel-style ASM code.  Section 17.2 of the FAQ says this, so I
> wonder why didn't you try that.  Perhaps you had a stale version of
> the FAQ?

I did try Gas (I did read about that in the FAQ) but it failed on the macros
and other directives.  MASM is MASM, even Borlands TASM has the quirks mode
to try and match it.

What I don' understand is why ld and M$ link disagree on COFF relocations.
It was originally a unix spec with i386 format being defined by M$.  Oh well
it just adds to the interest I suppose.

-- Lawrence Rust