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/
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
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
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:
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
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++
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 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
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.
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
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
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
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
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
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
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
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
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
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
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"
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
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,
22 matches
Mail list logo