Specify glibc-static as build requirement, fixes #357
Signed-off-by: Lorenzo Fontana <fontanalorenz@gmail.com>
This commit is contained in:
parent
f5e5a4b848
commit
57971c5409
1 changed files with 1 additions and 1 deletions
|
@ -42,7 +42,7 @@ It is currently in active development in the Kubernetes community through the [d
|
||||||
|
|
||||||
### Build
|
### Build
|
||||||
|
|
||||||
`btrfs-progs-devel`, `device-mapper-devel`, `glib2-devel`, `glibc-devel`, `gpgme-devel`, `libassuan-devel`, `libgpg-error-devel`, and `pkg-config` packages on CentOS/Fedora or `btrfs-tools`, `libassuan-dev`, `libc6-dev`, `libdevmapper-dev`, `libglib2.0-dev`, `libgpg-error-dev`, `libgpgme11-dev`, and `pkg-config` on Ubuntu or equivalent is required.
|
`btrfs-progs-devel`, `device-mapper-devel`, `glib2-devel`, `glibc-devel`, `glibc-static`, `gpgme-devel`, `libassuan-devel`, `libgpg-error-devel`, and `pkg-config` packages on CentOS/Fedora or `btrfs-tools`, `libassuan-dev`, `libc6-dev`, `libdevmapper-dev`, `libglib2.0-dev`, `libgpg-error-dev`, `libgpgme11-dev`, and `pkg-config` on Ubuntu or equivalent is required.
|
||||||
In order to enable seccomp support you will need to install development files for `libseccomp` on your platform.
|
In order to enable seccomp support you will need to install development files for `libseccomp` on your platform.
|
||||||
> e.g. `libseccomp-devel` for CentOS/Fedora, or `libseccomp-dev` for Ubuntu
|
> e.g. `libseccomp-devel` for CentOS/Fedora, or `libseccomp-dev` for Ubuntu
|
||||||
In order to enable apparmor support you will need to install development files for `libapparmor` on your platform.
|
In order to enable apparmor support you will need to install development files for `libapparmor` on your platform.
|
||||||
|
|
Loading…
Reference in a new issue