From: Mason <slash.tmp@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] ltp-testsuite: build kernel modules when appropriate
Date: Tue, 5 Apr 2016 13:09:40 +0200 [thread overview]
Message-ID: <57039CF4.5060902@free.fr> (raw)
In-Reply-To: <57038409.20600@mind.be>
From: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
If we're building a kernel, we can also build LTP's test modules.
Signed-off-by: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
---
Tested using the defconfig provided by Thomas Petazzoni.
$ find output/build/ltp-testsuite-20160126 -name *.ko
output/build/ltp-testsuite-20160126/testcases/kernel/device-drivers/uaccess/ltp_uaccess.ko
output/build/ltp-testsuite-20160126/testcases/kernel/device-drivers/block/block_dev_kernel/ltp_block_dev.ko
output/build/ltp-testsuite-20160126/testcases/kernel/module/delete_module/dummy_del_mod.ko
output/build/ltp-testsuite-20160126/testcases/kernel/module/delete_module/dummy_del_mod_dep.ko
output/build/ltp-testsuite-20160126/testcases/kernel/firmware/fw_load_kernel/ltp_fw_load.ko
Three modules still fail to build, but I think this depends on the kernel config.
Building modules: ltp_acpi_cmds.c
Building modules: ltp_tpci.c
Building modules: ltp_tbio.c
---
package/ltp-testsuite/ltp-testsuite.mk | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/package/ltp-testsuite/ltp-testsuite.mk b/package/ltp-testsuite/ltp-testsuite.mk
index 8adfdef68d69..e9202afbbf3f 100644
--- a/package/ltp-testsuite/ltp-testsuite.mk
+++ b/package/ltp-testsuite/ltp-testsuite.mk
@@ -13,6 +13,14 @@ LTP_TESTSUITE_CONF_OPTS += \
--with-power-management-testsuite \
--with-realtime-testsuite
+ifeq ($(BR2_LINUX_KERNEL),y)
+LTP_TESTSUITE_DEPENDENCIES += linux
+LTP_TESTSUITE_MAKE_ENV = $(LINUX_MAKE_FLAGS)
+LTP_TESTSUITE_CONF_OPTS += --with-linux-dir=$(LINUX_DIR)
+else
+LTP_TESTSUITE_CONF_OPTS += --without-modules
+endif
+
# Needs libcap with file attrs which needs attr, so both required
ifeq ($(BR2_PACKAGE_LIBCAP)$(BR2_PACKAGE_ATTR),yy)
LTP_TESTSUITE_DEPENDENCIES += libcap
--
2.8.1
next prev parent reply other threads:[~2016-04-05 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 14:02 [Buildroot] [PATCH] ltp-testsuite: build kernel modules when appropriate Mason
2016-03-24 21:25 ` Thomas Petazzoni
2016-03-28 12:49 ` Mason
2016-03-29 19:12 ` Arnout Vandecappelle
2016-04-04 13:08 ` [Buildroot] [PATCH v2] " Mason
2016-04-05 9:23 ` Arnout Vandecappelle
2016-04-05 11:09 ` Mason [this message]
2016-04-14 19:29 ` [Buildroot] [PATCH v3] " Mason
2016-04-18 19:42 ` Thomas Petazzoni
2016-04-18 20:03 ` Mason
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=57039CF4.5060902@free.fr \
--to=slash.tmp@free.fr \
--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