Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Fri, 26 Jan 2001 11:59:08 -0500
Message-Id: <200101261659.LAA07056@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT cygwin DOT com
In-reply-to: <20010126111932.A20139@redhat.com> (message from Christopher
	Faylor on Fri, 26 Jan 2001 11:19:32 -0500)
Subject: Re: [hjl AT valinux DOT com: Re: A PE patch.]
References: <200101242033 DOT PAA16287 AT envy DOT delorie DOT com> <20010126003903 DOT C14969 AT redhat DOT com> <200101261426 DOT JAA05790 AT envy DOT delorie DOT com> <20010126111932 DOT A20139 AT redhat DOT com>


> >No.  Think "cross compiler".
> 
> A grep of "include <" in bfd seems to unearth a number of system includes.
> Are you saying that you have to duplicate every header that you need to
> use in bfd?  I don't see the reason for that, since the headers already
> exist in the tree.

No, just the ones that define structures needed to read/write objects
and executables.  Plus, the bfd definitions use char[] to avoid
structure packing problems and alignment.

And, the win32 headers do *not* exist in the binutils tree.  They'd
only exist in a merged tree like you use.