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
_service 0000000347 347 Bytes
baselibs.conf 0000000012 12 Bytes
builderror-k316.diff 0000000781 781 Bytes
libseccomp-2.3.0.tar.gz 0000546948 534 KB
libseccomp-2.3.0.tar.gz.SHA256SUM.asc 0000000958 958 Bytes
libseccomp.changes 0000004844 4.73 KB
libseccomp.spec 0000004854 4.74 KB
no-static.diff 0000000754 754 Bytes
Revision 42 (latest revision is 105)
Marcus Meissner's avatar Marcus Meissner (msmeissn) committed (revision 42) 
- updated to final 2.3.0 release
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