libstdc++

I'm looking for a set of portable distributions for the standard C++11 engines like `std::mt19937' (see http://en.cppreference.com/w/cpp/numeric/random ). The engine implementations perform consistently (i.e. same sequence generated on different platforms – tested with Clang and MSVC), but the distributions seem to be implemented differently on the different platforms. So, even though the engines produce the same sequence, it seems that a distribution (for example, std::normal_distribution<double> ) does not use the same number of samples (i.e. produces different results) on the different

I am developing command line interface executables for both osx and linux using c/c++. The project will link against opencv. Should I use libc++ or libstdc++? Jonathan Wakely I would use the native library for each OS i.e. libstdc++ on GNU/Linux and libc++ on Mac OS X. libc++ is not 100% complete on GNU/Linux, and there's no real advantage to using it when libstdc++ is more complete. Also, if you want to link to any other libraries written in C++ they will almost certainly have been built with libstdc++ so you'll need to link with that too to use them. More info here about the completeness of

I see a fair amount of questions like Apple Mach-O Linker (Id) Error and Undefined symbols in cryptopp at IOS 64-bit project . The problem is usually described as: Undefined symbols for architecture i386: "std::__1::basic_ostream<char, std::__1::char_traits<char> >::flush()", referenced from: cv::gpu::error(char const*, char const*, int, char const*) in opencv2(gpumat.o) The problem often reduces to mixing/matching -stdlib=libc++ (LLVM C++ runtime) and -stdlib=libstdc++ (GNU C++ runtime). The LLVM C++ runtime ( libc++ ) has an __1 decoration symbol, but the GNU C++ runtime libstdc++ lacks the

I am working in C++ under Mac OS X (10.8.2) and I recently came up with the need of using C++11 features, which are available through the clang++ compiler using the libc++ stdlib. However, I also need to use some legacy library compiled and linked against libstdc++ (coming from MacPorts). In doing so, I got linking errors, since the headers of the legacy libraries using, e.g., std::string , required to be resolved against the std::__1::basic_string (i.e., the libc++ implementation of std::string ) instead of the std::basic_string implementation. Is there a way to mix the two libraries in

Consider the situation when a C++ project is built and shipped within a Centos 7 virtual machine or container. Default gcc for Centos 7 is 4.8 . In order to allow developers to use modern C++, the more recent version of gcc (for example, 6.3 ) is installed into Centos 7 which runs as a CI server. This provides -std=c++14 support. [builder@f7279ae9f33f build (master %)]$ /usr/bin/c++ -v 2>&1 | grep version gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) [builder@f7279ae9f33f build (master %)]$ /opt/rh/devtoolset-6/root/usr/bin/c++ -v 2>&1 | grep version gcc version 6.3.1 20170216 (Red Hat 6