search for: checkcompilerversion

Displaying 20 results from an estimated 22 matches for "checkcompilerversion".

2018 May 11
6
A Short Policy Proposal Regarding Host Compilers
...Clang 7.0 release, we will officially support any major release of our host compilers (MSVC, GCC, Clang, ?ICC?) released in the past 3* years from our previous branch date to give trunk-developers time to transition (so for 7.0, 3 years before January 3, 2018). This will be enforced via the CMake CheckCompilerVersion script (ala https://reviews.llvm.org/D46723). ADDITIONALLY, a CMake warning will be issued for any major release less than 1.5* years old to give our users sufficient time to transition/upgrade their compilers. Finally, our dependent C++ version will be the best released standard officially suppo...
2016 May 05
2
LLVM cross compilation for arm target
...LLVM_TARGETS_TO_BUILD=ARM -DCMAKE_CXX_FLAGS='-target armv7a-linux-gnueabihf -mcpu=cortex-a9 -I/usr/arm-linux-gnueabihf/include/c++/4.7.1/arm-linux-gnueabihf/ -I/usr/arm-linux-gnueabihf/include/ -mfloat-abi=hard -ccc-gcc-name arm-linux-gnueabihf-gcc' *error :* CMake Error at cmake/modules/CheckCompilerVersion.cmake:38 (message): Host Clang must be able to find libstdc++4.7 or newer! Call Stack (most recent call first): cmake/config-ix.cmake:14 (include) CMakeLists.txt:412 (include) I have installed libstdc++4.7-dev library but still same issue is coming. Does anyone know how to resolve this issu...
2016 Dec 13
0
LLVM Documentation - How does it get updated?
...) it's all > consistent with a certain point in time (again, I'd have to find the exact > CL), but nothing after that point in time ever made it in. I'm betting it was around the time we made GCC 4.8 the minimum requirement... :) Generating makefiles CMake Error at cmake/modules/CheckCompilerVersion.cmake:12 (message): Host GCC version must be at least 4.8! Call Stack (most recent call first): cmake/config-ix.cmake:14 (include) CMakeLists.txt:582 (include) However, the GCC on that machine is 4.9.4, so I have no idea why the error... Unfortunately, we don't have a good way to captur...
2016 Dec 13
2
LLVM Documentation - How does it get updated?
...t with a certain point in time (again, I'd have to find the exact >> CL), but nothing after that point in time ever made it in. > > I'm betting it was around the time we made GCC 4.8 the minimum requirement... :) > > Generating makefiles > CMake Error at cmake/modules/CheckCompilerVersion.cmake:12 (message): > Host GCC version must be at least 4.8! > Call Stack (most recent call first): > cmake/config-ix.cmake:14 (include) > CMakeLists.txt:582 (include) > > However, the GCC on that machine is 4.9.4, so I have no idea why the error... > > Unfortunately, w...
2018 May 11
0
A Short Policy Proposal Regarding Host Compilers
...we will officially support any major > release of our host compilers (MSVC, GCC, Clang, ?ICC?) released in the > past 3* years from our previous branch date to give trunk-developers time > to transition (so for 7.0, 3 years before January 3, 2018). This will be > enforced via the CMake CheckCompilerVersion script (ala > https://reviews.llvm.org/D46723). ADDITIONALLY, a CMake warning will be > issued for any major release less than 1.5* years old to give our users > sufficient time to transition/upgrade their compilers. Finally, our > dependent C++ version will be the best released stand...
2018 May 18
2
A Short Policy Proposal Regarding Host Compilers
...Clang 7.0 release, we will officially support any major release of our host compilers (MSVC, GCC, Clang, ?ICC?) released in the past 3* years from our previous branch date to give trunk-developers time to transition (so for 7.0, 3 years before January 3, 2018). This will be enforced via the CMake CheckCompilerVersion script (ala https://reviews.llvm.org/D46723). ADDITIONALLY, a CMake warning will be issued for any major release less than 1.5* years old to give our users sufficient time to transition/upgrade their compilers. Finally, our dependent C++ version will be the best released standard officially suppo...
2018 May 13
0
A Short Policy Proposal Regarding Host Compilers
...Clang 7.0 release, we will officially support any major release of our host compilers (MSVC, GCC, Clang, ?ICC?) released in the past 3* years from our previous branch date to give trunk-developers time to transition (so for 7.0, 3 years before January 3, 2018). This will be enforced via the CMake CheckCompilerVersion script (ala https://reviews.llvm.org/D46723). ADDITIONALLY, a CMake warning will be issued for any major release less than 1.5* years old to give our users sufficient time to transition/upgrade their compilers. Finally, our dependent C++ version will be the best released standard officially suppo...
2016 Jul 06
3
GCC prerequisites for building LLVM head?
Is there is minimum required version for GCC to build LLVM from the head revision? I have GCC v4.9.3, but 'Tools/sancov/sancov.cc' won't build because 'std::to_string' does not exist. When running CMake it did not flag GCC v4.9.3 as too old, and it is passing the '-std=gnu++11' option, but apparently this version of GCC is not fully C++ 11 compliant, or at least
2018 May 11
1
A Short Policy Proposal Regarding Host Compilers
...Clang 7.0 release, we will officially support any major release of our host compilers (MSVC, GCC, Clang, ?ICC?) released in the past 3* years from our previous branch date to give trunk-developers time to transition (so for 7.0, 3 years before January 3, 2018). This will be enforced via the CMake CheckCompilerVersion script (ala https://reviews.llvm.org/D46723). ADDITIONALLY, a CMake warning will be issued for any major release less than 1.5* years old to give our users sufficient time to transition/upgrade their compilers. Finally, our dependent C++ version will be the best released standard officially suppo...
2019 Jan 08
2
A Short Policy Proposal Regarding Host Compilers
...Clang 7.0 release, we will officially support any major release of our host compilers (MSVC, GCC, Clang, ?ICC?) released in the past 3* years from our previous branch date to give trunk-developers time to transition (so for 7.0, 3 years before January 3, 2018). This will be enforced via the CMake CheckCompilerVersion script (ala https://reviews.llvm.org/D46723). ADDITIONALLY, a CMake warning will be issued for any major release less than 1.5* years old to give our users sufficient time to transition/upgrade their compilers. Finally, our dependent C++ version will be the best released standard officially suppo...
2016 Dec 13
0
LLVM Documentation - How does it get updated?
...I'd have to find the > exact > >> CL), but nothing after that point in time ever made it in. > > > > I'm betting it was around the time we made GCC 4.8 the minimum > requirement... :) > > > > Generating makefiles > > CMake Error at cmake/modules/CheckCompilerVersion.cmake:12 (message): > > Host GCC version must be at least 4.8! > > Call Stack (most recent call first): > > cmake/config-ix.cmake:14 (include) > > CMakeLists.txt:582 (include) > > > > However, the GCC on that machine is 4.9.4, so I have no idea why the > er...
2016 Dec 13
2
LLVM Documentation - How does it get updated?
Yes when I first committed the docs were fine upstream. I think I even got 1 or 2 additional commits that I could see the changes of reflected on the website. At some point though, it just stopped updating (I don't know which exact CL). I can find a date range of when things stopped being update if that would be helpful. If I look at the PDB documentation now (which is rooted here
2019 Jan 11
2
A Short Policy Proposal Regarding Host Compilers
...Clang 7.0 release, we will officially support any major release of our host compilers (MSVC, GCC, Clang, ?ICC?) released in the past 3* years from our previous branch date to give trunk-developers time to transition (so for 7.0, 3 years before January 3, 2018). This will be enforced via the CMake CheckCompilerVersion script (ala https://reviews.llvm.org/D46723 <https://reviews.llvm.org/D46723>). ADDITIONALLY, a CMake warning will be issued for any major release less than 1.5* years old to give our users sufficient time to transition/upgrade their compilers. Finally, our dependent C++ version will be the...
2018 May 11
5
A Short Policy Proposal Regarding Host Compilers
...ly support any major >> release of our host compilers (MSVC, GCC, Clang, ?ICC?) released in the >> past 3* years from our previous branch date to give trunk-developers time >> to transition (so for 7.0, 3 years before January 3, 2018). This will be >> enforced via the CMake CheckCompilerVersion script (ala >> https://reviews.llvm.org/D46723). ADDITIONALLY, a CMake warning will be >> issued for any major release less than 1.5* years old to give our users >> sufficient time to transition/upgrade their compilers. Finally, our >> dependent C++ version will be the bes...
2016 Jul 06
2
GCC prerequisites for building LLVM head?
...ing LLVM head? On 6 July 2016 at 08:46, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Is there is minimum required version for GCC to build LLVM from the > head revision? Last I checked it was 4.7. The CMake files also tell me that's correct: modules/CheckCompilerVersion.cmake: # Check if the host compiler is new enough. LLVM requires at least GCC 4.7, > I have GCC v4.9.3, but ‘Tools/sancov/sancov.cc’ won’t build because > ‘std::to_string’ does not exist. When running CMake it did not flag > GCC > v4.9.3 as too old, and it is passing the ‘-std=gnu+...
2019 Apr 01
2
[RFC] migrating LLVM to C++14
...t; - std::quoted <https://wg21.link/N3654>: > - Without restriction. > - std::exchange <https://wg21.link/N3668>: > - Without restriction. > - Change the minimum toolchain requirement from a “soft-error” to a > “hard-error” such that CheckCompilerVersion.cmake now says: > - set(GCC_MIN 5.1) > set(GCC_SOFT_ERROR 5.1) > set(CLANG_MIN 3.5) > set(CLANG_SOFT_ERROR 3.5) > set(APPLECLANG_MIN 6.0) > set(APPLECLANG_SOFT_ERROR 6.0) > set(MSVC_MIN 19.1) > set(MSVC_SOFT_ERROR 19.1) >...
2019 May 06
2
[RFC] migrating LLVM to C++14
...3781>: >> Not allowed. >> std::quoted <https://wg21.link/N3654>: >> Without restriction. >> std::exchange <https://wg21.link/N3668>: >> Without restriction. >> Change the minimum toolchain requirement from a “soft-error” to a “hard-error” such that CheckCompilerVersion.cmake now says: >> set(GCC_MIN 5.1) >> set(GCC_SOFT_ERROR 5.1) >> set(CLANG_MIN 3.5) >> set(CLANG_SOFT_ERROR 3.5) >> set(APPLECLANG_MIN 6.0) >> set(APPLECLANG_SOFT_ERROR 6.0) >> set(MSVC_MIN 19.1) >> set(MSVC_SOFT_ERROR 19.1) >> The above makes...
2019 May 06
2
[RFC] migrating LLVM to C++14
...ot allowed. >>> std::quoted <https://wg21.link/N3654>: >>> Without restriction. >>> std::exchange <https://wg21.link/N3668>: >>> Without restriction. >>> Change the minimum toolchain requirement from a “soft-error” to a “hard-error” such that CheckCompilerVersion.cmake now says: >>> set(GCC_MIN 5.1) >>> set(GCC_SOFT_ERROR 5.1) >>> set(CLANG_MIN 3.5) >>> set(CLANG_SOFT_ERROR 3.5) >>> set(APPLECLANG_MIN 6.0) >>> set(APPLECLANG_SOFT_ERROR 6.0) >>> set(MSVC_MIN 19.1) >>> set(MSVC_SOFT_ERROR...
2018 May 11
0
A Short Policy Proposal Regarding Host Compilers
...Clang 7.0 release, we will officially support any major release of our host compilers (MSVC, GCC, Clang, ?ICC?) released in the past 3* years from our previous branch date to give trunk-developers time to transition (so for 7.0, 3 years before January 3, 2018). This will be enforced via the CMake CheckCompilerVersion script (ala https://reviews.llvm.org/D46723 <https://reviews.llvm.org/D46723>). ADDITIONALLY, a CMake warning will be issued for any major release less than 1.5* years old to give our users sufficient time to transition/upgrade their compilers. Finally, our dependent C++ version will be the...
2019 May 06
2
[RFC] migrating LLVM to C++14
...>>> - Without restriction. >>>> - std::exchange <https://wg21.link/N3668>: >>>> - Without restriction. >>>> - Change the minimum toolchain requirement from a “soft-error” >>>> to a “hard-error” such that CheckCompilerVersion.cmake now says: >>>> - set(GCC_MIN 5.1) >>>> set(GCC_SOFT_ERROR 5.1) >>>> set(CLANG_MIN 3.5) >>>> set(CLANG_SOFT_ERROR 3.5) >>>> set(APPLECLANG_MIN 6.0) >>>> set(APPLECLANG_SOFT_ERROR 6.0) &g...