Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3C0E11E8.4153D837@syntrex.com> Date: Wed, 05 Dec 2001 13:24:08 +0100 From: Pavel Tsekov X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: CA List Subject: Re: string.h vs string.h usage References: <3C0E0C4C DOT 73A1750D AT syntrex DOT com> <3C0E1075 DOT AE2A98C7 AT yahoo DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Earnie Boyd wrote: > > > Yes but it gives various include paths from cygwin build and newlib > > build - > > this means that you compile only in this environment (i.e. winsup env). > > If you > > try only mingw it wont work :) > > > > However I've fixed that for me locally > > There should be nothing to fix. If there is then you've done something > wrong in the setup or building the program. Using -mno-cygwin should > only give you MinGW headers and never the Cygwin headers. The only way > I can think of that this would happen is if you also added a > -I/usr/include to the gcc build options or if you modified the gcc > source and rebuilt it yourself. By fixing I mean replacing strings.h with string.h :) Btw it doesnt pick only mingw headers - check the makefile - i uses the option -isystem and supplies a bunch of include header file dirs from newlib and winsup.