From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65751[v4, 6/6] net/mlx: fix overlinking with meson and glue dlopen
Date: 22 Feb 2020 08:35:54 -0800 [thread overview]
Message-ID: <ee68f5$9dm8hr@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65751
_apply issues_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: 2020-02-12 01:59:44
Reply_mail: 20200212015944.3037000-7-thomas@monjalon.net
DPDK git baseline:
Repo:dpdk-next-net, CommitID: 5d24d6a55025c58ae9e890851e21cb861839cb66
Repo:dpdk, CommitID: 08ab4769c2b868143536ea3d1807e9a25647fd9e
*Repo: dpdk-next-net
if not static_ibverbs
ext_deps += lib
endif
else
error: patch failed: drivers/common/mlx5/meson.build:29
error: drivers/common/mlx5/meson.build: patch does not apply
Checking patch drivers/net/mlx4/meson.build...
error: while searching for:
endif
if lib.found()
--
if not static_ibverbs
ext_deps += lib
endif
else
error: patch failed: drivers/net/mlx4/meson.build:30
error: drivers/net/mlx4/meson.build: patch does not apply
*Repo: dpdk
if not static_ibverbs
ext_deps += lib
endif
else
error: patch failed: drivers/common/mlx5/meson.build:29
error: drivers/common/mlx5/meson.build: patch does not apply
Checking patch drivers/net/mlx4/meson.build...
error: while searching for:
endif
if lib.found()
--
if not static_ibverbs
ext_deps += lib
endif
else
error: patch failed: drivers/net/mlx4/meson.build:30
error: drivers/net/mlx4/meson.build: patch does not apply
DPDK STV team
reply other threads:[~2020-02-22 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='ee68f5$9dm8hr@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@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).