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 ..
Hi Jayesh,
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
Jayesh,
Use Spack. Spack has no problem auto-building CMake for you, along with
curl and whatever else it needs.
https://github.com/llnl/spack/
-- Elizabeth
On Wed, Nov 2, 2016 at 1:08 PM, Jayesh Badwaik
wrote:
> Hi,
>
> Is there a way to build CMake without curl? I am currently in an
> env
Hi,
Is there a way to build CMake without curl? I am currently in an environment
where I have no openssl-dev packages nor libcurl-dev packages. So, if I want
to build CMake, I will need to build openssl-dev myself which I do not want to
do.
I can ask my sysadmin for the packages, but I was wo