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 Date: Wed, 5 Dec 2001 08:26:58 -0500 From: Christopher Faylor To: cygwin-Apps AT cygwin DOT com Subject: Re: string.h vs string.h usage Message-ID: <20011205132658.GA17608@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-Apps AT cygwin DOT com References: <3C0E0C4C DOT 73A1750D AT syntrex DOT com> <3C0E1075 DOT AE2A98C7 AT yahoo DOT com> <3C0E11E8 DOT 4153D837 AT syntrex DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C0E11E8.4153D837@syntrex.com> User-Agent: Mutt/1.3.23.1i On Wed, Dec 05, 2001 at 01:24:08PM +0100, Pavel Tsekov wrote: >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. Well, then, that's the problem isn't it? Perverting mingw's header files is not the solution. cgf