Date:	Wed, 22 Mar 2000 10:34:41 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	ESD <esd AT deakin DOT edu DOT au>
cc:	djgpp AT delorie DOT com
Subject:	Re: a.out output
In-Reply-To:	<38D7EE8D.127AF606@deakin.edu.au>
Message-ID:	<Pine.SUN.3.91.1000322103344.17945N@is>
MIME-Version:	1.0
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

On Wed, 22 Mar 2000, ESD wrote:

> I had actually tried objcopy, but the files are still not quite what I need.
> When OD is run over the output from DJGPP/objcopy and compared with the same
> file produced by a pure a.out Intel compiler (on VSTa) there are some
> differences. It will link OK, but doesn't do anything that I can tell, eg
> output to the screen.

What does it use to write to the screen?  If it uses direct screen
writes, then the way this was implemented in DJGPP v1.x will indeed
not work in the DPMI environment (it didn't work in the DPMI
environment even in v1.x).

> Originally VSTa was built with an earlier version of DJGPP, one that is/was
> an a.out compiler, and I was hoping that V2 still could.

AFAIK, the support for a.out in v2 is not different from v1.x.  But
don't you have sources for those modules, to recompile them with v2?

> Is the version 1 on the djgpp.com web site what I am after, ie does it
> produce a.out?

It produces COFF by default, but you should be able to use non-default
switches (and prehaps change the linker script) to produce a.out.

> Does it handle long files names under windows?

No, v1.x never supported long file names (this support was introduced
with v2.0).  The reason is simple: Windows 95 did not exist when v1.x
was developed.

- Raw text -