[CMake] Warning in CMake Git HEAD

Williams, Norman K norman-k-williams at uiowa.edu
Thu Sep 19 13:08:21 EDT 2013


It is a typo.  This is a warning generated by a very recent development
head version of CLang I built.

It looks like it was added to CMake by Andy Cedilnik in revision 9314bb;
It looks like an upstream typo that just happened never to cause a
real-world problem.
--
Kent Williams norman-k-williams at uiowa.edu






On 9/19/13 11:15 AM, "Sean McBride" <sean at rogue-research.com> wrote:

>On Thu, 19 Sep 2013 15:12:54 +0000, Williams, Norman K said:
>
>>This looks like a simple typo.  I could fix it and submit a gerrit topic,
>>but I'm busy with other stuff for the moment.
>>
>>Or is this a typo imported from CURL?
>>
>>In file included from
>>/scratch/kent/cmake/cmake/Utilities/cmcurl/http.c:99:
>>/scratch/kent/cmake/cmake/Utilities/cmcurl/parsedate.h:1:9: warning:
>>'__PARSEDATE_H' is used as a header guard here, followed
>>      by #define of a different macro [-Wheader-guard]
>>#ifndef __PARSEDATE_H
>>        ^~~~~~~~~~~~~
>>/scratch/kent/cmake/cmake/Utilities/cmcurl/parsedate.h:2:9: note:
>>'__PARSEDATEL_H' is defined here; did you mean
>>      '__PARSEDATE_H'?
>>#define __PARSEDATEL_H
>>        ^~~~~~~~~~~~~~
>>        __PARSEDATE_H
>
>Strange that my dashboard is not showing this, I'll check on that.  It
>does look like a typo.  That's 3rd party code, right?  Maybe it is fixed
>upstream?  (Also, it's illegal to start an identifier with two
>underscores.)
>
>Cheers,
>
>--
>____________________________________________________________
>Sean McBride, B. Eng                 sean at rogue-research.com
>Rogue Research                        www.rogue-research.com
>Mac Software Developer              Montréal, Québec, Canada
>
>



________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
________________________________


More information about the CMake mailing list