string.h vs string.h usage

[Christopher Faylor]

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