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:19:32 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: [hjl AT valinux DOT com: Re: A PE patch.]
Message-ID:	<20010126111932.A20139@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
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>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<200101261426.JAA05790@envy.delorie.com>; from dj@delorie.com on Fri, Jan 26, 2001 at 09:26:01AM -0500

On Fri, Jan 26, 2001 at 09:26:01AM -0500, DJ Delorie wrote:
>> Shouldn't the PEI*_header stuff come from some w32api file or other?
>
>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.

cgf

- Raw text -