From: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
To: dev@dpdk.org
Cc: stable@dpdk.org
Subject: [PATCH V2] examples/pipeline: fix include path for rte_log.h
Date: Tue, 13 Feb 2024 17:38:09 +0000 [thread overview]
Message-ID: <20240213173809.1536955-1-cristian.dumitrescu@intel.com> (raw)
In-Reply-To: <20240213145218.1532323-1-cristian.dumitrescu@intel.com>
When rte_log.h was moved to a new directory, the include path was not
updated for the generated C code produced by the pipeline library,
which results in build failure for this code.
Fixes: 09ce41310930 ("log: separate logging functions out of EAL")
Cc: stable@dpdk.org
Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
---
drivers/net/softnic/rte_eth_softnic_cli.c | 2 ++
examples/pipeline/cli.c | 2 ++
2 files changed, 4 insertions(+)
diff --git a/drivers/net/softnic/rte_eth_softnic_cli.c b/drivers/net/softnic/rte_eth_softnic_cli.c
index 085523fe03..95e705c553 100644
--- a/drivers/net/softnic/rte_eth_softnic_cli.c
+++ b/drivers/net/softnic/rte_eth_softnic_cli.c
@@ -337,6 +337,7 @@ cmd_softnic_pipeline_libbuild(struct pmd_internals *softnic __rte_unused,
"-I %s/lib/eal/include "
"-I %s/lib/eal/x86/include "
"-I %s/lib/eal/include/generic "
+ "-I %s/lib/log "
"-I %s/lib/meter "
"-I %s/lib/port "
"-I %s/lib/table "
@@ -361,6 +362,7 @@ cmd_softnic_pipeline_libbuild(struct pmd_internals *softnic __rte_unused,
install_dir,
install_dir,
install_dir,
+ install_dir,
log_file,
obj_file,
lib_file,
diff --git a/examples/pipeline/cli.c b/examples/pipeline/cli.c
index 2ae6cc579f..afb143c01f 100644
--- a/examples/pipeline/cli.c
+++ b/examples/pipeline/cli.c
@@ -714,6 +714,7 @@ cmd_pipeline_libbuild(char **tokens,
"-I %s/lib/eal/include "
"-I %s/lib/eal/x86/include "
"-I %s/lib/eal/include/generic "
+ "-I %s/lib/log "
"-I %s/lib/meter "
"-I %s/lib/port "
"-I %s/lib/table "
@@ -738,6 +739,7 @@ cmd_pipeline_libbuild(char **tokens,
install_dir,
install_dir,
install_dir,
+ install_dir,
log_file,
obj_file,
lib_file,
--
2.34.1
next prev parent reply other threads:[~2024-02-13 17:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 14:52 [PATCH] " Cristian Dumitrescu
2024-02-13 16:18 ` David Marchand
2024-02-13 17:22 ` Dumitrescu, Cristian
2024-02-13 17:38 ` Cristian Dumitrescu [this message]
2024-02-14 11:22 ` [PATCH V2] " Ferruh Yigit
2024-02-14 16:25 ` Aaron Conole
2024-02-14 19:32 ` Patrick Robb
2024-02-14 20:00 ` Dumitrescu, Cristian
2024-02-14 20:17 ` Patrick Robb
2024-07-16 16:33 ` Patrick Robb
2024-07-17 10:10 ` Ferruh Yigit
2024-02-14 17:22 ` Dumitrescu, Cristian
2024-02-15 12:17 ` Ferruh Yigit
2024-02-15 13:32 ` Ferruh Yigit
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=20240213173809.1536955-1-cristian.dumitrescu@intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).