![]() usr/bin/cmake -E cmake_progress_start /home/matrim/workspace/cmake-examples/01-basic/G-compile-flags/build/CMakeFiles /home/matrim/workspace/cmake-examples/01-basic/G-compile-flags/build/CMakeFiles/progress.marks usr/bin/cmake -H/home/matrim/workspace/cmake-examples/01-basic/G-compile-flags -B/home/matrim/workspace/cmake-examples/01-basic/G-compile-flags/build -check-build-system CMakeFiles/Makefile.cmake 0 Build files have been written to: /home/matrim/workspace/cmake-examples/01-basic/G-compile-flags/build Check for working CXX compiler: /usr/bin/c++ - works Check for working CXX compiler: /usr/bin/c++ Check for working C compiler: /usr/bin/cc - works Check for working C compiler: /usr/bin/cc The CXX compiler identification is GNU 4.8.4 But I'm unsure if its the cause.- The C compiler identification is GNU 4.8.4 This broke cross-compilation of WPE for ARMv7 with CMake (using CMake 3.8.2)ĬMake Error: TRY_RUN() invoked in cross-compiling mode, please set the following cache variables appropriately:Īnd I have seen this also recently on the JSCOnly bots that cross-compile for MIPS/ARMv7.Ī quick search suggests that may be related. > I see you have already added it to the list of patches for the 2.20.3 > The patch for the 2.20 branch is slightly different so I'm including it here > (In reply to Alberto Garcia from comment #30) (In reply to Adrian Perez from comment #31) * We may want to check the output of “$ even in systems that do not With all the above in mind, the following seems like a sensible approach “Some uses of std::atomic also require linking to libatomic.” "gcc -dumpspecs" (look at the 'lib' and 'cpp' entries).” ![]() This is not well documented anywhere other than in Solaris and various BSDs) -pthread is honored. Linking) and link-library additions and/or replacements at link time. Required then you must provide the flag for all compilations not just Yet) to add all required macros to a compilation (if any such flags are Some ports support a special flag (the spelling isn't even standardized “ you will probably need to add a library or flag to g++. Gcc/g++ -v) the same thread model and that model is not ‘single’” “ multithreaded C++ application are only supported when libstdc++Īnd all user code was built with compilers which report (via Has some remarks about usage of atomic operations. I think we should do better detection of what's needed to use 64-bitĪtomic operations and packagers should not need using downstream patchesĪlso, I have been checking the libstdc++ manual at ![]() These functions are also provided by “libatomic“. Implementations for “_sync_add_and_fetch_8” and “_sync_sub_and_fetch_8”. “Source/WebKit/CMakeLists.txt” (lines 780 and below), and only if linkingįails then it adds “Source/WTF/wtf/Atomics.cpp” to the build, which has In short, what it does is using a check similar to the one present in Packaging of WebKitGTK+ the following patch is used: In a private chat with Alberto Garcia he mentioned that for the Debian
0 Comments
Leave a Reply. |