From: "Wiles, Keith" <keith.wiles@intel.com>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] RTE_MACHINE_TYPE Error
Date: Tue, 9 Oct 2018 13:54:08 +0000 [thread overview]
Message-ID: <2099488D-C9CD-4989-AF1F-18EA9F558717@intel.com> (raw)
In-Reply-To: <CA+Gp1nZj_GFsuho11OPJ0dUcS_URJHseLFcgGCir4k2po5-9-g@mail.gmail.com>
> On Oct 8, 2018, at 11:10 PM, Cliff Burdick <shaklee3@gmail.com> wrote:
>
> Hi, I'm trying to compile on a machine with an older-generation xeon than
> the target, so I'm using CONFIG_RTE_MACHINE="broadwell" in the config.
> gcc's options show that broadwell supports the AES flag, and I verified
> that the build shows -march=broadwell. However, when I run my application
> it prints immediately:
>
> ERROR: This system does not support "AES".
> Please check that RTE_MACHINE is set correctly.
> EAL: FATAL: unsupported cpu type.
> EAL: unsupported cpu type.
> EAL: Error - exiting with code: 1
> Cause: Error with EAL initialization
>
> This is gcc 7, so it supports that flag. Does anyone know how I can compile
> for a later architecture on an older machine?
Have you checked to make sure the CPU does support the feature by looking that the CPU flags in /proc/cpuinfo ?
Normally this is the reason the code will not run is the CPU does not support it.
Regards,
Keith
next prev parent reply other threads:[~2018-10-09 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 4:10 Cliff Burdick
2018-10-09 13:54 ` Wiles, Keith [this message]
2018-10-09 14:37 ` Cliff Burdick
2018-10-09 14:56 ` Cliff Burdick
2018-10-09 19:59 ` Wiles, Keith
2018-10-09 20:45 ` Cliff Burdick
2018-10-09 19:58 ` Wiles, Keith
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=2099488D-C9CD-4989-AF1F-18EA9F558717@intel.com \
--to=keith.wiles@intel.com \
--cc=shaklee3@gmail.com \
--cc=users@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).