From: Thomas F Herbert <therbert@redhat.com>
To: "users@dpdk.org" <dev@dpdk.org>
Cc: "rpm_dpdk@lists.fd.io" <rpm_dpdk@lists.fd.io>,
"The CentOS developers mailing list." <centos-devel@centos.org>
Subject: [dpdk-dev] [dpdk-users]Problem compiling dpdk on Centos aarch64
Date: Mon, 18 Jun 2018 11:37:48 -0400 [thread overview]
Message-ID: <a2b83a5b-3aa2-fe84-640e-d8b7e383cb84@redhat.com> (raw)
When compiling dpdk for aarch64 on Centos, I receive compilation error.
I see this in the Centos 1804 distribution.
I haven't tried locally n F28 but I see buildlogs in Fedora28 for dpdk.
I have also reproduced it in qemu-system aarch64 emulation:
uname -a
Linux aarch64-centos7 4.14.0-49.2.2.el7a.aarch64 #1 SMP Sat May 19
18:51:40 BST 2018 aarch64 aarch64 aarch64 GNU/Linux
l3fwd_em.c:245:2: error: #error No vector engine (SSE, NEON, ALTIVEC)
available, check your toolchain
#error No vector engine (SSE, NEON, ALTIVEC) available, check your
toolchain
Buildlogs show that dpdk built fine on Fedora 28/29.
--
*Thomas F Herbert*
NFV and Fast Data Planes
Networking Group Office of the CTO
*Red Hat*
reply other threads:[~2018-06-18 15:37 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=a2b83a5b-3aa2-fe84-640e-d8b7e383cb84@redhat.com \
--to=therbert@redhat.com \
--cc=centos-devel@centos.org \
--cc=dev@dpdk.org \
--cc=rpm_dpdk@lists.fd.io \
/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).