From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: thomas@monjalon.net
Subject: [dpdk-test-report] |FAILURE| pw39077 [PATCH 1/2] eal: fix build with glibc < 2.16
Date: 09 May 2018 10:06:01 -0700 [thread overview]
Message-ID: <f7a79a$1mjldm@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/39077
_apply patch file failure_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Fri, 27 Apr 2018 04:43:41 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:db3d585ff859251586f24f2bf60ffc276da01cda
Repo:dpdk-next-crypto, Branch:master, CommitID:440aa0ad8b89d9af5d68737dd79b1b7ae7ed5fb4
Repo:dpdk-next-net, Branch:master, CommitID:69e1d3bb2bc1dd3035b317522d3f03dc47e20324
Repo:dpdk-next-virtio, Branch:master, CommitID:037c0996bc927342f157426739e0cb63f2db8689
Repo:dpdk, Branch:master, CommitID:67af7ecc52ec0abdec3e9d5b35dcd4dc78b595ce
Apply patch file failed:
Repo: dpdk
39077:
patching file lib/librte_eal/common/eal_common_cpuflags.c
Hunk #1 FAILED at 22.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_cpuflags.c.rej
Repo: dpdk-next-crypto
39077:
patching file lib/librte_eal/common/eal_common_cpuflags.c
Hunk #1 FAILED at 22.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_cpuflags.c.rej
Repo: dpdk-next-net
39077:
patching file lib/librte_eal/common/eal_common_cpuflags.c
Hunk #1 FAILED at 22.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_cpuflags.c.rej
Repo: dpdk-next-virtio
39077:
patching file lib/librte_eal/common/eal_common_cpuflags.c
Hunk #1 FAILED at 22.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_cpuflags.c.rej
Repo: dpdk-next-eventdev
39077:
patching file lib/librte_eal/common/eal_common_cpuflags.c
Hunk #1 FAILED at 22.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_cpuflags.c.rej
DPDK STV team
reply other threads:[~2018-05-09 17:06 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='f7a79a$1mjldm@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).