It looks like you're using an existing configuration already set to use system installed libraries. Try from a clean source tree and an out-of-source (the recommend way to do all cmake things) build directory. Using the 3.6.2 tarball, I get:
$ tar -xvf cmake-3.6.2.tar.gz ... lots of tar output ... $ mkdir cmake-3.6.2-build $ cd cmake-3.6.2-build $ ../cmake-3.6.2/bootstrap --prefix=../cmake-3.6.2-install --------------------------------------------- CMake 3.6.2, Copyright 2000-2016 Kitware, Inc. Found GNU toolchain C compiler on this system is: gcc C++ compiler on this system is: g++ Makefile processor on this system is: gmake g++ is GNU compiler g++ has setenv g++ has unsetenv g++ does not have environ in stdlib.h g++ has stl wstring --------------------------------------------- ... lots of compile output ... loading initial cache file /home/khq.kitware.com/chuck. atkins/Code/CMake/source/cmake-3.6.2-build/Bootstrap. cmk/InitialCacheFlags.cmake -- The C compiler identification is GNU 6.2.1 -- The CXX compiler identification is GNU 6.2.1 ... lots of cmake output ... --------------------------------------------- CMake has bootstrapped. Now run gmake. $ At this point, if you run "make help" then you'll get a list of available targets. In there, amongst others, you will see cmzlib, cmcurl, cmbzip2, cmliblzma, cmlibarchive, cmexpat, and cmjsoncpp. These are CMake's internal copies of the dependencies. When bootstrap is run with --system-libs then system versions of those dependencies will be used instead and the previously mentioned cm<libname> targets will not exist in the make help output. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Thu, Nov 3, 2016 at 10:47 AM, Jayesh Badwaik <pub...@jayeshbadwaik.in> wrote: > > CMake includes internal versions of all the dependencies it needs to > > build. You have the option of using an external system-supplied version > > but it's certainly not required. Without OpenSSL you'll just have a > cmake > > that can't use https, certainly not the end of the world. The default > > configuration of the ./bootstrap command should be using internal > versions > > of all of CMake's dependencies. Is that causing problems for you? > > Yes. The bootstrap command runs successfully, but after that it advises me > to > run gmake, which fails. I've attached the errors of the bootstrap command > and > the gmake command in this mail. > > -- > Cheers > Jayesh Badwaik > https://www.jayeshbadwaik.in >
-- 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: http://public.kitware.com/mailman/listinfo/cmake
