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 15:21:38 +0300 From: egor duda X-Mailer: The Bat! (v1.53 RC/4) Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <15915798356.20011205152138@logos-m.ru> To: Pavel Tsekov CC: cygwin-apps AT cygwin DOT com Subject: Re: string.h vs string.h usage In-Reply-To: <3C0E0C4C.73A1750D@syntrex.com> References: <3C0E0C4C DOT 73A1750D AT syntrex DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Wednesday, 05 December, 2001 Pavel Tsekov ptsekov AT syntrex DOT com wrote: SUSv2 mandates both and mingw declares strcasecmp() in while SUSv2 says it should be in i believe mingw headers should be fixed/updated. PT> Any opinions on this topic ? PT> -------- Original Message -------- >> > Btw one thing - I've found many #include in >> > the latest sources - shouldn't this be changed to #include >> > ? 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 :}. >> PT> Yes but it gives various include paths from cygwin build and newlib PT> build - this means that you compile only in this environment (i.e. winsup env). PT> If you try only mingw it wont work :) PT> However I've fixed that for me locally Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19