-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cmake fails for Gvm-libs #284
Comments
I guess the problem is that Alpine is using musl libc which is (as seen on various occasions) different to glibc. @SergioBinfo you probably need to find / research if there is any alternative for musl libc to the not available malloc_trim. As @greenbone/gvm-dev probably isn't adding compatibility for Alpine Linux this needs an update / PR from the community / some one familiar with Alpine Linux to make gvm-libs to build on Alpine Linux. |
Calling malloc_trim is not required, so you could just patch out the calls. |
You can check the APKBUILD for Alpine. I'm the maintainer, you can use it as base. https://git.alpinelinux.org/aports/tree/community/openvas?h=master Hope it helps. |
We will replace the malloc_trim calls. |
For now, Alpine has a patch downstream that disables malloc_trim() since it's GLIBC specific, while Alpine uses musl.
|
Hi, I'm trying to create a Dockerfile which will install GVM10 from its source code. I'm using alpine 3.10 as base image. I'm following the install.md for each component.
Expected behavior
cmake with success in the folder where I unzipped the source code of gvm-libs and go to the next stop which will be make and make install.
Current behavior
Warnings stops with error and abort the process.
Steps to reproduce
GVM versions
gsa: (gsad --version)
8.0.1
gvm: (gvmd --version)
8.0.1
openvas-scanner: (openvassd --version)
6.0.1
gvm-libs:
10.0.1
openvas-smb:
1.0.5
Environent
Operating system:
Linux Alpine
Installation method / source: (packages, source installation)
From source code https://community.greenbone.net/t/gvm-10-old-stable-initial-release-2019-04-05/208
Logfiles
The text was updated successfully, but these errors were encountered: