[config] Need some clang testing help...
Folks there are persistent bug reports relating to clang with libstdc++ not correctly detecting the std lib feature set, see https://svn.boost.org/trac/boost/ticket/7473 for a lengthy discussion on the issue, and why it's been unsolvable. Anyhow, I've just committed a tentative patch in https://github.com/boostorg/config/commit/b36566fe04a89103b7ef5569c03e3a26eb... and I'd be grateful if as many folks as possible can test this with their clang/linux/libstdc++/C++11 setups as they can. It works well for me locally, but that's only one possible clang configuration. BTW the easiest way to patch your Boost version is probably to download a replacement libstdcpp2.hpp from here: https://raw.githubusercontent.com/boostorg/config/b36566fe04a89103b7ef5569c0... Many thanks in advance, John.
On 10/05/2014 12:01 PM, John Maddock wrote:
Folks there are persistent bug reports relating to clang with libstdc++ not correctly detecting the std lib feature set, see https://svn.boost.org/trac/boost/ticket/7473 for a lengthy discussion on the issue, and why it's been unsolvable.
Anyhow, I've just committed a tentative patch in https://github.com/boostorg/config/commit/b36566fe04a89103b7ef5569c03e3a26eb... and I'd be grateful if as many folks as possible can test this with their clang/linux/libstdc++/C++11 setups as they can. It works well for me locally, but that's only one possible clang configuration.
BTW the easiest way to patch your Boost version is probably to download a replacement libstdcpp2.hpp from here: https://raw.githubusercontent.com/boostorg/config/b36566fe04a89103b7ef5569c0...
Many thanks in advance, John.
Exactly what version of clang is this and what needs to be tested ? A little more information on what you want tested would be helpful. I have clang installed on a number of Linux distros and would be glad to test with your latest config fix if I knew what you needed.
BTW the easiest way to patch your Boost version is probably to download a replacement libstdcpp2.hpp from here: https://raw.githubusercontent.com/boostorg/config/b36566fe04a89103b7ef5569c0...
Many thanks in advance, John.
Exactly what version of clang is this and what needs to be tested ? A little more information on what you want tested would be helpful.
I have clang installed on a number of Linux distros and would be glad to test with your latest config fix if I knew what you needed.
As many clang versions and libstdc++ configurations as possible - I've tested latest and greatest clang with gcc-4.8, but it needs testing with other combinations - best way to do that is to get "the crowd" to do it. Thanks, John.
On 10/6/2014 7:49 AM, John Maddock wrote:
BTW the easiest way to patch your Boost version is probably to download a replacement libstdcpp2.hpp from here: https://raw.githubusercontent.com/boostorg/config/b36566fe04a89103b7ef5569c0...
Many thanks in advance, John.
Exactly what version of clang is this and what needs to be tested ? A little more information on what you want tested would be helpful.
I have clang installed on a number of Linux distros and would be glad to test with your latest config fix if I knew what you needed.
As many clang versions and libstdc++ configurations as possible - I've tested latest and greatest clang with gcc-4.8, but it needs testing with other combinations - best way to do that is to get "the crowd" to do it.
Isn't libstdc++ the default when testing with clang ? If not, what do I have to do to use libstdc++ with clang on Linux ?
Isn't libstdc++ the default when testing with clang ? If not, what do I have to do to use libstdc++ with clang on Linux ?
Yes I believe it's the default unless you've added libc++ to your include path. If in doubt the output from config_info (config_info.output, located deep under bin.v2) will show you all could want to know. John.
On 10/6/2014 12:47 PM, John Maddock wrote:
Isn't libstdc++ the default when testing with clang ? If not, what do I have to do to use libstdc++ with clang on Linux ?
Yes I believe it's the default unless you've added libc++ to your include path. If in doubt the output from config_info (config_info.output, located deep under bin.v2) will show you all could want to know.
I tried out the latest 'develop' branch of config with both clang 3.3 and the latest clang build from source on SUSE Linux. I ran my tests for tti using clang without any problems. Should I be looking for a particular version of gcc headers/libs or libstdc++ that clang is using ?
Isn't libstdc++ the default when testing with clang ? If not, what do I have to do to use libstdc++ with clang on Linux ?
Yes I believe it's the default unless you've added libc++ to your include path. If in doubt the output from config_info (config_info.output, located deep under bin.v2) will show you all could want to know.
I tried out the latest 'develop' branch of config with both clang 3.3 and the latest clang build from source on SUSE Linux. I ran my tests for tti using clang without any problems. Should I be looking for a particular version of gcc headers/libs or libstdc++ that clang is using ?
No just whatever combinations you have available - many thanks for that, John.
On 05/10/2014 18:01, John Maddock wrote:
Folks there are persistent bug reports relating to clang with libstdc++ not correctly detecting the std lib feature set, see https://svn.boost.org/trac/boost/ticket/7473 for a lengthy discussion on the issue, and why it's been unsolvable.
Anyhow, I've just committed a tentative patch in https://github.com/boostorg/config/commit/b36566fe04a89103b7ef5569c03e3a26eb... and I'd be grateful if as many folks as possible can test this with their clang/linux/libstdc++/C++11 setups as they can. It works well for me locally, but that's only one possible clang configuration.
BTW the easiest way to patch your Boost version is probably to download a replacement libstdcpp2.hpp from here: https://raw.githubusercontent.com/boostorg/config/b36566fe04a89103b7ef5569c0...
Why use the GCC version numbers as a base instead of the libstdc++ version numbers? (__GLIBCXX__) They're probably more reliable than checking for existence of an include.
On 06/10/2014 01:05, Mathias Gaunard wrote:
On 05/10/2014 18:01, John Maddock wrote:
Folks there are persistent bug reports relating to clang with libstdc++ not correctly detecting the std lib feature set, see https://svn.boost.org/trac/boost/ticket/7473 for a lengthy discussion on the issue, and why it's been unsolvable.
Anyhow, I've just committed a tentative patch in https://github.com/boostorg/config/commit/b36566fe04a89103b7ef5569c03e3a26eb...
and I'd be grateful if as many folks as possible can test this with their clang/linux/libstdc++/C++11 setups as they can. It works well for me locally, but that's only one possible clang configuration.
BTW the easiest way to patch your Boost version is probably to download a replacement libstdcpp2.hpp from here: https://raw.githubusercontent.com/boostorg/config/b36566fe04a89103b7ef5569c0...
Why use the GCC version numbers as a base instead of the libstdc++ version numbers? (__GLIBCXX__) They're probably more reliable than checking for existence of an include.
My bad, hadn't read the ticket. __GLIBCXX__ apparently has problems because of GCC bugfix releases.
participants (3)
-
Edward Diener -
John Maddock -
Mathias Gaunard