Message-ID: <38D7EE8D.127AF606@deakin.edu.au> From: ESD X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: Re: a.out output References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 28 Date: Wed, 22 Mar 2000 08:50:05 +1100 NNTP-Posting-Host: 128.184.83.51 X-Trace: news.deakin.edu.au 953675400 128.184.83.51 (Wed, 22 Mar 2000 08:50:00 EST) NNTP-Posting-Date: Wed, 22 Mar 2000 08:50:00 EST Organization: Deakin University, Victoria, Australia To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Thanks Eli, and forgive my ramblings but frustration has a way of preciptitating wierdness... 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. It will link OK, but doesn't do anything that I can tell, eg output to the screen. I have in the past successfully produced executables on a cross-compiler on a Solaris/Sparc system, (with considerable fiddling arround), but I was hoping to be able to do it under Windows, with long file names! Originally VSTa was built with an earlier version of DJGPP, one that is/was an a.out compiler, and I was hoping that V2 still could. Is the version 1 on the djgpp.com web site what I am after, ie does it produce a.ou? Does it handle long files names under windows? Which bits do I need? > > Not really helpful, not even with a smiley... > > To Eric: you can try using the objcopy utility (it's part of Binutils) to > convert COFF files into a.out format. The DJGPP port of Binutils knows > about a.out format, among others. > > Note that some information may be lost when you convert to a.out, because > it doesn't support all the info that COFF includes.