search for: check_cxx_source_compil

Displaying 4 results from an estimated 4 matches for "check_cxx_source_compil".

2016 Dec 22
2
(Thin)LTO llvm build
...lse on your > system? > Here's the check from the cmake file: > > # There doesn't seem to be an easy way to check the library version. Instead, > # we rely on the fact that std::set did not have the allocator constructor available > # until version 4.9 > check_cxx_source_compiles(" > #include <set> > std::set<int> s = std::set<int>(std::allocator<int>()); > int main() { return 0; }" I cannot make g++ 6.2.1 fail to build the test snippet with or without the archlinux-default/custom CXXFLAGS and...
2016 Dec 21
0
(Thin)LTO llvm build
...p a different libstdc++ from somewhere else on your system? Here's the check from the cmake file: # There doesn't seem to be an easy way to check the library version. Instead, we rely on the # fact that std::set did not have the allocator constructor available until version 4.9 check_cxx_source_compiles(" #include <set> std::set<int> s = std::set<int>(std::allocator<int>()); int main() { return 0; }" LLDB_USING_LIBSTDCXX_4_9) So the version check isn't precise, but unless libstdc++ 6.2.1 doesn't have this interface a...
2016 Dec 23
0
(Thin)LTO llvm build
...#39;s the check from the cmake file: > > > > # There doesn't seem to be an easy way to check the library version. > Instead, > > # we rely on the fact that std::set did not have the allocator > constructor available > > # until version 4.9 > > check_cxx_source_compiles(" > > #include <set> > > std::set<int> s = std::set<int>(std::allocator<int>()); > > int main() { return 0; }" > > I cannot make g++ 6.2.1 fail to build the test snippet with > or without the archlinu...
2016 Dec 21
2
(Thin)LTO llvm build
On Wed, Dec 21, 2016 at 2:55 PM, Teresa Johnson <tejohnson at google.com> wrote: > I think you can get this via "ninja -t commands bin/lldb-argdumper" > (this will give you a lot of output, all of the compilation commands > used to build that target). Or redo the build with -v to be sure. Unfortunately the old build tree is gone for space reclaim reasons. Sorry, I'll