[Cmake-commits] CMake branch, master, updated. v3.7.2-1209-gb30ac98

_VERSION_MINOR 7) -set(CMake_VERSION_PATCH 20170127) +set(CMake_VERSION_PATCH 20170128) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[CMake] CMake 3.7.2 and parallel builds

I've recently upgraded to CMake 3.7.2 (and gnu make-4.2.1). Now, when I execute 'make -j5 NightlyBuild', I get the following new (to me) warning: "gmake[4]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule." If I downgrade make back to the previous version, 4.1-r1 (the -r1

Re: [CMake] Comaptibility with older gcc

On 1/27/2017 10:04 AM, Michele Portolan wrote: I have a project that build correctly using gcc 4.9.3, generating a dynamic library that I can later link to obtain my executables. So, nothing special. My problem is that on one of my target systems, I only have a gcc 4.1.2 and I am forced to use

Re: [CMake] Comaptibility with older gcc

27.01.2017, 21:05, "Elizabeth A. Fischer" : > C++ code is not compatible between different compilers.  This is not true for compilers implementing Itanium C++ ABI, including GCC. The only possible source of incompatibility comes from different standard library

Re: [CMake] Comaptibility with older gcc

27.01.2017, 20:04, "Michele Portolan" : > I have a project that build correctly using gcc 4.9.3, generating a > dynamic library that I can later link to obtain my executables. So, > nothing special. > > My problem is that on one of my target systems, I only have

Re: [CMake] Comaptibility with older gcc

> C++ code is not compatible between different compilers. This is only kinda-sorta true. Clang and G++ interoperate quite nicely on Linux, for instance, since they both implement the Itanium-style ABI. I believe Intel's C++ compiler on Windows implements the same ABI as MSVC++. There are no

Re: [CMake] Comaptibility with older gcc

If the target platform has an adapted gcc that does not match upstream gcc, or may not be possible to just compile a newer version. Or it is a discontinued arch. Am 27. Januar 2017 19:05:09 MEZ schrieb "Elizabeth A. Fischer" : >C++ code is not compatible

Re: [CMake] Comaptibility with older gcc

C++ code is not compatible between different compilers. You cannot link C++ code built with GCC 4.9.3 with GCC 4.2.1. Maybe if you hack around and find the GNU C++ libraries from your GCC 4.9.3 installation... just maybe, with enough hacking, it will work. But in general, this is a rabbit hole

Re: [CMake] Comaptibility with older gcc

It depends very much on your target system. The C++-ABI between 4.9 and 4.1 may be compatible but that is not guaranteed. C++14 is also a bit unspecific: language features or library features? Does your library expose any C++11/14 features in its interface? It may just not be possible after

Re: [CMake] Comaptibility with older gcc

Your answer is totally unrelated to the question. Am 27. Januar 2017 18:23:39 MEZ schrieb "Elizabeth A. Fischer" : >Get spack, then use it to build GCC 4.9.3 takes a couple hours of wall >time, five minutes of your time. > >Github.com/llnl/spack >On Jan 27, 2017

Re: [CMake] Comaptibility with older gcc

Get spack, then use it to build GCC 4.9.3 takes a couple hours of wall time, five minutes of your time. Github.com/llnl/spack On Jan 27, 2017 12:04 PM, "Michele Portolan" < michele.porto...@grenoble-inp.fr> wrote: > I have a project that build correctly using gcc 4.9.3, generating a > dynamic

Re: [CMake] Comaptibility with older gcc

27.01.2017, 20:04, "Michele Portolan" : > I have a project that build correctly using gcc 4.9.3, generating a > dynamic library that I can later link to obtain my executables. So, > nothing special. > > My problem is that on one of my target systems, I only have

[CMake] Comaptibility with older gcc

I have a project that build correctly using gcc 4.9.3, generating a dynamic library that I can later link to obtain my executables. So, nothing special. My problem is that on one of my target systems, I only have a gcc 4.1.2 and I am forced to use it for at least linking the last executable.

[Cmake-commits] CMake branch, next, updated. v3.7.2-2396-g2086b6a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 2086b6a344ba7dbf235a5d161035aea9fb966628 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.2-2393-g597fe23

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 597fe23b9bdeff2276adc1c6204c7d45eee7f7bd (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.2-1202-gfa9c129

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via fa9c12933f0fc51ee577a43b51381b4d8e4a127b (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.2-2388-g51c1863

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 51c1863936254a27fb1fe756f2c5c2bcef718422 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.2-2390-gc610be3

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via c610be3c4f698e4fdb3e3272305e381121c8103b (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.2-2379-g75650c6

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 75650c68024ad5d9d3374e197d5fdec5ae9406aa (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.2-2377-gad64b91

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via ad64b91c25208a5b27f49cef201ae155aae3cd9e (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.2-1204-g86ec0ac

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 86ec0aca050f2568cea691a0ec965f6a95e06d2b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.2-1206-g0ea578b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 0ea578b498059340d575be263f5b6a91581f5ce5 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.2-1208-g325c615

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 325c6153088c673569971958f107f6cb97b67c50 (commit) via