DO NOT REPLY [Bug 14612] New: - GCCDefs clashes with cygwin's string.h for stricmp and strnicmp

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14612>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14612

GCCDefs clashes with cygwin's string.h for stricmp and strnicmp

           Summary: GCCDefs clashes with cygwin's string.h for stricmp and
                    strnicmp
           Product: Xerces-C++
           Version: 2.1.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Build
        AssignedTo: xerces-c-dev@xml.apache.org
        ReportedBy: abraham@backus.com


After submitting a test package for cygwin to the cygwin-apps list for review, 
one of the reviewers, Gareth Pearce (tilps@hotmail.com), discovered issues at 
runtime.

It turns out that cygwin's string.h defines stricmp and strnicmp as C macros to 
strcasecmp and strncasecmp respectively.  So in GCCDefs.cpp, the method stricmp 
being defined is actually defining strcasecmp after the preprocessor is 
finished with it.  The body of this method is simply a call to the method 
strcasecmp, so it ends up being infinitely recursive.

Exists in 2.1.0 and in current cvs.  I'm attaching a patch to fix this.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org