On 2017-07-13 09:36, bz0...@tirol.com wrote: >> On 2017-07-12 11:15, bz0...@tirol.com wrote: >>> gcc does not recognize some functions from pthread.h if option -std=c11 >>> is used: >> >> Exactly, and the same happens with glibc. When you use -std=c*, that means >> you are declaring strict ISO C, and all extensions are disabled by default >> unless explicitly enabled (e.g. with -D_POSIX_C_SOURCE=200112L). >> >> If you are not compatible with ISO C, then you should be using >> -std=gnu* instead.
> Many thanks for the info, Yaakov. Accoring to the manual -std determines the > language standard and c11 means ISO C11, the 2011 revision of the ISO C > standard. Howevery, I find no restriction on POSIX in ISO/IEC 9899:2011. So > why should -std=c11 have an influence on Pthreads? Am I missing something? ISO/IEC 9899 specifies the features and facilities that shall or may be provided by all standard conforming freestanding or hosted implementations. It considers proposals from stakeholders for new language and library features based on available implementations. Threading is optional in standards conforming implementations: conforming programs must compile cleanly if the feature is not available, and use only the facilities declared in threads.h. See https://en.wikipedia.org/wiki/C11_(C_standard_revision)#Optional_features POSIX specifies common features and facilities that shall or may be provided by one class of hosted implementations, with additional requirements to those specified for standard conforming implementations. POSIX does not provide threads.h but does provide pthreads.h, so you have a choice, depending on whether you want to be strictly conforming or support POSIX. See or search for Linux glibc man 7 feature_test_macros for more info about macros and values. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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
