Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date:	Wed, 31 May 2000 13:54:31 -0400
Message-Id:	<200005311754.NAA26524@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	earnie_boyd AT yahoo DOT com
CC:	cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to:	<20000531170303.3295.qmail@web122.yahoomail.com> (message from
	Earnie Boyd on Wed, 31 May 2000 10:03:03 -0700 (PDT))
Subject:	Re: libiberty and standard includes.
References:	<20000531170303 DOT 3295 DOT qmail AT web122 DOT yahoomail DOT com>

> However, shouldn't the build of libiberty ignore the standard
> include directory and use the newlib version during the build
> process?

I've already submitted a change to libiberty to handle this bug.  I'm
awaiting approval.

- Raw text -