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.4.2.tar.gz 0000601014 587 KB
libseccomp-fix_aarch64-test.patch 0000001261 1.23 KB
libseccomp.changes 0000009308 9.09 KB
libseccomp.keyring 0000043508 42.5 KB
libseccomp.spec 0000004176 4.08 KB
no-static.diff 0000000790 790 Bytes
Revision 71 (latest revision is 105)
Jan Engelhardt's avatar Jan Engelhardt (jengelh) accepted request 761651 from Andreas Schwab's avatar Andreas Schwab (Andreas_Schwab) (revision 71) 
- Tests are passing on all architectures
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