Re: [Boost-bugs] [Boost C++ Libraries] #11756: boost.Test: non standards compliant use of FE_* macros (unable to compile boost test library on FPU-less arches)

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11756: boost.Test: non standards compliant use of FE_* macros (unable to compile boost test library on FPU-less arches)
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2017-03-11 19:40:19


#11756: boost.Test: non standards compliant use of FE_* macros (unable to compile
boost test library on FPU-less arches)
----------------------------------+------------------------
  Reporter: bartosz.krasinski@… | Owner: renficiaud
      Type: Patches | Status: reopened
 Milestone: Boost 1.64.0 | Component: test
   Version: Boost 1.59.0 | Severity: Problem
Resolution: | Keywords:
----------------------------------+------------------------

Comment (by renficiaud):

 The thing is that ```fenv.h``` is there, and hence this is normal that
 ```BOOST_NO_FENV_H``` is not defined. What is not normal is that
 ```__GLIBC__``` and ```__USE_GNU``` are also defined, which should not be
 the case (this is ulibC after all).

 So my suggestion is not to define ```BOOST_NO_FENV_H```, but to not define
 ```BOOST_TEST_FPE_SUPPORT_WITH_GLIBC_EXTENSIONS__``` for the ulibC (this
 is the purpose of the macro).

 I wanted to know if something outside of boost.test has changed, and this
 is indeed the case (boost.build or config).

 But maybe I am missing sthg?

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/11756#comment:55>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-03-11 19:43:38 UTC