From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: objcopy problems.
Date: 12 Feb 2001 16:54:55 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 31
Message-ID: <9694gv$j17$1@nets3.rz.RWTH-Aachen.DE>
References: <966tp1$i25$1 AT nnrp1 DOT deja DOT com> <968k55$plu$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <968vhj$55q$1 AT nnrp1 DOT deja DOT com>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 981996895 19495 137.226.32.75 (12 Feb 2001 16:54:55 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 12 Feb 2001 16:54:55 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

gbcshady AT my-deja DOT com wrote:

[...]
> No, the .o file seems to be corrupt from the start.  Here is what my
> command line and output look like.  Note that the message about unknown
> architecture is *normal*, 

I have my doubts regarding this. Whenever your input or output format
is 'binary', I think you're supposed to also specify a target
architecture and/or section names.  Without that, objcopy might have a
hard time correctly interpreting even a simple binary file without any
file structure or symbols --- thus the warning.

> $ objcopy -v -I binary -O coff-go32 input.bin output.o
>> copy from input.bin(binary) to output.o(coff-go32)
>> Warning: Output file cannot represent architecture UNKNOWN!
> $ nm output.o
>> c:/djgpp/bin/nm.exe: output.o: File format not recognized

Another useful test could be:

	objdump -x -d output.o

to output (almost) everything about output.o that BFD can determine.

Further details might better be directed at the binutils mailing list,
or at least the djgpp-workers mailing list, where all the experts
porting GCC and binutils to DJGPP are listening.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.