GitHub user sjpcg created a discussion: Error while building kvorkcs ,it sames 
that downloading jemalloc failed

Error Detail  as below:
[ 11%] Creating directories for 'jemalloc-populate'
[ 22%] Performing download step (download, verify and extract) for 
'jemalloc-populate'
-- Downloading...
   
dst='/data0/kvrocks/incubator-kvrocks/build/_deps/jemalloc-subbuild/jemalloc-populate-prefix/src/12cd13cd418512d9e7596921ccdb62e25a103f87.zip'
   timeout='none'
   inactivity timeout='none'
-- Using 
src='https://github.com/jemalloc/jemalloc/archive/12cd13cd418512d9e7596921ccdb62e25a103f87.zip'
CMake Error at 
jemalloc-subbuild/jemalloc-populate-prefix/src/jemalloc-populate-stamp/download-jemalloc-populate.cmake:170
 (message):
  Each download failed!

    error: downloading 
'https://github.com/jemalloc/jemalloc/archive/12cd13cd418512d9e7596921ccdb62e25a103f87.zip'
 failed
          status_code: 1
          status_string: "Unsupported protocol"
          log:
          --- LOG BEGIN ---
          Protocol "https" not supported or disabled in libcurl

  Closing connection -1

  

          --- LOG END ---
          
    


gmake[2]: *** 
[jemalloc-populate-prefix/src/jemalloc-populate-stamp/jemalloc-populate-download]
 Error 1
gmake[1]: *** [CMakeFiles/jemalloc-populate.dir/all] Error 2
gmake: *** [all] Error 2

CMake Error at build/cmake/share/cmake-3.23/Modules/FetchContent.cmake:1088 
(message):
  Build step for jemalloc failed: 2
Call Stack (most recent call first):
  build/cmake/share/cmake-3.23/Modules/FetchContent.cmake:1217:EVAL:2 
(__FetchContent_directPopulate)
  build/cmake/share/cmake-3.23/Modules/FetchContent.cmake:1217 (cmake_language)
  cmake/jemalloc.cmake:29 (FetchContent_Populate)
  CMakeLists.txt:50 (include)


-- Configuring incomplete, errors occurred!
See also "/data0/kvrocks/incubator-kvrocks/build/CMakeFiles/CMakeOutput.log".


GitHub link: https://github.com/apache/incubator-kvrocks/discussions/712

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to