X-Authentication-Warning: larry.ztnet.com: Host cm-24-25-151-140.nycap.rr.com [24.25.151.140] claimed to be shady
Message-ID: <000901c097cf$691ff3a0$8c971918@nycap.rr.com>
From: "Matthew Conte" <zeus AT nofrendo DOT org>
To: <djgpp-workers AT delorie DOT com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010215161352 DOT 29378A-100000 AT is>
Subject: Re: possible objcopy problem.
Date: Thu, 15 Feb 2001 23:17:42 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Reply-To: djgpp-workers AT delorie DOT com

From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>

> First, did you try DJGPP's bin2h utility?  It is documented in the
> utils.info manual, and might be just what you are looking for.

It's a little off from what I'm trying to do, but thanks for the pointer.

> The above error message means that the output doesn't look like a COFF
> file.  The first sign of a non-COFF file is the absence of the COFF
> magic signature at the beginning of the file, not of some section.  Do
> you see the COFF signature in output.o?

No, no I don't.  The first two bytes are not $014c, they are $0000.  That's
a Bad Thing.  And what do you know, changing them to the correct COFF magic
number makes everything work correctly.

This same problem also happens with sparC and elf32-i386.  I have posted on
the binutils mailing list about this, but I haven't gotten any response yet.
Eli, do you have a "hotter" connection into binutils development that could
raise interest about this bug?

Thanks for the help,
Matthew.