Xref: news2.mv.net comp.os.msdos.djgpp:1217
Newsgroups: comp.os.msdos.djgpp
From: jhaide AT btrvtech DOT com (Janos Haide)
Subject: Re: Help: Converting TASM to AT&T GAS
Message-ID: <DMrwKI.4HD@BtrvTech.Com>
Sender: news AT BtrvTech DOT Com (0000-USENET News(0000))
Nntp-Posting-Host: jhaide.btrieve.com
Organization: DNRC
References: <Pine DOT ULT DOT 3 DOT 91 DOT 960213111331 DOT 15055A-100000 AT rowan>
Date: Wed, 14 Feb 1996 16:02:40 GMT
Lines: 42
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <Pine DOT ULT DOT 3 DOT 91 DOT 960213111331 DOT 15055A-100000 AT rowan>,
D. Hibbs <mtx064 AT coventry DOT ac DOT uk> wrote:
>On 9 Feb 1996, Robert Gorichanaz wrote:
>
>> 'ello
>> 
>> I have some assembly code written for Borland's TASM in IDEAL mode and
>> I need some pointers in converting it over to DJGPP/GNU assembly.
>> 

Two solutions come to mind (both of which require other C/C++ packages) 
'sokay though, we all are compiler freaks (*).

(a) Keep using TASM to produce .obj files and then use watcom's
        
        wdisasm -au

    to produce files in AT&T syntax and recompile those with djasm

(b) Get EMX (Eberhard Mattes' extender package for OS/2 and DOS) and check out
    the utility called

        emxaout

    which takes OMF objects (built with TASM, .386 / .flat) and converts them
    into a.out format. That should work. 

Hope this was of help,
Janos

(*)  I got (and use): Watcom C/C++; Borland C/C++ (3.x, 4.x, OS/2); EMX; 
     DJGPP; IBM VisualAge C++. (**) No compilers from MS, though.

(**) These are all full installs. ZIP drives rule. <grin>
 
    So, do I qualify as a compiler package freak?
--
 "I just want to say that if someone gave me a Macintosh, I'd open it up,
  throw away the insides, and use the empty shell for a birdhouse. Rather
  have sparrows than Apples." -- wharfie (on austin.general in mid '93)