From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: a.out output
Date: 22 Mar 2000 13:53:58 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 25
Message-ID: <8baj9m$ncu$1@nets3.rz.RWTH-Aachen.DE>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000320182537 DOT 26722N-100000 AT is> <38D7EE8D DOT 127AF606 AT deakin DOT edu DOT au>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 953733238 23966 137.226.32.75 (22 Mar 2000 13:53:58 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 22 Mar 2000 13:53:58 GMT
User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586))
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

ESD <esd AT deakin DOT edu DOT au> 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. 

'OD' as in 'objdump', or as in 'od', the 'octal dump' tool? Only
'objdump' differences should be significant, at all. But without you
showing us a typical example of such a difference, in the first place,
there's little, if anything we can do to help you with it. We're not
psychic, after all.

> It will link OK, but doesn't do anything that I can tell, eg
> output to the screen. 

You'll have to enable and compare linker protocol output, and objdumps
of readily linked binaries, too, to check what the actual difference
is. Difference in behaviour has to come from somewhere, so differences
of the binaries and how they were reported to be generated are
important.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.