boost chrono bad_cast (gcc > 4.9 on Mac)
Hi All, I was wondering if Boost.Chrono works with gcc > 4.9 on Mac. When system_clock::now() is called, it throws an std::bad_cast exception. The binary from the same code doesn’t have the issue if compiled with clang on Mac and gcc > 4.9 on Linux. The gcc compilers that I use are macport-installed gcc 4.9 and 5.0 (g++-mp-4.9 and g++-mp-5.0) on Mac. Any help would be appreciated. Thanks. Regards, Min Yang Jung
Le 30/04/2016 18:14, Min Yang Jung a écrit :
Hi All,
I was wondering if Boost.Chrono works with gcc > 4.9 on Mac. When system_clock::now() is called, it throws an std::bad_cast exception. The binary from the same code doesn’t have the issue if compiled with clang on Mac and gcc > 4.9 on Linux.
The gcc compilers that I use are macport-installed gcc 4.9 and 5.0 (g++-mp-4.9 and g++-mp-5.0) on Mac.
Any help would be appreciated. Thanks.
Hi, I have no such version installed on Mac, but it used to work when I had it (I removed it when I changed my Mac Version :(). On linux there is no issue for any version (http://www.boost.org/development/tests/master/developer/chrono.html) Unfortunately we don't have regression on MacOS anymore. Any additional information is welcome. Vicente
On 30 Apr 2016, at 18:14, Min Yang Jung
wrote: I was wondering if Boost.Chrono works with gcc > 4.9 on Mac. When system_clock::now() is called, it throws an std::bad_cast exception. The binary from the same code doesn’t have the issue if compiled with clang on Mac and gcc > 4.9 on Linux.
#include
participants (3)
-
Min Yang Jung
-
Thomas Trummer
-
Vicente J. Botet Escriba