Subject: Re: [boost] [EXTERNAL] Clang Darwin trunk Cray 8.0 and max_digits10 support - problem in config?
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2012-07-09 18:56:42
> -----Original Message-----
> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]] On Behalf Of Belcourt,
> Kenneth
> Sent: Monday, July 09, 2012 11:21 PM
> To: <boost_at_[hidden]>
> Subject: Re: [boost] [EXTERNAL] Clang Darwin trunk Cray 8.0 and max_digits10 support - problem in
> config?
>
>
> On Jul 9, 2012, at 10:03 AM, Paul A. Bristow wrote:
>
> >> -----Original Message-----
> >> From: boost-bounces_at_[hidden]
> >> [mailto:boost-bounces_at_[hidden]] On Behalf Of Michel
> > Morin
> >> Sent: Monday, July 09, 2012 3:52 PM
> >> To: boost_at_[hidden]
> >> Subject: Re: [boost] Clang Darwin trunk Cray 8.0 and max_digits10 support - problem in config?
> >>
> >> Paul A. Bristow wrote:
> >>> for Clang the messages are
> >>>
> >>> In file included from ../libs/math/test/zztest_max_digits10.cpp:27:
> >>> In file included from ../boost/config.hpp:40:
> >>> ../boost/config/select_stdlib_config.hpp:18:12: fatal error: 'cstddef'
> >>> file not found # include <cstddef>
> >>>
> >>> In file included from ../libs/math/test/ztest_max_digits10.cpp:27:
> >>> In file included from ../boost/config.hpp:40:
> >>> ../boost/config/select_stdlib_config.hpp:18:12: fatal error: 'cstddef'
> >>> file not found
> >>
> >> boost/config/select_stdlib_config.hpp includes <cstddef> to determine
> >> which stdlib is used. It
> > seems that,
> >> due to some misconfiguration in the test runner, clang cannot find <cstddef>.
> >> In my system (Mac OS X 10.7, clang trunk, libc++ and boost trunk), the two tests run fine.
> >
> > Well, that's reassuring :-)
> >
> > Is there anything else I should do to alert the test runners that very
> > many tests will now fail on their platforms until this is corrected?
>
>
> This is, I'm afraid, out of the test runners hands. The issue is that clang (the same binary)
works fine on
> these platforms if we disable c++11, not sure why enabling c++11 triggers missing cstddef header
> problems. We may need to followup with the clang developers to see if this behavior is known /
expected
> or considered a bug.
Well - I fear it will prevent any useful Boost.Test results on this configuration until it is
resolved. If really, really necessary, I could revert this change for a short time until that is
done.
(Does the fact the Cray test runner has the same problem give any clues?)
Paul