Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Tue, 27 Aug 2002 20:31:22 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: A quick note on Message-ID: <20020828003122.GL16631@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <000201c24e27$ffa0bb10$6132bc3e AT BABEL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000201c24e27$ffa0bb10$6132bc3e@BABEL> User-Agent: Mutt/1.3.23.1i On Wed, Aug 28, 2002 at 12:52:14AM +0100, Conrad Scott wrote: >The include file is causing problems with cygwin >builds. Um, what newlib.h include file? I'm obviously building cygwin with gcc 3.2 with no problem on both linux and windows. I don't have a newlib.h file in my build area and I don't see it installed anywhere. I also don't see it referenced by anything in winsup or newlib. Wait a minute. pause cvs update shows that there is a new file called newlib.h that was introduced *today*. Hmm. This is one of the reasons that I'm getting sick of our dependency on newlib. I've asked that cygwin be taken into account when making changes like this but, the last I heard, the newlib guys were stalled trying to accommodate my request since the two year old gcc cross compiler that they insist on using is no longer able to build cygwin. It's easy enough to add another include path to cygwin but I'm not sure that I want to do that. I think, instead, I'm going to start thinking about how we can eliminate our dependency on newlib. In the meantime, I've checked in an empty "newlib.h" file into the winsup/cygwin. That should allow things to build, at least. cgf