Mailing-List:	contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT cygwin DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT cygwin DOT com>
List-Help:	<mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
Message-ID:	<3C0E0C4C.73A1750D@syntrex.com>
Date:	Wed, 05 Dec 2001 13:00:12 +0100
From:	Pavel Tsekov <ptsekov AT syntrex DOT com>
X-Mailer:	Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin-apps AT cygwin DOT com
Subject:	string.h vs string.h usage

Any opinions on this topic ?

-------- Original Message --------
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Message-ID: <3C0E04DC DOT 224452C9 AT syntrex DOT com>
Date: Wed, 05 Dec 2001 12:28:28 +0100
From: Pavel Tsekov <ptsekov AT syntrex DOT com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
Subject: Re: linux -> cygwin cross compiler
References: <3C0CC8AA DOT 5463D0B3 AT syntrex DOT com>
<083a01c17cc3$b85798e0$0200a8c0 AT lifelesswks>
<3C0CDB6E DOT 96A3EE57 AT syntrex DOT com>
<086f01c17cce$c9bdf060$0200a8c0 AT lifelesswks>
<3C0CDBF6 DOT BEEFD8A6 AT syntrex DOT com> <3C0CDC9B DOT 24D4D813 AT syntrex DOT com>
<088001c17ccf$8d13e3d0$02 <03fe01c17d7f$1627a4e0$0200a8c0 AT lifelesswks>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit

> 
> > Btw one thing - I've found many #include <strings.h> in
> > the latest sources - shouldn't this be changed to #include
> > <string.h> ? mingw doesnt have strings.h. Btw It seems that
> > if you have string.h you dont need strings.h (I'm under
> > the impression that string.h include strings.h on linux)
> >
> > Does this sound reasonable ?
> 
> I dunno. Setup builds with -mno-cygwin with FAIK uses all mingw headers,
> so I don't know whether that is needed or not. Thats probably better
> asked on-list :}.
> 

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

- Raw text -