You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notably, the include paths don't include /home/fboemer/repos/SEAL/thirdparty/zlib-src, which has zlib.h.
During the cmake command, I see
-- ZLIB: download ...
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of off64_t
-- Check size of off64_t - done
-- Looking for fseeko
-- Looking for fseeko - found
-- Looking for unistd.h
-- Looking for unistd.h - found
-- Renaming
-- /home/fboemer/repos/SEAL/thirdparty/zlib-src/zconf.h
-- to 'zconf.h.included' because this file is included with zlib
-- but CMake generates it automatically in the build directory.
-- Zstandard: download ...
-- ZSTD VERSION: 1.4.5
Installing zlib via sudo apt-get install libz-dev fixes the issue.
If I understand correctly, on systems without zlib installed SEAL should automatically download zlib and find zlib.h. If I'm mistaken, and zlib is required on the system, feel free to close the issue.
The text was updated successfully, but these errors were encountered:
Thanks, Fabian, this is a bug and right on time. It is fixed in the next release. Meanwhile, adding the following commands right after this line will fix this for you.
I'm trying to compile SEAL v3.6.1 with the below option:
with cmake version 3.16.3 on Ubuntu 20.04 without zlib already installed.
make VERBOSE=1
yields the below error message:Notably, the include paths don't include
/home/fboemer/repos/SEAL/thirdparty/zlib-src
, which haszlib.h
.During the
cmake
command, I seeInstalling zlib via
sudo apt-get install libz-dev
fixes the issue.If I understand correctly, on systems without zlib installed SEAL should automatically download zlib and find
zlib.h
. If I'm mistaken, and zlib is required on the system, feel free to close the issue.The text was updated successfully, but these errors were encountered: