From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw63750build: fix soname info for 19.11 compatiblity
Date: 24 Jan 2020 02:36:01 -0800 [thread overview]
Message-ID: <ee68f5$95qa1q@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/63750
_apply issues_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: 2019-12-11 10:26:42
Reply_mail: 20191211102642.983579-1-bruce.richardson@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: c465e6b94be343303303f26b95f3c2ae4969063e
*Repo: dpdk
Checking patch ABI_VERSION...
error: while searching for:
20.1
error: patch failed: ABI_VERSION:1
error: ABI_VERSION: patch does not apply
Checking patch drivers/meson.build...
error: while searching for:
if is_experimental != 0
--
endif
# now build the static driver
static_lib = static_library(lib_name,
error: patch failed: drivers/meson.build:132
error: drivers/meson.build: patch does not apply
Checking patch lib/meson.build...
error: while searching for:
if is_experimental != 0
--
endif
# first build static lib
static_lib = static_library(libname,
error: patch failed: lib/meson.build:113
error: lib/meson.build: patch does not apply
Checking patch mk/rte.lib.mk...
error: while searching for:
endif
ifeq ($(CONFIG_RTE_BUILD_SHARED_LIB),y)
LIB := $(patsubst %.a,%.so.$(LIBABIVER),$(LIB))
ifeq ($(EXTLIB_BUILD),n)
CPU_LDFLAGS += --version-script=$(SRCDIR)/$(EXPORT_MAP)
error: patch failed: mk/rte.lib.mk:19
error: mk/rte.lib.mk: patch does not apply
DPDK STV team
next reply other threads:[~2020-01-24 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 10:36 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-12 8:14 sys_stv
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$95qa1q@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).