All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Shah, Rahul R" <rahul.r.shah@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] port: fix library build order dependency
Date: Thu, 7 Nov 2019 09:11:59 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E95CE7B@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20191105194210.5222-1-rahul.r.shah@intel.com>



> -----Original Message-----
> From: Shah, Rahul R <rahul.r.shah@intel.com>
> Sent: Tuesday, November 5, 2019 7:42 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org
> Subject: [PATCH] port: fix library build order dependency
> 
> The port library should be build after eventdev library.
> 
> Fixes: 	5d92c4e5 ("port: add eventdev port type")
> 
> Signed-off-by: Rahul Shah <rahul.r.shah@intel.com>
> ---
>  lib/Makefile | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/lib/Makefile b/lib/Makefile
> index 5d04ab915..2c2b80ac3 100644
> --- a/lib/Makefile
> +++ b/lib/Makefile
> @@ -90,6 +90,7 @@ DEPDIRS-librte_distributor := librte_eal librte_mbuf
> librte_ethdev
>  DIRS-$(CONFIG_RTE_LIBRTE_PORT) += librte_port
>  DEPDIRS-librte_port := librte_eal librte_mempool librte_mbuf librte_ethdev
>  DEPDIRS-librte_port += librte_ip_frag librte_sched
> +DEPDIRS-librte_port += librte_eventdev
>  ifeq ($(CONFIG_RTE_LIBRTE_KNI),y)
>  DEPDIRS-librte_port += librte_kni
>  endif
> --
> 2.20.1

Cosmetically, you might want to squeeze & add librte_eventdev on the line immediately above.

  reply	other threads:[~2019-11-07  9:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 19:42 [dpdk-dev] [PATCH] port: fix library build order dependency Rahul Shah
2019-11-07  9:11 ` Dumitrescu, Cristian [this message]
2019-11-07 14:19 ` 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=3EB4FA525960D640B5BDFFD6A3D891268E95CE7B@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=rahul.r.shah@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.