From:	gbcshady AT my-deja DOT com
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: objcopy problems.
Date:	Mon, 12 Feb 2001 15:30:08 GMT
Organization:	Deja.com
Lines:	34
Message-ID:	<968vhj$55q$1@nnrp1.deja.com>
References:	<966tp1$i25$1 AT nnrp1 DOT deja DOT com> <968k55$plu$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
NNTP-Posting-Host:	64.132.59.82
X-Article-Creation-Date:	Mon Feb 12 15:30:08 2001 GMT
X-Http-User-Agent:	Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
X-Http-Proxy:	1.1 x63.deja.com:80 (Squid/1.1.22) for client 64.132.59.82
X-MyDeja-Info:	XMYDJUIDgbcshady
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <968k55$plu$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>,
  Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> wrote:

> What do you get for:
>
> 	nm output.o
>
> I.e.: is the .o file still intact, before you added it to the archive?
> What happens if you instruct 'ar' to not create a symbol table for the
> archive (no 's' option)?

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*, and I get it when creating ARM ELF object
files:

$ 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

So I maintain that there is something broken within objcopy.

Any ideas as to what it is that could be broken, or any possible
workarounds?  I'd like to circumvent the problem, if at all possible,
before I start hacking at the objcopy source. =/

Regards,
Matthew Conte.


Sent via Deja.com
http://www.deja.com/

- Raw text -