Overview Repositories Revisions Requests Users Attributes Meta

libseccomp

Edit Package libseccomp
No description set
  • Sources inherited from project security
  • Devel package for openSUSE:Factory
  • 3 derived packages
  • Links to openSUSE:Factory / libseccomp
  • Download package
  • osc -A https://api.opensuse.org checkout home:redwil:15.4/libseccomp && cd $_
  • Create Badge
Refresh
Refresh
Source Files
Filename Size Changed
_link 0000000124 124 Bytes
baselibs.conf 0000000012 12 Bytes
libseccomp-2.5.0.tar.gz 0000638793 624 KB
libseccomp-2.5.0.tar.gz.asc 0000000833 833 Bytes
libseccomp.changes 0000011969 11.7 KB
libseccomp.keyring 0000043508 42.5 KB
libseccomp.spec 0000004365 4.26 KB
testsuite-riscv64-missing-syscalls.patch 0000005670 5.54 KB
Revision 80 (latest revision is 105)
Marcus Meissner's avatar Marcus Meissner (msmeissn) accepted request 833241 from Dominique Leuenberger's avatar Dominique Leuenberger (dimstar) (revision 80) 
- Do not rely on gperf: pass GPERF=/bin/true to configure and
  remove gperf BuildRequires. The syscalls.perf file it would
  generate is part of the tarball already.
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