Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 14 Apr 2003 00:49:25 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: C libraries Message-ID: <20030414044925.GA24720@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Sun, Apr 13, 2003 at 10:18:17PM -0700, Martin Gainty wrote: >My cygwin stdio.h is in %HOME%/usr/include >assuming you are compiling from HOME folder you can >SET INCLUDE=/usr/include >make >and you should be good to go.. No. No. You don't have to set an INCLUDE environment variable for gcc to work properly. /usr/include should be in /usr/include. HOME has nothing to do with it. To debug this problem, go to http://cygwin.com/bugs.html and follow the instructions there. At the very least, that will give us some idea of your environment. That page also gives you some minimal guidance in reporting bugs. The two most useful bits of advice would be "provide details" (you didn't provide the gcc command line that is failing) and provide cygcheck output. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/