Date: Mon, 20 Mar 2000 18:28:44 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Chris Mears <chris_mears AT softhome DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: a.out output
In-Reply-To: <ecubdsc1cmkdkdlqcf4m5pldmoav9hpu0j@4ax.com>
Message-ID: <Pine.SUN.3.91.1000320182537.26722N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 20 Mar 2000, Chris Mears wrote:

> That Eric Dines <esd AT deakin DOT edu DOT au> really knows where his towel is.
> On Mon, 20 Mar 2000 20:17:03 +1100, he wrote:
> 
> >Can anyone tell me how to produce a.out binaries from DJGPP without
> >creating some sort of cross compiler please?
> 
> gcc foo.c -o a.out

Not really helpful, not even with a smiley...

To Eric: you can try using the objcopy utility (it's part of Binutils) to 
convert COFF files into a.out format.  The DJGPP port of Binutils knows 
about a.out format, among others.

Note that some information may be lost when you convert to a.out, because 
it doesn't support all the info that COFF includes.