[Cmake-commits] CMake branch, master, updated. v3.11.0-421-g2e49bb6

2018-04-05 Thread Kitware Robot
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  2e49bb643450d4b27788b6f86d58f13ca1fbf917 (commit)
  from  d7af8a34b67026feaee558433db3a835d6007e06 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2e49bb643450d4b27788b6f86d58f13ca1fbf917
commit 2e49bb643450d4b27788b6f86d58f13ca1fbf917
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Fri Apr 6 00:01:03 2018 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Fri Apr 6 00:01:03 2018 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index a173a1e..7ea071b 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 11)
-set(CMake_VERSION_PATCH 20180405)
+set(CMake_VERSION_PATCH 20180406)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Bo Zhou
When use Devtoolset of CentOS, don't forget to install the *binutils* from
that devtoolset, or else, the compilation might generate strange error.

On Fri, Apr 6, 2018 at 6:13 AM, Alexander Neundorf  wrote:

> On 2018 M04 5, Thu 15:15:21 CEST Juan E. Sanchez wrote:
> > The example I just sent was for building in centos 6, because 5 is gone.
>
> not really gone, it's still in vault.centos.org :-)
> https://hub.docker.com/r/aneundorf/centos5-build-base/~/dockerfile/
>
> Alex
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Alexander Neundorf
On 2018 M04 5, Thu 15:15:21 CEST Juan E. Sanchez wrote:
> The example I just sent was for building in centos 6, because 5 is gone.

not really gone, it's still in vault.centos.org :-)
https://hub.docker.com/r/aneundorf/centos5-build-base/~/dockerfile/

Alex

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Alexander Neundorf
On 2018 M04 5, Thu 12:50:04 CEST Ben Sferrazza wrote:
> 
> Were you able to actually build the newer versions of Cmake that require
> c++11 on Centos 5? 

I didn't try that.

Alex

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Juan E. Sanchez

The example I just sent was for building in centos 6, because 5 is gone.

docker run -it  --name centos6 centos:6 /bin/bash

Regards,

Juan

On 4/5/18 3:13 PM, Juan E. Sanchez wrote:

Hello,

Centos 5, Redhat 5 is EOL as of March 31, 2017.

Building cmake in docker:

cd /root;
curl -L -O https://cmake.org/files/v3.11/cmake-3.11.0.tar.gz;
tar xzvf cmake-3.11.0.tar.gz;
yum install -y centos-release-scl;
yum install -y devtoolset-6-gcc devtoolset-6-gcc-c++ 
devtoolset-6-libquadmath-devel devtoolset-6-gcc-gfortran;

source /opt/rh/devtoolset-6/enable;
cd cmake-3.11.0;
./bootstrap --prefix=/root/cmake --parallel=4;
make -j4;
make install;
cd /root;
tar czvf cmake.tgz;

Please note that cmake will silently ignore features for packages that 
haven't been installed into the image, (ncurses, curl).


Regards,

Juan

On 4/5/18 2:50 PM, Ben Sferrazza wrote:



On Thu, Apr 5, 2018 at 12:30 PM, Alexander Neundorf > wrote:


    On 2018 M04 5, Thu 21:24:40 CEST Alexander Neundorf wrote:
    > On 2018 M04 5, Thu 16:15:17 CEST suzuki toshiya wrote:
    > > Dear Eric,
    > >
    > > # if anybody think "how C++11 environment should be prepared
    > > # on legacy GNU/Linux" is off-topic and should be discussed
    > > # in off-list, please let me know. I will do so.
    > >
    > > Eric Wing wrote:
    > > > Thanks for the responses. Yes, I just need this to run on 
Ubuntu 12.04
    > > > (and some other old Linux's in that era). Yes, I think the 
probably is

    > > > the libstdc++ dependency.
    > > >
    > > > As pointed out, it is really hard to get a newer compiler on 
Ubuntu
    > > > 12.04. I've been down this road before, and if memory 
serves, the gcc
    > > > bootstrapping process to get a newer compiler doesn't seem 
to work
    > > > with a compiler older than gcc 4.8. Same goes for clang, 
which also

    > > > weirdly relies on gcc 4.8 to bootstrap itself.
    > >
    > > At least, gcc-4.6.3, the last official gcc for Ubuntu-12.04, 
could

    > > build gcc-4.8.5 manually (without shared libstdc++, so confused
    > > dependency could be avoided). And, I could build cmake-3.11.0 
by it.

    > > Now I'm checking "make test".
    >
    > I have recently built a gcc 4.9.5 on Centos 5, i.e. gcc 4.1. 
There were no

    > issues after getting the configure flags right.

    4.9.4 I mean.
    You can see the flags here:

https://hub.docker.com/r/aneundorf/docker-centos5-build-svn-gcc/~/dockerfile/ 


 


    (but the docker image didn't build, it was killed by a dockerhub
    timeout).

    Alex


Were you able to actually build the newer versions of Cmake that 
require c++11 on Centos 5? I have built up a bootstrapped toolchain, 
following much of the guidance found in Linux From Scratch, on a 
Centos 5 system at work (which unfortunately cannot be upgrade due to 
the support of legacy software). The toolchain uses the latest gcc 
7.3.0, binutils 2.30, and glibc 2.19 (the latest version of glibc 
supported by the 2.6.18 kernel of Centos 5). Yet cmake complains that 
my toolchain does not support c++11. Which kernel and glibc version do 
you have on your Centos 5 box? Thank you.







--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Juan E. Sanchez

Hello,

Centos 5, Redhat 5 is EOL as of March 31, 2017.

Building cmake in docker:

cd /root;
curl -L -O https://cmake.org/files/v3.11/cmake-3.11.0.tar.gz;
tar xzvf cmake-3.11.0.tar.gz;
yum install -y centos-release-scl;
yum install -y devtoolset-6-gcc devtoolset-6-gcc-c++ 
devtoolset-6-libquadmath-devel devtoolset-6-gcc-gfortran;

source /opt/rh/devtoolset-6/enable;
cd cmake-3.11.0;
./bootstrap --prefix=/root/cmake --parallel=4;
make -j4;
make install;
cd /root;
tar czvf cmake.tgz;

Please note that cmake will silently ignore features for packages that 
haven't been installed into the image, (ncurses, curl).


Regards,

Juan

On 4/5/18 2:50 PM, Ben Sferrazza wrote:



On Thu, Apr 5, 2018 at 12:30 PM, Alexander Neundorf > wrote:


On 2018 M04 5, Thu 21:24:40 CEST Alexander Neundorf wrote:
> On 2018 M04 5, Thu 16:15:17 CEST suzuki toshiya wrote:
> > Dear Eric,
> >
> > # if anybody think "how C++11 environment should be prepared
> > # on legacy GNU/Linux" is off-topic and should be discussed
> > # in off-list, please let me know. I will do so.
> >
> > Eric Wing wrote:
> > > Thanks for the responses. Yes, I just need this to run on Ubuntu 12.04
> > > (and some other old Linux's in that era). Yes, I think the probably is
> > > the libstdc++ dependency.
> > >
> > > As pointed out, it is really hard to get a newer compiler on Ubuntu
> > > 12.04. I've been down this road before, and if memory serves, the gcc
> > > bootstrapping process to get a newer compiler doesn't seem to work
> > > with a compiler older than gcc 4.8. Same goes for clang, which also
> > > weirdly relies on gcc 4.8 to bootstrap itself.
> >
> > At least, gcc-4.6.3, the last official gcc for Ubuntu-12.04, could
> > build gcc-4.8.5 manually (without shared libstdc++, so confused
> > dependency could be avoided). And, I could build cmake-3.11.0 by it.
> > Now I'm checking "make test".
>
> I have recently built a gcc 4.9.5 on Centos 5, i.e. gcc 4.1. There were no
> issues after getting the configure flags right.

4.9.4 I mean.
You can see the flags here:

https://hub.docker.com/r/aneundorf/docker-centos5-build-svn-gcc/~/dockerfile/


(but the docker image didn't build, it was killed by a dockerhub
timeout).

Alex


Were you able to actually build the newer versions of Cmake that require 
c++11 on Centos 5? I have built up a bootstrapped toolchain, following 
much of the guidance found in Linux From Scratch, on a Centos 5 system 
at work (which unfortunately cannot be upgrade due to the support of 
legacy software). The toolchain uses the latest gcc 7.3.0, binutils 
2.30, and glibc 2.19 (the latest version of glibc supported by the 
2.6.18 kernel of Centos 5). Yet cmake complains that my toolchain does 
not support c++11. Which kernel and glibc version do you have on your 
Centos 5 box? Thank you.





--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Ben Sferrazza
On Thu, Apr 5, 2018 at 12:30 PM, Alexander Neundorf 
wrote:

> On 2018 M04 5, Thu 21:24:40 CEST Alexander Neundorf wrote:
> > On 2018 M04 5, Thu 16:15:17 CEST suzuki toshiya wrote:
> > > Dear Eric,
> > >
> > > # if anybody think "how C++11 environment should be prepared
> > > # on legacy GNU/Linux" is off-topic and should be discussed
> > > # in off-list, please let me know. I will do so.
> > >
> > > Eric Wing wrote:
> > > > Thanks for the responses. Yes, I just need this to run on Ubuntu
> 12.04
> > > > (and some other old Linux's in that era). Yes, I think the probably
> is
> > > > the libstdc++ dependency.
> > > >
> > > > As pointed out, it is really hard to get a newer compiler on Ubuntu
> > > > 12.04. I've been down this road before, and if memory serves, the gcc
> > > > bootstrapping process to get a newer compiler doesn't seem to work
> > > > with a compiler older than gcc 4.8. Same goes for clang, which also
> > > > weirdly relies on gcc 4.8 to bootstrap itself.
> > >
> > > At least, gcc-4.6.3, the last official gcc for Ubuntu-12.04, could
> > > build gcc-4.8.5 manually (without shared libstdc++, so confused
> > > dependency could be avoided). And, I could build cmake-3.11.0 by it.
> > > Now I'm checking "make test".
> >
> > I have recently built a gcc 4.9.5 on Centos 5, i.e. gcc 4.1. There were
> no
> > issues after getting the configure flags right.
>
> 4.9.4 I mean.
> You can see the flags here:
> https://hub.docker.com/r/aneundorf/docker-centos5-
> build-svn-gcc/~/dockerfile/
> (but the docker image didn't build, it was killed by a dockerhub timeout).
>
> Alex
>

Were you able to actually build the newer versions of Cmake that require
c++11 on Centos 5? I have built up a bootstrapped toolchain, following much
of the guidance found in Linux From Scratch, on a Centos 5 system at work
(which unfortunately cannot be upgrade due to the support of legacy
software). The toolchain uses the latest gcc 7.3.0, binutils 2.30, and
glibc 2.19 (the latest version of glibc supported by the 2.6.18 kernel of
Centos 5). Yet cmake complains that my toolchain does not support c++11.
Which kernel and glibc version do you have on your Centos 5 box? Thank you.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Alexander Neundorf
On 2018 M04 5, Thu 21:24:40 CEST Alexander Neundorf wrote:
> On 2018 M04 5, Thu 16:15:17 CEST suzuki toshiya wrote:
> > Dear Eric,
> > 
> > # if anybody think "how C++11 environment should be prepared
> > # on legacy GNU/Linux" is off-topic and should be discussed
> > # in off-list, please let me know. I will do so.
> > 
> > Eric Wing wrote:
> > > Thanks for the responses. Yes, I just need this to run on Ubuntu 12.04
> > > (and some other old Linux's in that era). Yes, I think the probably is
> > > the libstdc++ dependency.
> > > 
> > > As pointed out, it is really hard to get a newer compiler on Ubuntu
> > > 12.04. I've been down this road before, and if memory serves, the gcc
> > > bootstrapping process to get a newer compiler doesn't seem to work
> > > with a compiler older than gcc 4.8. Same goes for clang, which also
> > > weirdly relies on gcc 4.8 to bootstrap itself.
> > 
> > At least, gcc-4.6.3, the last official gcc for Ubuntu-12.04, could
> > build gcc-4.8.5 manually (without shared libstdc++, so confused
> > dependency could be avoided). And, I could build cmake-3.11.0 by it.
> > Now I'm checking "make test".
> 
> I have recently built a gcc 4.9.5 on Centos 5, i.e. gcc 4.1. There were no
> issues after getting the configure flags right.

4.9.4 I mean.
You can see the flags here:
https://hub.docker.com/r/aneundorf/docker-centos5-build-svn-gcc/~/dockerfile/
(but the docker image didn't build, it was killed by a dockerhub timeout).

Alex

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Alexander Neundorf
On 2018 M04 5, Thu 16:15:17 CEST suzuki toshiya wrote:
> Dear Eric,
> 
> # if anybody think "how C++11 environment should be prepared
> # on legacy GNU/Linux" is off-topic and should be discussed
> # in off-list, please let me know. I will do so.
> 
> Eric Wing wrote:
> > Thanks for the responses. Yes, I just need this to run on Ubuntu 12.04
> > (and some other old Linux's in that era). Yes, I think the probably is
> > the libstdc++ dependency.
> > 
> > As pointed out, it is really hard to get a newer compiler on Ubuntu
> > 12.04. I've been down this road before, and if memory serves, the gcc
> > bootstrapping process to get a newer compiler doesn't seem to work
> > with a compiler older than gcc 4.8. Same goes for clang, which also
> > weirdly relies on gcc 4.8 to bootstrap itself.
> 
> At least, gcc-4.6.3, the last official gcc for Ubuntu-12.04, could
> build gcc-4.8.5 manually (without shared libstdc++, so confused
> dependency could be avoided). And, I could build cmake-3.11.0 by it.
> Now I'm checking "make test".

I have recently built a gcc 4.9.5 on Centos 5, i.e. gcc 4.1. There were no 
issues after getting the configure flags right.

Alex

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


[Cmake-commits] CMake branch, master, updated. v3.11.0-420-gd7af8a3

2018-04-05 Thread Kitware Robot
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  d7af8a34b67026feaee558433db3a835d6007e06 (commit)
   via  57c2834da056394bed178936fbbe9811a36ae006 (commit)
   via  308d21b225af15c52806b6a2d601cb2f06d42629 (commit)
   via  45bf6f6246a72874c880aa3de13ba957abd50ca6 (commit)
   via  304f493e570a177795575b5297c4b54bf1b3d2ac (commit)
   via  44ad8e48def8d98eaff8fd6deb11731520183daa (commit)
   via  30bbb4f2acdebc50a08ef29a0b79577f8275ed2a (commit)
  from  43e44bcd8e14783ff454f70d097cfa9fa8aef652 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d7af8a34b67026feaee558433db3a835d6007e06
commit d7af8a34b67026feaee558433db3a835d6007e06
Merge: 57c2834 44ad8e4
Author: Brad King 
AuthorDate: Thu Apr 5 17:28:14 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 5 13:28:19 2018 -0400

Merge topic 'findwxwidgets-msys-library-dirs'

44ad8e48de FindwxWidgets: Fix wxWidgets_LIBRARY_DIRS on Cygwin/MSYS

Acked-by: Kitware Robot 
Merge-request: !1930


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=57c2834da056394bed178936fbbe9811a36ae006
commit 57c2834da056394bed178936fbbe9811a36ae006
Merge: 308d21b 30bbb4f
Author: Brad King 
AuthorDate: Thu Apr 5 17:27:34 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 5 13:27:39 2018 -0400

Merge topic 'vs10-groups'

30bbb4f2ac cmVisualStudio10TargetGenerator: extend DOM-like generation

Acked-by: Kitware Robot 
Merge-request: !1905


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=308d21b225af15c52806b6a2d601cb2f06d42629
commit 308d21b225af15c52806b6a2d601cb2f06d42629
Merge: 43e44bc 45bf6f6
Author: Brad King 
AuthorDate: Thu Apr 5 17:26:33 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 5 13:26:49 2018 -0400

Merge topic 'msvc-toolset-version-variable'

45bf6f6246 Modules: Use MSVC_TOOLSET_VERSION variable to simplify logic
304f493e57 MSVC: Add MSVC_TOOLSET_VERSION variable

Acked-by: Kitware Robot 
Merge-request: !1882


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=45bf6f6246a72874c880aa3de13ba957abd50ca6
commit 45bf6f6246a72874c880aa3de13ba957abd50ca6
Author: Arkady Shapkin 
AuthorDate: Thu Mar 22 21:50:03 2018 +0300
Commit: Brad King 
CommitDate: Wed Apr 4 13:21:16 2018 -0400

Modules: Use MSVC_TOOLSET_VERSION variable to simplify logic

diff --git a/Modules/FindBoost.cmake b/Modules/FindBoost.cmake
index 8d44aee..5b5002a 100644
--- a/Modules/FindBoost.cmake
+++ b/Modules/FindBoost.cmake
@@ -458,20 +458,10 @@ function(_Boost_GUESS_COMPILER_PREFIX _ret)
   elseif (GHSMULTI)
 set(_boost_COMPILER "-ghs")
   elseif("x${CMAKE_CXX_COMPILER_ID}" STREQUAL "xMSVC")
-if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 19.10)
+if(MSVC_TOOLSET_VERSION GREATER_EQUAL 141)
   set(_boost_COMPILER "-vc141;-vc140")
-elseif (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 19)
-  set(_boost_COMPILER "-vc140")
-elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 18)
-  set(_boost_COMPILER "-vc120")
-elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 17)
-  set(_boost_COMPILER "-vc110")
-elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 16)
-  set(_boost_COMPILER "-vc100")
-elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 15)
-  set(_boost_COMPILER "-vc90")
-elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 14)
-  set(_boost_COMPILER "-vc80")
+elseif(MSVC_TOOLSET_VERSION GREATER_EQUAL 80)
+  set(_boost_COMPILER "-vc${MSVC_TOOLSET_VERSION}")
 elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 13.10)
   set(_boost_COMPILER "-vc71")
 elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 13) # Good luck!
@@ -1009,21 +999,12 @@ 
function(_Boost_UPDATE_WINDOWS_LIBRARY_SEARCH_DIRS_WITH_PREBUILT_PATHS component
 else()
   set(_arch_suffix 32)
 endif()
-if(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 19.10)
+if(MSVC_TOOLSET_VERSION GREATER_EQUAL 141)
   list(APPEND ${componentlibvar} ${basedir}/lib${_arch_suffix}-msvc-14.1)
   list(APPEND ${componentlibvar} ${basedir}/lib${_arch_suffix}-msvc-14.0)
-elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 19)
-  list(APPEND ${componentlibvar} ${basedir}/lib${_arch_suffix}-msvc-14.0)
-elseif(NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 18)
-  

[Cmake-commits] CMake branch, release, updated. v3.11.0-10-g1c85742

2018-04-05 Thread Kitware Robot
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, release has been updated
   via  1c857427013d5b63daf89404d638b4733d19fee6 (commit)
   via  35109e718bf88e3823a8e0d56e0d8ce773d3f445 (commit)
  from  b1aa90f057985d51773dadfe9e69bac45b061a50 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Help/release/3.11.rst |   25 -
 Modules/CheckIncludeFile.cmake|3 ---
 Modules/CheckIncludeFileCXX.cmake |3 ---
 Modules/CheckIncludeFiles.cmake   |3 ---
 4 files changed, 16 insertions(+), 18 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, master, updated. v3.11.0-413-g43e44bc

2018-04-05 Thread Kitware Robot
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  43e44bcd8e14783ff454f70d097cfa9fa8aef652 (commit)
   via  d1660bd2cb9f22be7ecdd2eb6ec9e946f65b137f (commit)
   via  1c857427013d5b63daf89404d638b4733d19fee6 (commit)
   via  35109e718bf88e3823a8e0d56e0d8ce773d3f445 (commit)
  from  aae2bcf8ddfa637a58e0ba976ec7d5357ca078c7 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=43e44bcd8e14783ff454f70d097cfa9fa8aef652
commit 43e44bcd8e14783ff454f70d097cfa9fa8aef652
Merge: d1660bd 1c85742
Author: Brad King 
AuthorDate: Thu Apr 5 13:24:02 2018 -0400
Commit: Brad King 
CommitDate: Thu Apr 5 13:24:02 2018 -0400

Merge branch 'release-3.11'


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d1660bd2cb9f22be7ecdd2eb6ec9e946f65b137f
commit d1660bd2cb9f22be7ecdd2eb6ec9e946f65b137f
Merge: aae2bcf 35109e7
Author: Brad King 
AuthorDate: Thu Apr 5 17:23:25 2018 +
Commit: Kitware Robot 
CommitDate: Thu Apr 5 13:23:34 2018 -0400

Merge topic 'revert-CheckIncludeFile-required-libs'

35109e718b Revert "CheckIncludeFiles: Honor CMAKE_REQUIRED_LIBRARIES"

Acked-by: Kitware Robot 
Merge-request: !1931


---

Summary of changes:
 Help/release/3.11.rst |   25 -
 Modules/CheckIncludeFile.cmake|3 ---
 Modules/CheckIncludeFileCXX.cmake |3 ---
 Modules/CheckIncludeFiles.cmake   |3 ---
 4 files changed, 16 insertions(+), 18 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits


Re: [cmake-developers] Is the "cmake_policy (VERSION 3.11)" statement in the latest UseSWIG.cmake correct?

2018-04-05 Thread Alan W. Irwin

On 2018-04-05 07:34- CHEVRIER, Marc wrote:


Yes, the "cmake_policy" command is here on purpose because the "new" module 
rely on features (mainly source properties) introduced in CMake version 3.11.


OK.  Thanks for that clear answer and also for maintaining this
important module.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Juan E. Sanchez

Hello,

SHORT VERSION:

BTW, Ubuntu 12 is officially End of Life on April 28, 2017

http://releases.ubuntu.com/12.04/

So unless you are paying them for support, you should really upgrade to 
Ubuntu 14.


LONG VERSION:

I recommend starting a docker image of centos 6 in a newer version of 
Ubuntu.  This would be a virtual machine environment you can build a 
version with a newer compiler, g++, but with an older glibc.  The 
libstdc++ you link against would then be compatible with most modern 
distributions.


This is by getting the devtoolset-6 or devtoolset-7 tools provided by 
redhat.  You can communicate with me offline on how to do this, but in 
principle the installation of the compiler is this:


yum install -y centos-release-scl
yum install -y devtoolset-6-gcc devtoolset-6-gcc-c++ 
devtoolset-6-libquadmath-devel devtoolset-6-gcc-gfortran


Docker is freely available and used across the open source community to 
build for multiple linux versions.  It can be installed directly from 
ubuntu as a standard package.


You can then package the application, and it would more than likely run 
on your system.


Regards,

Juan

On 4/4/18 10:23 PM, Eric Wing wrote:

I just discovered that CMake no longer builds on my Ubuntu 12.04. I
need to build binaries that are compatible with that ABI.

I see that your binary distribution of CMake 3.11 still works on
Ubuntu 12.04. Can you tell me what you do to achieve this? What are
you doing for your official builds?

Are you just using -static-libstdc++ -static-libgcc for
CMAKE_CXX_FLAGS, or is there more?

(I just noticed that ldd shows that you don't have dependencies on
libssl, libcrypto, and libz, whereas I do.)

Thanks,
Eric



--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Patrick Griffiths
I had a similar problem on 14.04 and solved it by installing gcc 4.9 (other
version are also available) from the ubuntu-toolchain-r PPA.

This worked for me. YMMV:

$ sudo add-apt-repository ppa:ubuntu-toolchain-r/test
$ sudo apt-get update
$ sudo apt-get install gcc-4.9
$ sudo apt-get install g++-4.9

When building CMake I set the CXX and CC variables at the command line

$ CXX=g++-4.9 CC=gcc-4.9 ../path/to/bootstrap ...etc ..
$ CXX=g++-4.9 CC=gcc-4.9 make install

HTH
Patrick

On Thu, Apr 5, 2018 at 7:15 AM, Robert Maynard 
wrote:

> The official CMake binaries do the same thing as you and build with a
> static libstdc++ and libgcc.
> As far as dependencies we use static builds of those too, with most
> being the version provided inside CMake, and an external openssl.
>
> You can find the more information on the exact flags we are using at:
> https://gitlab.kitware.com/cmake/cmake/blob/master/
> Utilities/Release/linux64_release.cmake
>
> On Thu, Apr 5, 2018 at 3:09 AM, Eric Wing  wrote:
> > Thanks for the responses. Yes, I just need this to run on Ubuntu 12.04
> > (and some other old Linux's in that era). Yes, I think the probably is
> > the libstdc++ dependency.
> >
> > As pointed out, it is really hard to get a newer compiler on Ubuntu
> > 12.04. I've been down this road before, and if memory serves, the gcc
> > bootstrapping process to get a newer compiler doesn't seem to work
> > with a compiler older than gcc 4.8. Same goes for clang, which also
> > weirdly relies on gcc 4.8 to bootstrap itself.
> >
> > Anyway, CMake seems to already know how to ship binaries that work
> > across Linux distros. I'm pretty sure they just statically linked
> > libstdc++ and libgcc. In fact, I just built it with -static-libstdc++
> > -static-libgcc on a newer Linux and tested it on 12.04 and it seemed
> > to work.
> >
> > But I wanted to know for sure how CMake is building their own binaries
> > in case there are subtle problems with what I did, and they have a
> > completely different way of building it, e.g. statically libmusl for C
> > and libc++ for C++, avoiding gcc entirely.
> >
> > Also, I did not take care of the libssl, libcrypto, and libz
> > dependencies. I'm curious in practice how much trouble these are. (My
> > recollection with zlib is that it is extremely stable and they care a
> > great deal about not breaking backwards compatibility. I don't know
> > about the others.)
> >
> > Thanks,
> > Eric
> > --
> >
> > Powered by www.kitware.com
> >
> > Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
> >
> > Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
> >
> > CMake Support: http://cmake.org/cmake/help/support.html
> > CMake Consulting: http://cmake.org/cmake/help/consulting.html
> > CMake Training Courses: http://cmake.org/cmake/help/training.html
> >
> > Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
> >
> > Follow this link to subscribe/unsubscribe:
> > https://cmake.org/mailman/listinfo/cmake
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Robert Maynard
The official CMake binaries do the same thing as you and build with a
static libstdc++ and libgcc.
As far as dependencies we use static builds of those too, with most
being the version provided inside CMake, and an external openssl.

You can find the more information on the exact flags we are using at:
https://gitlab.kitware.com/cmake/cmake/blob/master/Utilities/Release/linux64_release.cmake

On Thu, Apr 5, 2018 at 3:09 AM, Eric Wing  wrote:
> Thanks for the responses. Yes, I just need this to run on Ubuntu 12.04
> (and some other old Linux's in that era). Yes, I think the probably is
> the libstdc++ dependency.
>
> As pointed out, it is really hard to get a newer compiler on Ubuntu
> 12.04. I've been down this road before, and if memory serves, the gcc
> bootstrapping process to get a newer compiler doesn't seem to work
> with a compiler older than gcc 4.8. Same goes for clang, which also
> weirdly relies on gcc 4.8 to bootstrap itself.
>
> Anyway, CMake seems to already know how to ship binaries that work
> across Linux distros. I'm pretty sure they just statically linked
> libstdc++ and libgcc. In fact, I just built it with -static-libstdc++
> -static-libgcc on a newer Linux and tested it on 12.04 and it seemed
> to work.
>
> But I wanted to know for sure how CMake is building their own binaries
> in case there are subtle problems with what I did, and they have a
> completely different way of building it, e.g. statically libmusl for C
> and libc++ for C++, avoiding gcc entirely.
>
> Also, I did not take care of the libssl, libcrypto, and libz
> dependencies. I'm curious in practice how much trouble these are. (My
> recollection with zlib is that it is extremely stable and they care a
> great deal about not breaking backwards compatibility. I don't know
> about the others.)
>
> Thanks,
> Eric
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Stephen McDowell
Hi Suzuki,

(Note: to other CMake mailing list readers, this pertains very little to CMake 
itself.  I’m sending it to the mailing list so that future users with this 
issue may also have a possible solution).

Getting a newer version of GCC is quite challenging by yourself indeed, but you 
may be interested in the Spack package manager: 
http://spack.readthedocs.io/en/latest/getting_started.html 


It’s designed for high performance computing, but has a special emphasis on 
supporting older distributions (since updating HPC cluster operating systems is 
the devil).

Some quick tips:

1. Once you start installing things, you cannot move the spack directory.  So 
decide where you want it and clone it there.  For example, I keep all of my 
installations in /opt/spack

cd /opt
sudo git clone https://github.com/spack/spack.git

Assuming you are `user` on this system (echo $USER)
sudo chown -R user spack/

Then proceed with the getting started tutorial.

2. You have many possible newer versions of GCC available, by default `spack 
install gcc` installs the newest one.  Run `spack info gcc` to see the versions 
available.  Suppose you installed gcc@6.4.0 (which will as you know take a 
while).  You will want to make this available as a compiler, so you `spack load 
gcc@6.4.0` (it might tell you to source a script, so do that) and run `spack 
compiler find`.  When `spack compiler list` shows your shiny new GCC compiler, 
you can now `spack install cmake %gcc@6.4.0` to use GCC 6.4.0 to compile Cmake! 
 Note you don’t need to install GCC 6.4.0, that was purely an example.  I know 
there have been some issues with really old GCC versions compiling newer 
versions, but I think we fixed the underlying problem that caused that.  AKA my 
hope is this works seamlessly, but you may run into trouble.  If you do, you 
might try installing an older version of GCC (in this example, say 6.4.0 didn’t 
work, maybe try GCC 5.5.0).

I hope this is helpful for you!  There’s a lot more to spack, but if you get 
stuck raise an issue on GitHub.  The spack user community is very helpful and 
friendly to newcomers :)

Good luck!

-Stephen

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] [FYI] clang-3.4 vs cmake-3.11.0 (How to build CMake so it works on an older Linux?)

2018-04-05 Thread suzuki toshiya
Dear Marcel,

Oh, I slipped to remind the exist of launchpad... Thanks!
at least, gcc-6.2.0 seems to be available for 12.04.

Regards,
mpsuzuki

Marcel Loose wrote:
> Hi Suzuki,
> 
> Sorry for chiming in late, but you may want to try the PPA for Ubuntu
> Toolchain test builds, which contains compiler builds up to gcc-8 for
> Ubuntu version as old as 10.04. Much less of a hassle than building GCC
> yourself, I can tell from experience. Check out
> https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test
> 
> Cheers,
> Marcel.
> 
> 
> On 05/04/18 07:29, suzuki toshiya wrote:
>> Sorry for bothering subscribers for posting about C++11 environment
>> instead of cmake itself. Now I understand building gcc >= 4.8.5
>> manually might be easier, in comparison with the quest of libc++
>> for clang-3.4.
>>
>> https://stackoverflow.com/questions/39332406/install-libc-on-ubuntu
>>
>> Regards,
>> mpsuzuki
>>
>> suzuki toshiya wrote:
>>> Dear Bo Zhou,
>>>
>>> Sorry, I've confirmed by myself.
>>> By default, clang-3.4 for Ubuntu prioritizes old g++ header files, and clang
>>> header files are searched as a fallback.
>>> I can customize the searching order by -nostdinc++...
>>>
>>> Regards,
>>> mpsuzuki
>>>
>>> suzuki toshiya wrote:
 Dear Bo Zhou,

 Thank you for prompt reply.

> Be aware that GCC suite actually is independent from the libstdc++, so if 
> you have a newer compiler, the compiler might still pick the older 
> libstdc++ without the new API.
 Oh, so, even if I installed clang-3.4, still it uses older (maybe C++03)
 libraries are referred by it?

 Regards,
 mpsuzuki

 Bo Zhou wrote:
> The emplace() is new API from C++11.
>
> Be aware that GCC suite actually is independent from the libstdc++, so if 
> you have a newer compiler, the compiler might still pick the older 
> libstdc++ without the new API.
>
> This issue doesn't exist at Windows, since Visual Studio is a complete 
> sytem.
>
> This issue happens on OSX also, so user must give the compiler a proper 
> MacOS SDK for the new header files etc.
>
> On Thu, Apr 5, 2018 at 1:33 PM, suzuki toshiya 
> > wrote:
> $ clang++ --version
> Ubuntu clang version 3.4-1ubuntu3~precise2 (tags/RELEASE_34/final) (based 
> on
> LLVM 3.4)
> Target: x86_64-pc-linux-gnu
> Thread model: posix
>
> But I got following abort:
>
> cmake-3.11.0/Source/cmLocalGenerator.cxx:553:36: error: no member named 
> 'emplace' in
>   'std::unordered_map std::hash, std::equal_to,
>   std::allocator cmGeneratorTarget
> *> > >'
>   this->GeneratorTargetSearchIndex.emplace(gt->GetName(), gt);
>    ^
>
> G X-D
>
> Regards,
> mpsuzuki
>
> suzuki toshiya wrote:
>> Dear Bo Zhou,
>>
>> Thank you for the info! Now I'm checking Ubuntu 12.04 in LXC.
>> So, gcc-4.8.5 or later would be needed for C++11, it seems that the last 
>> version
>> of gcc officially provided for Ubuntu-12 was 4.7. oh.
>> According to https://clang.llvm.org/cxx_status.html , clang-3.3 supports 
>> C++11,
>> and the last version of clang officially provided for Ubuntu-12 was 3.4. 
>> ooh.
>> I will check if clang-3.4 for Ubuntu-12.04 can compile cmake (or any 
>> other
>> dependency problems would arise).
>>
>>> Usually the ABI is not the problem but the libstdc++, you can use a old 
>>> Ubuntu with old libstdc++ but build CMake with new compiler and make 
>>> sure it links with old libstdc++. This is the trick.
>> Indeed.
>>
>> Regards,
>> mpsuzuki
>>
>> Bo Zhou wrote:
>>> The latest CMake requires C++11 compiler, so what you need is just a 
>>> newer GCC which supports C++11 at your platform, that's it.
>>>
>>> Usually the ABI is not the problem but the libstdc++, you can use a old 
>>> Ubuntu with old libstdc++ but build CMake with new compiler and make 
>>> sure it links with old libstdc++. This is the trick.
>>>
>>> I don't know how to do this on Ubuntu, but on CentOS, it's possible to 
>>> build CMake in that way, so the CMake would be portable at older CentOS 
>>> platform with old libstdc++ .
>>>
>>> Good luck.
>>>
>>> On Thu, Apr 5, 2018 at 12:23 PM, Eric Wing 
>>> >>
>>>  wrote:
>>> I just discovered that CMake no longer builds on my Ubuntu 12.04. I
>>> need to build binaries that are compatible with that ABI.
>>>
>>> I see that your binary distribution of CMake 3.11 still works on
>>> Ubuntu 12.04. Can you tell me what you do to achieve this? What are

Re: [CMake] [FYI] clang-3.4 vs cmake-3.11.0 (How to build CMake so it works on an older Linux?)

2018-04-05 Thread Marcel Loose
Hi Suzuki,

Sorry for chiming in late, but you may want to try the PPA for Ubuntu
Toolchain test builds, which contains compiler builds up to gcc-8 for
Ubuntu version as old as 10.04. Much less of a hassle than building GCC
yourself, I can tell from experience. Check out
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test

Cheers,
Marcel.


On 05/04/18 07:29, suzuki toshiya wrote:
> Sorry for bothering subscribers for posting about C++11 environment
> instead of cmake itself. Now I understand building gcc >= 4.8.5
> manually might be easier, in comparison with the quest of libc++
> for clang-3.4.
>
> https://stackoverflow.com/questions/39332406/install-libc-on-ubuntu
>
> Regards,
> mpsuzuki
>
> suzuki toshiya wrote:
>> Dear Bo Zhou,
>>
>> Sorry, I've confirmed by myself.
>> By default, clang-3.4 for Ubuntu prioritizes old g++ header files, and clang
>> header files are searched as a fallback.
>> I can customize the searching order by -nostdinc++...
>>
>> Regards,
>> mpsuzuki
>>
>> suzuki toshiya wrote:
>>> Dear Bo Zhou,
>>>
>>> Thank you for prompt reply.
>>>
 Be aware that GCC suite actually is independent from the libstdc++, so if 
 you have a newer compiler, the compiler might still pick the older 
 libstdc++ without the new API.
>>> Oh, so, even if I installed clang-3.4, still it uses older (maybe C++03)
>>> libraries are referred by it?
>>>
>>> Regards,
>>> mpsuzuki
>>>
>>> Bo Zhou wrote:
 The emplace() is new API from C++11.

 Be aware that GCC suite actually is independent from the libstdc++, so if 
 you have a newer compiler, the compiler might still pick the older 
 libstdc++ without the new API.

 This issue doesn't exist at Windows, since Visual Studio is a complete 
 sytem.

 This issue happens on OSX also, so user must give the compiler a proper 
 MacOS SDK for the new header files etc.

 On Thu, Apr 5, 2018 at 1:33 PM, suzuki toshiya 
 > wrote:
 $ clang++ --version
 Ubuntu clang version 3.4-1ubuntu3~precise2 (tags/RELEASE_34/final) (based 
 on
 LLVM 3.4)
 Target: x86_64-pc-linux-gnu
 Thread model: posix

 But I got following abort:

 cmake-3.11.0/Source/cmLocalGenerator.cxx:553:36: error: no member named 
 'emplace' in
   'std::unordered_map,
   std::allocator > >'
   this->GeneratorTargetSearchIndex.emplace(gt->GetName(), gt);
    ^

 G X-D

 Regards,
 mpsuzuki

 suzuki toshiya wrote:
> Dear Bo Zhou,
>
> Thank you for the info! Now I'm checking Ubuntu 12.04 in LXC.
> So, gcc-4.8.5 or later would be needed for C++11, it seems that the last 
> version
> of gcc officially provided for Ubuntu-12 was 4.7. oh.
> According to https://clang.llvm.org/cxx_status.html , clang-3.3 supports 
> C++11,
> and the last version of clang officially provided for Ubuntu-12 was 3.4. 
> ooh.
> I will check if clang-3.4 for Ubuntu-12.04 can compile cmake (or any other
> dependency problems would arise).
>
>> Usually the ABI is not the problem but the libstdc++, you can use a old 
>> Ubuntu with old libstdc++ but build CMake with new compiler and make 
>> sure it links with old libstdc++. This is the trick.
> Indeed.
>
> Regards,
> mpsuzuki
>
> Bo Zhou wrote:
>> The latest CMake requires C++11 compiler, so what you need is just a 
>> newer GCC which supports C++11 at your platform, that's it.
>>
>> Usually the ABI is not the problem but the libstdc++, you can use a old 
>> Ubuntu with old libstdc++ but build CMake with new compiler and make 
>> sure it links with old libstdc++. This is the trick.
>>
>> I don't know how to do this on Ubuntu, but on CentOS, it's possible to 
>> build CMake in that way, so the CMake would be portable at older CentOS 
>> platform with old libstdc++ .
>>
>> Good luck.
>>
>> On Thu, Apr 5, 2018 at 12:23 PM, Eric Wing 
>> >>
>>  wrote:
>> I just discovered that CMake no longer builds on my Ubuntu 12.04. I
>> need to build binaries that are compatible with that ABI.
>>
>> I see that your binary distribution of CMake 3.11 still works on
>> Ubuntu 12.04. Can you tell me what you do to achieve this? What are
>> you doing for your official builds?
>>
>> Are you just using -static-libstdc++ -static-libgcc for
>> CMAKE_CXX_FLAGS, or is there more?
>>
>> (I just noticed that ldd shows that you don't have dependencies on
>> libssl, libcrypto, and libz, whereas I do.)
>>
>> Thanks,
>> 

Re: [cmake-developers] Is the "cmake_policy (VERSION 3.11)" statement in the latest UseSWIG.cmake correct?

2018-04-05 Thread CHEVRIER, Marc
Yes, the "cmake_policy" command is here on purpose because the "new" module 
rely on features (mainly source properties) introduced in CMake version 3.11.

On 04/04/2018 21:18, "cmake-developers on behalf of Alan W. Irwin" 
 
wrote:

According to
, an
important side effect of "cmake_policy (VERSION 3.11)" is that no user
with cmake version less than 3.11.0 can use the latest version of
UseSWIG.cmake.

Was that change intended (i.e., does the latest version of
UseSWIG.cmake use policies AND CMake logic that is only available for
3.11.0 and higher)? If so, fair enough.  But if not (i.e., the latest
version of UseSWIG.cmake would work fine for earlier versions of
CMake) I suggest you adjust the above VERSION 3.11 to the actual
minimum version of CMake that will work with this module to advertise
what range of older versions of CMake can use it as a replacement for
the buggy official UseSWIG.cmake that they would otherwise be using.

This reason this issue has come up for me is that I had to copy the
3.9.1 UseSWIG.cmake module to PLplot to give our users that use older
versions of CMake such as 3.6.2 access to an important bug fix in that
version. And that copy has worked fine for us ever since for those
using, e.g., cmake version 3.6.2.  So as a result I became interested
in the official further development of UseSWIG.cmake module after
3.9.1 in case there were any further bug fixes that would be important
to our users.  And that investigation left me wondering whether that
"cmake_policy (VERSION 3.11)" statement actually states the correct
minimum version of cmake that would work with this module.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers


-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread suzuki toshiya
Dear Eric,

# if anybody think "how C++11 environment should be prepared
# on legacy GNU/Linux" is off-topic and should be discussed
# in off-list, please let me know. I will do so.

Eric Wing wrote:
> Thanks for the responses. Yes, I just need this to run on Ubuntu 12.04
> (and some other old Linux's in that era). Yes, I think the probably is
> the libstdc++ dependency.
> 
> As pointed out, it is really hard to get a newer compiler on Ubuntu
> 12.04. I've been down this road before, and if memory serves, the gcc
> bootstrapping process to get a newer compiler doesn't seem to work
> with a compiler older than gcc 4.8. Same goes for clang, which also
> weirdly relies on gcc 4.8 to bootstrap itself.

At least, gcc-4.6.3, the last official gcc for Ubuntu-12.04, could
build gcc-4.8.5 manually (without shared libstdc++, so confused
dependency could be avoided). And, I could build cmake-3.11.0 by it.
Now I'm checking "make test".

If you can give the preferred prefix to install gcc-4.8.5 + cmake-3.11.0,
I would be able to a tarball of the binaries. but please prepare
some virus + malware checking :-)

Regards,
mpsuzuki

> Anyway, CMake seems to already know how to ship binaries that work
> across Linux distros. I'm pretty sure they just statically linked
> libstdc++ and libgcc. In fact, I just built it with -static-libstdc++
> -static-libgcc on a newer Linux and tested it on 12.04 and it seemed
> to work.
> 
> But I wanted to know for sure how CMake is building their own binaries
> in case there are subtle problems with what I did, and they have a
> completely different way of building it, e.g. statically libmusl for C
> and libc++ for C++, avoiding gcc entirely.
> 
> Also, I did not take care of the libssl, libcrypto, and libz
> dependencies. I'm curious in practice how much trouble these are. (My
> recollection with zlib is that it is extremely stable and they care a
> great deal about not breaking backwards compatibility. I don't know
> about the others.)
> 
> Thanks,
> Eric
> 

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


Re: [CMake] How to build CMake so it works on an older Linux?

2018-04-05 Thread Eric Wing
Thanks for the responses. Yes, I just need this to run on Ubuntu 12.04
(and some other old Linux's in that era). Yes, I think the probably is
the libstdc++ dependency.

As pointed out, it is really hard to get a newer compiler on Ubuntu
12.04. I've been down this road before, and if memory serves, the gcc
bootstrapping process to get a newer compiler doesn't seem to work
with a compiler older than gcc 4.8. Same goes for clang, which also
weirdly relies on gcc 4.8 to bootstrap itself.

Anyway, CMake seems to already know how to ship binaries that work
across Linux distros. I'm pretty sure they just statically linked
libstdc++ and libgcc. In fact, I just built it with -static-libstdc++
-static-libgcc on a newer Linux and tested it on 12.04 and it seemed
to work.

But I wanted to know for sure how CMake is building their own binaries
in case there are subtle problems with what I did, and they have a
completely different way of building it, e.g. statically libmusl for C
and libc++ for C++, avoiding gcc entirely.

Also, I did not take care of the libssl, libcrypto, and libz
dependencies. I'm curious in practice how much trouble these are. (My
recollection with zlib is that it is extremely stable and they care a
great deal about not breaking backwards compatibility. I don't know
about the others.)

Thanks,
Eric
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake