On Wednesday, April 30, 2014 11:05:25 PM Jan Engelhardt wrote:
> On Wednesday 2014-04-30 20:15, Paul Moore wrote:
> >> If you want to build the tests with static, you can use
> >>
> >> scmp_sys_resolver_LDADD = ../src/libseccomp.la
> >> scmp_sys_resolver_LDFLAGS = -static
> >>
> >> (provided that ./configure was not called with --disable-static, in
> >> which case the user does not want static anyway.)
> >
> >I always want the tests to be built with the static library, regardless of
> >the ./configure options, so we don't accidentally link with the systems
> >libseccomp. Is there a way to do that with libseccomp.la?
>
> kmod does something similar too.:
>
> # src/Makefile.am
> noinst_LTLIBRARIES = libseccomp-internal.la
> libseccomp_internal_la_SOURCES = this.c that.c andsoon.c
> lib_LTLIBRARIES = libseccomp.la
> libseccomp_la_SOURCES = ${libseccomp_internal_la_SOURCES}
> libseccomp_la_LDFLAGS = -version-info ...
>
> # tests/Makefile.am
> scmp_sys_resolve_LDADD = ../src/libseccomp-internal.la
This still ends up building a separate library for use with the tests, what is
the advantage to what you are proposing above? Is it simply the fact that it
is a "LTLIBRARIES" and therefore uses libtool? If so, doesn't that still make
it vulnerable to "--disable-static"?
I guess what I'm looking for is a way to use the existing libseccomp.la
mechanism that would allow us to specify a static linkage for the tests that
wouldn't be affected by configure options.
--
paul moore
security and virtualization @ redhat
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
libseccomp-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libseccomp-discuss
