summaryrefslogtreecommitdiff
path: root/mk/rte.cpuflags.mk
diff options
context:
space:
mode:
authorSimon Kagstrom <simon.kagstrom@netinsight.net>2015-11-24 08:50:01 +0100
committerThomas Monjalon <thomas.monjalon@6wind.com>2015-12-04 20:10:35 +0100
commit9aa2053c6e81493b23346ff4e387903560de5c81 (patch)
tree556f20f5b4113c19999c63757327c99a5d72bcbf /mk/rte.cpuflags.mk
parentebfd02be8a956536d34d8bf57dc17d152dfaf272 (diff)
downloaddpdk-9aa2053c6e81493b23346ff4e387903560de5c81.zip
dpdk-9aa2053c6e81493b23346ff4e387903560de5c81.tar.gz
dpdk-9aa2053c6e81493b23346ff4e387903560de5c81.tar.xz
mk: influence CPU flags with user input
We have encountered a CPU where the AES-NI instruction set is disabled due to export restrictions. Since the build machine and target machine is different, using -native configs doesn't work, and on this CPU, the application refuses to run due to the AES CPU flags being amiss. The patch passes EXTRA_CFLAGS to the figure-out-cpu-flags helper, which allows us to add -mno-aes to the compile flags and resolve this problem. Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net> Acked-by: Olivier Matz <olivier.matz@6wind.com>
Diffstat (limited to 'mk/rte.cpuflags.mk')
-rw-r--r--mk/rte.cpuflags.mk2
1 files changed, 1 insertions, 1 deletions
diff --git a/mk/rte.cpuflags.mk b/mk/rte.cpuflags.mk
index 0a340a9..c6bb8de 100644
--- a/mk/rte.cpuflags.mk
+++ b/mk/rte.cpuflags.mk
@@ -33,7 +33,7 @@
# used to set the RTE_CPUFLAG_* environment variables giving details
# of what instruction sets the target cpu supports.
-AUTO_CPUFLAGS := $(shell $(CC) $(MACHINE_CFLAGS) -dM -E - < /dev/null)
+AUTO_CPUFLAGS := $(shell $(CC) $(MACHINE_CFLAGS) $(EXTRA_CFLAGS) -dM -E - < /dev/null)
# adding flags to CPUFLAGS