Overview

libseccomp

Edit Package libseccomp
No description set
  • Devel package for openSUSE:Factory
  • 2 derived packages
  • Developed at SCM
  • Download package
  • osc -A https://api.opensuse.org checkout security/libseccomp && cd $_
  • Create Badge
Refresh
Source Files
Filename Size Changed
62-sim-arch_transactions-remove-fuzzer.patch 0000001360 1.33 KB
_multibuild 0000000055 55 Bytes
_scmsync.obsinfo 0000000157 157 Bytes
baselibs.conf 0000000012 12 Bytes
build.specials.obscpio 0000000308 308 Bytes
libseccomp-2.6.0.tar.gz 0000685655 670 KB
libseccomp-2.6.0.tar.gz.asc 0000000833 833 Bytes
libseccomp.changes 0000016552 16.2 KB
libseccomp.keyring 0000046563 45.5 KB
libseccomp.spec 0000005897 5.76 KB
make-python-build.patch 0000026065 25.5 KB
modernize-python-build.patch 0000004619 4.51 KB
python-pip-packages.patch 0000008763 8.56 KB
Comments 2
Jochen Breuer's avatar
Jochen Breuer (brejoc) -

While the spec mentions the python bindings for seccomp, it's not actually enabled with --enable-python during ./configure. Also static builds are disable with --disable-static, which prevents setup.py from running because libseccomp.a is missing. Can we have both, static an dynamic binaries somehow?

Jan Engelhardt's avatar
Jan Engelhardt (jengelh) -
maintainer
  1. Removed the package def, because if anything, it should be replaced with the python macro magic for multipython builds.
  2. If setup.py requires libseccomp.a, then setup is broken and needs fixing. Reading .la files to determine the real lib name is not hard.
openSUSE Build Service is sponsored by
Places