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
0001-build-use-autotools-as-build-system.patch 0000009239 9.02 KB
_link 0000000124 124 Bytes
libseccomp-2.1.1.tar.gz 0000113133 110 KB
libseccomp-s390x-support.patch 0000061107 59.7 KB
libseccomp.changes 0000002582 2.52 KB
libseccomp.spec 0000004728 4.62 KB
Revision 22 (latest revision is 105)
Jan Engelhardt's avatar Jan Engelhardt (jengelh) accepted request 240751 from Marcus Meissner's avatar Marcus Meissner (msmeissn) (revision 22) 
- updated ppc64le patch

  s390 32bit: passed: 3823 / failed: 91 / errored: 43
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