From: Thomas Monjalon <thomas@monjalon.net>
To: hemant.agrawal@nxp.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] mk: fix kernel modules build dependency
Date: Thu, 29 Mar 2018 17:39:31 +0200 [thread overview]
Message-ID: <20180329153931.26351-1-thomas@monjalon.net> (raw)
Some kernel modules may need some header files to be "installed"
in the build directory.
When running multiple threads of make, kernel modules can try to
be compiled before the lib headers are ready:
make -j3
kernel/linux/kni/kni_misc.c:19:37: fatal error:
exec-env/rte_kni_common.h: No such file or directory
This error appeared recently after moving kernel modules in their
own directory.
Fixes: acaa9ee991b5 ("move kernel modules directories")
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
On a related note, this header file
lib/librte_eal/linuxapp/eal/include/exec-env/rte_kni_common.h
could be moved to lib/librte_kni/
Opinion?
---
mk/rte.sdkbuild.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/mk/rte.sdkbuild.mk b/mk/rte.sdkbuild.mk
index 53e0721e9..5dc43e429 100644
--- a/mk/rte.sdkbuild.mk
+++ b/mk/rte.sdkbuild.mk
@@ -14,6 +14,7 @@ endif
-include $(RTE_SDK)/mk/exec-env/$(RTE_EXEC_ENV)/rte.custom.mk
buildtools: | lib
+kernel: | lib
drivers: | lib buildtools
app: | lib buildtools drivers
test: | lib buildtools drivers
--
2.16.2
next reply other threads:[~2018-03-29 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 15:39 Thomas Monjalon [this message]
2018-03-29 15:48 ` Ferruh Yigit
2018-03-29 16:32 ` Thomas Monjalon
2018-03-29 16:38 ` Ferruh Yigit
2018-03-29 16:43 ` Thomas Monjalon
2018-03-29 16:50 ` Ferruh Yigit
2018-03-29 17:01 ` Thomas Monjalon
2018-03-29 18:12 ` Hemant Agrawal
2018-03-29 18:28 ` Ferruh Yigit
2018-03-29 18:21 ` Ferruh Yigit
2018-03-29 18:43 ` Ferruh Yigit
2018-03-30 8:32 ` Thomas Monjalon
2018-03-30 10:15 ` Ferruh Yigit
2018-03-30 11:03 ` Thomas Monjalon
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=20180329153931.26351-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
/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;
as well as URLs for NNTP newsgroup(s).