DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Nipun Gupta <nipun.gupta@nxp.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Dependency issue between event/dpaa and crypto/dpaa_sec
Date: Thu, 30 Jan 2020 12:01:58 +0100	[thread overview]
Message-ID: <CAJFAV8zaHorokgF5vcX=_FudXcbP9PZOhaDre6G6JCgksMLLJQ@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0401MB2541E8D0883AE57703DC355A89040@VI1PR0401MB2541.eurprd04.prod.outlook.com>

On Thu, Jan 30, 2020 at 11:53 AM Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
>         Can you elaborate more, how are you compiling? are you using the v19.11.0 tag?
> event/dpaa is dependent on crypto/dpaa_sec
>
> but code do take care of it.

Yes, the v19.11 tag.
Using ./devtools/test-build.sh, and I hit the issue once with the
i686-native-linux-gcc+shared+debug+default.


I could not find a dependency in the makefiles for this.
But meson has this dependency.

drivers/event/dpaa/meson.build
deps += ['pmd_dpaa', 'pmd_dpaa_sec']


I suppose I can catch it because I build with -j28.
I have been burning^Wcompiling a lot, those weeks, but this is the
first time I caught it.


-- 
David Marchand


  reply	other threads:[~2020-01-30 11:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30  8:31 David Marchand
2020-01-30 10:53 ` Hemant Agrawal
2020-01-30 11:01   ` David Marchand [this message]
2020-02-13 12:06     ` Hemant Agrawal
2020-02-13 12:16       ` David Marchand
2020-02-21 14:31         ` 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='CAJFAV8zaHorokgF5vcX=_FudXcbP9PZOhaDre6G6JCgksMLLJQ@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=nipun.gupta@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).