From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] libseccomp: Add new config option to build and install tests
Date: Mon, 21 Sep 2015 11:40:18 +0100 [thread overview]
Message-ID: <55FFDE92.9010901@imgtec.com> (raw)
In-Reply-To: <1442827716-8802-1-git-send-email-markos.chandras@imgtec.com>
Dear Markos Chandras,
could you please mark your previous patch as superseded?
http://patchwork.ozlabs.org/patch/519170/
On 09/21/2015 10:28 AM, Markos Chandras wrote:
> Add new config option to allow building and installing the libseccomp
> testsuite on the target. It's useful for testing the kernels'
> seccomp behavior for the target architecture.
>
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Build test for MIPS architecture. All fine. Binary files built for the
right architecture and no more .py files installed on target. Checked
that now the tests and tools are installed in /usr/share/libseccomp/.
Regards,
Vincent.
> ---
> changes since v2:
> - Move installation path for tests to /usr/share/libseccomp
> - Do not install python files. We don't support python + libseccomp
> at the moment so there is no point in installing these tests yet.
>
> changes since v1:
> - Drop compile hook for tests and use MAKE_OPTS instead
> ---
> package/libseccomp/Config.in | 9 +++++++++
> package/libseccomp/libseccomp.mk | 16 ++++++++++++++++
> 2 files changed, 25 insertions(+)
>
> diff --git a/package/libseccomp/Config.in b/package/libseccomp/Config.in
> index 4c34c5466592..760a6f321142 100644
> --- a/package/libseccomp/Config.in
> +++ b/package/libseccomp/Config.in
> @@ -15,6 +15,15 @@ config BR2_PACKAGE_LIBSECCOMP
>
> https://github.com/seccomp/libseccomp
>
> +config BR2_PACKAGE_LIBSECCOMP_TESTS
> + bool "Install libseccomp tests"
> + depends on BR2_PACKAGE_BASH && BR2_PACKAGE_LIBSECCOMP
> + help
> + Build and install the libseccomp testsuite.
> +
> +comment "libseccomp testsuite needs bash as running shell"
> + depends on !BR2_PACKAGE_BASH && BR2_PACKAGE_LIBSECCOMP
> +
> comment "libseccomp needs a toolchain w/ headers >= 3.12"
> depends on BR2_aarch64 || BR2_mips || BR2_mipsel || BR2_mips64 || \
> BR2_mips64el || BR2_i386 || BR2_x86_64
> diff --git a/package/libseccomp/libseccomp.mk b/package/libseccomp/libseccomp.mk
> index a188298006b1..e6e578b85561 100644
> --- a/package/libseccomp/libseccomp.mk
> +++ b/package/libseccomp/libseccomp.mk
> @@ -17,4 +17,20 @@ define LIBSECCOMP_FIXUP_M4_DIR
> endef
> LIBSECCOMP_POST_EXTRACT_HOOKS += LIBSECCOMP_FIXUP_M4_DIR
>
> +ifeq ($(BR2_PACKAGE_LIBSECCOMP_TESTS),y)
> +
> +LIBSECCOMP_MAKE_OPTS += check-build
> +
> +define LIBSECCOMP_TESTS_INSTALL
> + mkdir -p $(TARGET_DIR)/usr/share/libseccomp/{tests,tools} && \
> + for x in tests tools; do \
> + find $(@D)/$$x -maxdepth 1 \( -name "*.tests" -o -perm -a=x \) -a ! -name "*.py" \
> + -type f -exec cp {} $(TARGET_DIR)/usr/share/libseccomp/$$x/ \; ; \
> + done
> +endef
> +
> +LIBSECCOMP_POST_INSTALL_TARGET_HOOKS += LIBSECCOMP_TESTS_INSTALL
> +
> +endif
> +
> $(eval $(autotools-package))
>
next prev parent reply other threads:[~2015-09-21 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 13:53 [Buildroot] [PATCH] libseccomp: Add new config option to build and install tests Markos Chandras
2015-09-17 17:02 ` Vicente Olivert Riera
2015-09-18 8:19 ` [Buildroot] [PATCH v2] " Markos Chandras
2015-09-18 8:36 ` Vicente Olivert Riera
2015-09-18 8:39 ` Vicente Olivert Riera
2015-09-20 12:46 ` Thomas Petazzoni
2015-09-21 8:39 ` Markos Chandras
2015-09-21 9:28 ` [Buildroot] [PATCH v3] " Markos Chandras
2015-09-21 10:40 ` Vicente Olivert Riera [this message]
2015-10-02 8:24 ` Markos Chandras
2015-11-10 9:49 ` Markos Chandras
2015-11-10 10:00 ` Thomas Petazzoni
2015-11-10 10:14 ` Markos Chandras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55FFDE92.9010901@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox