From: David Marchand <david.marchand@redhat.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev <dev@dpdk.org>, "Yigit, Ferruh" <ferruh.yigit@intel.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] drivers: fix the event dependency on crypto
Date: Thu, 5 Mar 2020 09:04:22 +0100 [thread overview]
Message-ID: <CAJFAV8wn8Ajjo83K7rF+dRTsZibWp5_z1DTHTfCtbrUKL4jwbg@mail.gmail.com> (raw)
In-Reply-To: <20200305120412.16085-1-hemant.agrawal@nxp.com>
On Thu, Mar 5, 2020 at 7:32 AM Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
>
> Since the introduction of crypto event adapters, event drivers
> have dependencies on crypto drivers.
>
> /usr/bin/ld: cannot find -lrte_pmd_dpaa_sec
> collect2: error: ld returned 1 exit status
> make[9]: *** [.../mk/rte.lib.mk:100:
> librte_pmd_dpaa_event.so.20.0.2] Error 1
>
> Fixes: b0f66a68ca74 ("event/dpaa: support crypto adapter")
> Fixes: 3721c39f405a ("event/dpaa2: support crypto adapter")
> Cc: stable@dpdk.org
>
Reported-by: David Marchand <david.marchand@redhat.com>
> Suggested-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> drivers/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/Makefile b/drivers/Makefile
> index 46374ca69..c70bdf9cc 100644
> --- a/drivers/Makefile
> +++ b/drivers/Makefile
> @@ -21,7 +21,7 @@ DEPDIRS-compress := bus mempool
> DIRS-$(CONFIG_RTE_LIBRTE_VHOST) += vdpa
> DEPDIRS-vdpa := common bus mempool
> DIRS-$(CONFIG_RTE_LIBRTE_EVENTDEV) += event
> -DEPDIRS-event := common bus mempool net
> +DEPDIRS-event := common bus mempool net crypto
> DIRS-$(CONFIG_RTE_LIBRTE_RAWDEV) += raw
> DEPDIRS-raw := common bus mempool net event
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2020-03-05 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 12:04 Hemant Agrawal
2020-03-05 8:04 ` David Marchand [this message]
2020-03-05 13:56 ` David Marchand
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=CAJFAV8wn8Ajjo83K7rF+dRTsZibWp5_z1DTHTfCtbrUKL4jwbg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--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).