This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: clang copy of limits.h misses NAME_MAX
- From: Ismail Donmez <ismail at i10z dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 17 Mar 2016 15:42:46 +0200
- Subject: Re: clang copy of limits.h misses NAME_MAX
- Authentication-results: sourceware.org; auth=none
- References: <56EAAD1B dot 4030107 at t-online dot de> <CAFo71_5=CPzstQq8Vd3sDa6yGVDArp9oE2p1eeu-hqQbt95+nA at mail dot gmail dot com> <56EAB2A8 dot 4010400 at gmail dot com>
On Thu, Mar 17, 2016 at 3:35 PM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
> it seems to prefer gcc headers
>
> # 1 "/usr/bin/../lib/clang/3.7.1/include/limits.h" 1 3 4
> # 37 "/usr/bin/../lib/clang/3.7.1/include/limits.h" 3 4
> # 1 "/usr/lib/gcc/x86_64-pc-cygwin/5.3.0/include/limits.h" 1 3 4
> # 38 "/usr/bin/../lib/clang/3.7.1/include/limits.h" 2 3 4
> # 17 "/usr/include/sys/dirent.h" 2 3 4
I am looking at clang 3.7 headers on Linux so this might be not 100%
same on Cygwin but, clang's limits.h has this on top:
/* The system's limits.h may, in turn, try to #include_next GCC's limits.h.
Avert this #include_next madness. */
#if defined __GNUC__ && !defined _GCC_LIMITS_H_
#define _GCC_LIMITS_H_
#endif
which should prevent including gcc's own limits.h but looks like it doesn't.
ismail
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple