Date: Mon, 12 Feb 2001 21:53:16 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp AT delorie DOT com Message-Id: <1659-Mon12Feb2001215316+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 In-reply-to: <968hgl$pkp$1@nnrp1.deja.com> (gbcshady@my-deja.com) Subject: Re: objcopy problems. References: <968hgl$pkp$1 AT nnrp1 DOT deja DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: gbcshady AT my-deja DOT com > Newsgroups: comp.os.msdos.djgpp > Date: Mon, 12 Feb 2001 11:30:28 GMT > > > How exactly did you produce the binary file? With what tool(s) and > > what command line(s)? > > It's immaterial -- it's just a raw binary file. It might not be immaterial. When you ask for help, it's usually a good idea to supply information that people who are trying to help you request. > Something is very broken with the interaction of objcopy/ar/nm. It > almost looks like they are built with different versions of the bfd > library, or one of them really doesn't support coff-go32 like it says > it does. This is impossible. They are all built from the same version of Binutils. You could run each one of the utilities on a DJGPP object file and see if any one of them fails to recognize the file. > The format I should be using is coff-go32, right? That's the only object format produced by DJGPP (coff-go32-exe is identical to it, modulo the stub issue).