From: "Sanford, Robert" <rsanford@akamai.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: meson options - build vs target machine cpuflags question
Date: Thu, 10 Mar 2022 14:46:36 +0000 [thread overview]
Message-ID: <165CAE28-2A3E-4960-8E57-2EB9A19024DB@akamai.com> (raw)
Hello All,
We build a DPDK 21.05 app on Intel x86 machines with RDSEED in cpuflags, and may run it on machines *without* RDSEED.
This results in a fatal error ...
ERROR: This system does not support "RDSEED".
Please check that RTE_MACHINE is set correctly.
EAL: FATAL: unsupported cpu type.
I try adding -Dplatform=haswell when running meson, (because gcc man page indicates that haswell is last arch w/o RDSEED) but get the same result.
Until we resolve it, our workaround is changing the error-out in rte_cpu_is_supported() to just print a warning and continue.
We don't have direct access to automated build machines, we go through change request processes, and so we can't rapidly try too many things.
Is there a better meson option, such as machine=haswell, or something else that will work?
Thanks in advance,
Robert Sanford
next reply other threads:[~2022-03-10 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 14:46 Sanford, Robert [this message]
2022-03-10 22:54 ` Dan Gora
2022-03-10 22:58 ` Dan Gora
2022-03-10 23:39 ` Sanford, Robert
2022-03-11 0:00 ` Dan Gora
2022-03-11 1:18 ` Stephen Hemminger
2022-03-11 2:45 ` Dan Gora
2022-03-11 3:01 ` Stephen Hemminger
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=165CAE28-2A3E-4960-8E57-2EB9A19024DB@akamai.com \
--to=rsanford@akamai.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).