Python's distutils/setup.py doesn't play well with libtool libraries so directly reference the static libseccomp library inside setup.py. Also fix a problem with the automake configuration which likely masked this problem in the first place.
Signed-off-by: Paul Moore <[email protected]> --- src/python/Makefile.am | 4 ++-- src/python/setup.py | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/python/Makefile.am b/src/python/Makefile.am index 27b4188..8ecd7d9 100644 --- a/src/python/Makefile.am +++ b/src/python/Makefile.am @@ -35,11 +35,11 @@ PY_INSTALL = ${PY_DISTUTILS} install all-local: build -build: ../libseccomp-internal.la libseccomp.pxd seccomp.pyx +build: ../libseccomp-internal.la libseccomp.pxd seccomp.pyx setup.py ${PY_BUILD} && touch build install-exec-local: build ${PY_INSTALL} --prefix=${DESTDIR}/${prefix} clean-local: - ${RM} -rf seccomp.c build/ + ${RM} -rf seccomp.c build diff --git a/src/python/setup.py b/src/python/setup.py index a8a95df..e559a2e 100644 --- a/src/python/setup.py +++ b/src/python/setup.py @@ -40,6 +40,6 @@ setup( cmdclass = {'build_ext': build_ext}, ext_modules = [ Extension("seccomp", ["seccomp.pyx"], - extra_objects=["../libseccomp-internal.la"]) - ] + extra_objects=["../.libs/libseccomp-internal.a"]) + ] ) ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ libseccomp-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libseccomp-discuss
