search for: __has_include

...figureLog. I made it private, FWIW. > > Please provide a link. I can not find it because it is private. I copied it to a public paste called ConfigureLogPublic at http://pastebin.com/yaLHmmGk. > > Anyway, attached is a patch that should allow old clangs that don't > implement __has_include. Please test. Thanks ! If not implementing __has_include does not keep the clang package from working correctly, why would it be part of the "configure" script ?

...te called ConfigureLogPublic at > http://pastebin.com/yaLHmmGk. I see that this clang has problems with parsing unwind.h. I don't understand how does it manage to compile LLVM/Clang. > >> Anyway, attached is a patch that should allow old clangs that don't >> implement __has_include. Please test. >> > > Thanks ! If not implementing __has_include does not keep the clang package > from working correctly, why would it be part of the "configure" script ? > Sorry, I did not quite get it. Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i...

...at 3:32 AM, Edward Diener <eldlistmailingz at tropicsoft.com> wrote: > It is on pastebin and is called ConfigureLog. I made it private, FWIW. Please provide a link. I can not find it because it is private. Anyway, attached is a patch that should allow old clangs that don't implement __has_include. Please test. Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/ -------------- next part -------------- A non-text attachment was scrubbed... Name: dont-reject-clang-without-has-i...

...>> >> It looks to me that clang 2.8-14 does indeed find the necessary header >> files. Yet you are rejecting it. Also it did build clang successfully before >> your update. > > Can you pastebin the config.log file, please? (I think that clang 2.8 > did not support __has_include that I used in the test, but I need the > log file to check that it indeed caused the problem.) It is on pastebin and is called ConfigureLog. I made it private, FWIW.

How can I tell at compile time through predefined macros whether libc++ includes/supports the C++14 header file shared_mutex ? Given that I have identified that libc++ is being used, will this work ? : #if __cplusplus >= 201402 // Header file shared_mutex supported #endif or do I need to check something else ?

...> End of search list." > > It looks to me that clang 2.8-14 does indeed find the necessary header > files. Yet you are rejecting it. Also it did build clang successfully before > your update. Can you pastebin the config.log file, please? (I think that clang 2.8 did not support __has_include that I used in the test, but I need the log file to check that it indeed caused the problem.) Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/

On 01/09/2013 10:37 AM, Dmitri Gribenko wrote: > On Tue, Jan 8, 2013 at 8:43 AM, Edward Diener > <eldlistmailingz at tropicsoft.com> wrote: >> After applying your patch on Mageia 2 and invoking llvm's configure: >> >> Using clang 3.0 I get: >> >> "checking whether clang works... no >> configure: error: Selected compiler could not find or

...late template parameter > - Nested namespace definition > - Attributes for namespaces and enumerators > - u8 character literals > - Allow constant evaluation for all non-type template arguments > - Fold Expressions > - Unary fold expressions and empty parameter packs > - __has_include in preprocessor conditional > - Differing begin and end types in range-based for\ > > From: https://en.cppreference.com/w/cpp/compiler_support > <https://en.cppreference.com/w/cpp/compiler_support> > > The only thing that’s really nice are fold expressions, and I hope >...

...th no message - typename in a template template parameter - Nested namespace definition - Attributes for namespaces and enumerators - u8 character literals - Allow constant evaluation for all non-type template arguments - Fold Expressions - Unary fold expressions and empty parameter packs - __has_include in preprocessor conditional - Differing begin and end types in range-based for\ From: https://en.cppreference.com/w/cpp/compiler_support <https://en.cppreference.com/w/cpp/compiler_support> The only thing that’s really nice are fold expressions, and I hope they’re not buggy in GCC 6. Othe...

...late template parameter > - Nested namespace definition > - Attributes for namespaces and enumerators > - u8 character literals > - Allow constant evaluation for all non-type template arguments > - Fold Expressions > - Unary fold expressions and empty parameter packs > - __has_include in preprocessor conditional > - Differing begin and end types in range-based for\ > > From: https://en.cppreference.com/w/cpp/compiler_support > > The only thing that’s really nice are fold expressions, and I hope they’re > not buggy in GCC 6. > > Otherwise the list is miss...

...th no message - typename in a template template parameter - Nested namespace definition - Attributes for namespaces and enumerators - u8 character literals - Allow constant evaluation for all non-type template arguments - Fold Expressions - Unary fold expressions and empty parameter packs - __has_include in preprocessor conditional - Differing begin and end types in range-based for\ From: https://en.cppreference.com/w/cpp/compiler_support The only thing that’s really nice are fold expressions, and I hope they’re not buggy in GCC 6. Otherwise the list is missing a good amount for C++17 language...

...- Nested namespace definition > > - Attributes for namespaces and enumerators > > - u8 character literals > > - Allow constant evaluation for all non-type template arguments > > - Fold Expressions > > - Unary fold expressions and empty parameter packs > > - __has_include in preprocessor conditional > > - Differing begin and end types in range-based for\ > > > > From: https://en.cppreference.com/w/cpp/compiler_support > > > > The only thing that’s really nice are fold expressions, and I hope they’re > not buggy in GCC 6. > > &...

...- Attributes for namespaces and enumerators >> >> - u8 character literals >> >> - Allow constant evaluation for all non-type template arguments >> >> - Fold Expressions >> >> - Unary fold expressions and empty parameter packs >> >> - __has_include in preprocessor conditional >> >> - Differing begin and end types in range-based for\ >> >> >> >> From: https://en.cppreference.com/w/cpp/compiler_support >> >> >> >> The only thing that’s really nice are fold expressions, and I hope they...

...- Nested namespace definition > > - Attributes for namespaces and enumerators > > - u8 character literals > > - Allow constant evaluation for all non-type template arguments > > - Fold Expressions > > - Unary fold expressions and empty parameter packs > > - __has_include in preprocessor conditional > > - Differing begin and end types in range-based for\ > > > > From: https://en.cppreference.com/w/cpp/compiler_support > > > > The only thing that’s really nice are fold expressions, and I hope they’re > not buggy in GCC 6. > > &...

If it's the only thing we can agree then I'll take it, but I just worry that 3 years from now we're going to start another 3 year discussion, so that any actual move to C++17 would end up taking double the time. Are the issues specific to C++17 additions to the standard library? What if you allow C++17 language features but not C++17 library features? I'm guessing this is too