From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw112064 [PATCH] Fix RISC-V builds
Date: Mon, 30 May 2022 10:28:12 -0400 (EDT) [thread overview]
Message-ID: <20220530142812.046C96D4C2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/112064
_apply patch failure_
Submitter: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Date: Monday, May 30 2022 14:11:03
Applied on: CommitID:64fcadeac0f70c8c9c215196a3d580b4ad37dcdc
Apply patch set 112064 failed:
Checking patch meson.build...
error: while searching for:
# set up some global vars for compiler, platform, configuration, etc.
cc = meson.get_compiler('c')
add_project_arguments('-march=native', language: 'c')
if get_option('enable-avx') and cc.has_argument('-mavx')
add_project_arguments('-mavx', language: 'c')
error: patch failed: meson.build:17
Applying patch meson.build with 1 reject...
Rejected hunk #1.
diff a/meson.build b/meson.build (rejected hunks)
@@ -17,7 +17,10 @@ pktgen_conf = configuration_data()
# set up some global vars for compiler, platform, configuration, etc.
cc = meson.get_compiler('c')
-add_project_arguments('-march=native', language: 'c')
+target = target_machine.cpu_family()
+if (target != 'riscv64')
+ add_project_arguments('-march=native', language: 'c')
+endif
if get_option('enable-avx') and cc.has_argument('-mavx')
add_project_arguments('-mavx', language: 'c')
https://lab.dpdk.org/results/dashboard/patchsets/22358/
UNH-IOL DPDK Community Lab
next reply other threads:[~2022-05-30 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 14:28 dpdklab [this message]
[not found] <20220530141103.42444-1-heinrich.schuchardt@canonical.com>
2022-05-30 14:11 ` checkpatch
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=20220530142812.046C96D4C2@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).