From:	cgf AT bbc DOT com (Christopher Faylor)
Subject:	Re: Adding coff.h header
2 Feb 1998 16:14:14 -0800 :
Message-ID:	<EnrwHq.AC4.cygnus.cygwin32.developers@bbc.com>
References:	<199802022050 DOT MAA22907 AT skaro DOT cygnus DOT com>
Reply-To:	cygwin32-developers AT cygnus DOT com
To:	cygwin32-developers AT cygnus DOT com

In article <199802022210 DOT RAA12269 AT subrogation DOT cygnus DOT com>,
Ian Lance Taylor  <cygwin32-developers AT cygnus DOT com> wrote:
>   From: Geoffrey Noer <noer AT cygnus DOT com>
>   Date: Mon, 2 Feb 1998 12:50:33 -0800 (PST)
>
>   I already have Sergey's opinion.  Do others agree?  Should this be
>   added as winsup/include/coff.h (assuming copyright status is such
>   that I can add it).
>
>This is basically a rearrangement of information which is already in
>include/coff, so the copyright status should be fine.
>
>I no longer have access to a COFF based native system, but I don't
>recall a coff.h header file.  I recall header files like <a.out.h>,
><sym.h> and <reloc.h>.

That's right.  Digital UNIX (a COFF system) has all of these files and
more.  This is what is included in a.out.h:

	#include <filehdr.h>
	#include <aouthdr.h>
	#include <scnhdr.h>
	#include <reloc.h>
	#include <syms.h>       /* includes storclass.h */

I think a.out.h is pretty standard.  Possibly we could get by with just
calling it a.out.h.
-- 
http://www.bbc.com/	cgf AT bbc DOT com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."

- Raw text -