On 10/11/2018 02:13 PM, Hongxu Jia wrote: > On 2018年10月11日 13:53, Hongxu Jia wrote: >> On 2018年10月11日 13:21, Anuj Mittal wrote: >>> I think we shouldn't be building with -march=corei7 (which is what it >>> will do if you remove HOST_CC_ARCH) if the underlying hardware doesn't >>> support it. It probably wouldn't even work since default value is >>> core2duo for qemu in tune-core2.inc which doesn't support SSE 4.2 (which >>> is a requirement for dpdk). >>> >>> In my opinion, we should keep HOST_CC_ARCH and anyone using dpdk should >>> make sure that they define COMPATIBLE_MACHINE and DPDK_TARGET_MACHINE >>> properly depending on the arch that they are building for. Does that >>> make sense? >> How about remove `-march=corei7' from default value >> --- a/mk/machine/default/rte.vars.mk >> +++ b/mk/machine/default/rte.vars.mk >> @@ -26,5 +26,3 @@ >> # CPU_CFLAGS = >> # CPU_LDFLAGS = >> # CPU_ASFLAGS = >> - >> -MACHINE_CFLAGS += -march=corei7 >> > After build test, directly remove it doesn't work, the error is still here, > as you said, let customer define COMPATIBLE_MACHINE and DPDK_TARGET_MACHINE >
Yes, setting DPDK_TARGET_MACHINE to the correct/same -march value as the one defined by the MACHINE for which it is being built should work (assuming dpdk supports it). Thanks for checking, Anuj -- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
