There's a bug in some versions of cmake's FindOpenSSL. Just download and 
use the latest version of cmake from 
https://cmake.org/files/v3.6/cmake-3.6.2-Linux-x86_64.tar.gz


On Sunday, September 11, 2016 at 12:42:27 PM UTC-7, Davide wrote:
>
> I put the output of make (with no -j option and got with tee) in file 
> makejulia.log, together with the files CMakeError.log and CMakeOutput.log 
> in the following GitHub gist:
>
>    https://gist.github.com/anonymous/842016eeac177a2ad634b359592fd6bb
>
> Thanks,
>
>    Davide
>
> On Sunday, September 11, 2016 at 8:10:00 PM UTC+2, Milan Bouchet-Valat 
> wrote:
>>
>> Le dimanche 11 septembre 2016 à 11:05 -0700, Davide a écrit : 
>> > Hi, 
>> > 
>> > I am trying to compile v0.5rc04 and I get the error reported below 
>> > during configuration. 
>> > My system: Debian GNU/Linux 64bit on an Intel i7 machine. 
>> > I checked for the required external dependencies and all are 
>> > installed. 
>> > I have MARCH=native in Make.user. 
>> > 
>> > The last lines of the output of the make command (make -j 4) are: 
>> > 
>> > CMake Error at /usr/share/cmake-3.0/Modules/FindOpenSSL.cmake:293 
>> > (list): 
>> >   list GET given empty list 
>> > Call Stack (most recent call first): 
>> >   CMakeLists.txt:277 (FIND_PACKAGE) 
>> > 
>> > CMake Error at /usr/share/cmake-3.0/Modules/FindOpenSSL.cmake:294 
>> > (list): 
>> >   list GET given empty list 
>> > Call Stack (most recent call first): 
>> >   CMakeLists.txt:277 (FIND_PACKAGE) 
>> > 
>> > CMake Error at /usr/share/cmake-3.0/Modules/FindOpenSSL.cmake:296 
>> > (list): 
>> >   list GET given empty list 
>> > Call Stack (most recent call first): 
>> >   CMakeLists.txt:277 (FIND_PACKAGE) 
>> > 
>> > CMake Error at /usr/share/cmake-3.0/Modules/FindOpenSSL.cmake:298 
>> > (list): 
>> >   list GET given empty list 
>> > Call Stack (most recent call first): 
>> >   CMakeLists.txt:277 (FIND_PACKAGE) 
>> > 
>> > -- Configuring incomplete, errors occurred! 
>> > 
>> >    Thanks for help, 
>> > 
>> >    Davide 
>> Please call make without -j, and post a longer excerpt of the log (e.g. 
>> in a GitHub gist). 
>>
>>
>> Regards 
>>
>

Reply via email to