From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: <dev@dpdk.org>
Cc: <olivier.matz@6wind.com>, <akhil.goyal@nxp.com>,
<thomas@monjalon.net>, <ferruh.yigit@intel.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: [dpdk-dev] [PATCH 1/2] drivers: fix shared build error for DPAA crypto
Date: Thu, 26 Oct 2017 19:39:05 +0530 [thread overview]
Message-ID: <20171026140906.10347-1-shreyansh.jain@nxp.com> (raw)
Various symbols are being used by DPAA Crypto driver which were not exposed
from DPAA bus during initial version. This breaks the shared build.
This patch also adds the LDLIBS line required after (cbc12b0a9) patch.
Fixes: c3e85bdcc6e6 ("crypto/dpaa_sec: add crypto driver for NXP DPAA platform")
Cc: akhil.goyal@nxp.com
Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
---
drivers/bus/dpaa/rte_bus_dpaa_version.map | 9 +++++++++
drivers/crypto/dpaa_sec/Makefile | 2 ++
2 files changed, 11 insertions(+)
diff --git a/drivers/bus/dpaa/rte_bus_dpaa_version.map b/drivers/bus/dpaa/rte_bus_dpaa_version.map
index 64a05a9..fb9d532 100644
--- a/drivers/bus/dpaa/rte_bus_dpaa_version.map
+++ b/drivers/bus/dpaa/rte_bus_dpaa_version.map
@@ -40,14 +40,23 @@ DPDK_17.11 {
fman_ip_rev;
netcfg_acquire;
netcfg_release;
+ of_find_compatible_node;
+ of_get_property;
+ qm_channel_caam;
qman_create_fq;
qman_dequeue;
qman_dqrr_consume;
+ qman_enqueue;
qman_enqueue_multi;
+ qman_fq_fqid;
+ qman_fq_state;
qman_global_init;
qman_init_fq;
+ qman_poll_dqrr;
+ qman_query_fq_np;
qman_set_vdq;
qman_reserve_fqid_range;
+ qman_volatile_dequeue;
rte_dpaa_driver_register;
rte_dpaa_driver_unregister;
rte_dpaa_mem_ptov;
diff --git a/drivers/crypto/dpaa_sec/Makefile b/drivers/crypto/dpaa_sec/Makefile
index 9a061b4..17bc79c 100644
--- a/drivers/crypto/dpaa_sec/Makefile
+++ b/drivers/crypto/dpaa_sec/Makefile
@@ -53,6 +53,8 @@ CFLAGS += -I$(RTE_SDK)/drivers/crypto/dpaa_sec/
CFLAGS += -I$(RTE_SDK)/drivers/crypto/dpaa2_sec/
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/common/include
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/linuxapp/eal
+LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
+LDLIBS += -lrte_cryptodev
# versioning export map
EXPORT_MAP := rte_pmd_dpaa_sec_version.map
--
2.9.3
next reply other threads:[~2017-10-26 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 14:09 Shreyansh Jain [this message]
2017-10-26 14:09 ` [dpdk-dev] [PATCH 2/2] drivers: fix shared build error for dpaa2 event Shreyansh Jain
2017-10-26 14:10 ` [dpdk-dev] [PATCH 1/2] drivers: fix shared build error for DPAA crypto Akhil Goyal
2017-10-26 21:06 ` 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=20171026140906.10347-1-shreyansh.jain@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.com \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).