Boost logo

Boost :

Subject: Re: [boost] [config] Need some clang testing help...
From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2014-10-05 19:08:27


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/b36566fe04a89103b7ef5569c03e3a26eb77af36
>>
>> 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/b36566fe04a89103b7ef5569c03e3a26eb77af36/include/boost/config/stdlib/libstdcpp3.hpp
>>
>>
>
> 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.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk