|COFF and byte ordering firstname.lastname@example.org (Chris Eich) (1992-06-25)|
|Re: COFF and byte ordering email@example.com (1992-06-26)|
|Re: COFF and byte ordering firstname.lastname@example.org (Chris Eich) (1992-06-26)|
|Re: COFF and byte ordering email@example.com (Chris Eich) (1992-07-01)|
|From:||Chris Eich <firstname.lastname@example.org>|
|Date:||Wed, 1 Jul 1992 17:37:37 GMT|
I had written:
One person suggested conv(1), which seems to be BSDish ....
I got email correcting me; conv is from AT&T and specifically deals with
other-endian COFF files. (The name "conv" is much too generic for such a
program; I'd rather it be "coffconv". But then, I'm not AT&T. See Figure
So it looks like the summary is:
1. The tools themselves may recognize and swap other-endian COFF files.
2. Else if you have "conv" (is it standard in SVR3 or 4?), use it.
3. Otherwise, the GNU binutils seem to be able to do the job.
Return to the
Search the comp.compilers archives again.