This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: string.h vs string.h usage


Hi!

Wednesday, 05 December, 2001 Pavel Tsekov ptsekov@syntrex.com wrote:

SUSv2 mandates both <strings.h> and <string.h>

mingw declares strcasecmp() in <string.h> while SUSv2 says it should
be in <strings.h>

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 <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 :}.
>> 

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@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]