On 4/6/2017 3:09 PM, Thomas Monjalon wrote: > 2017-04-06 15:05, Ferruh Yigit: >> On 4/6/2017 2:59 PM, Thomas Monjalon wrote: >>> 2017-04-06 14:46, Ferruh Yigit: >>>> --- a/mk/toolchain/gcc/rte.toolchain-compat.mk >>>> +++ b/mk/toolchain/gcc/rte.toolchain-compat.mk >>>> @@ -89,4 +89,8 @@ else >>>> ifeq ($(shell test $(GCC_VERSION) -lt 42 && echo 1), 1) >>>> MACHINE_CFLAGS := $(filter-out -march% -mtune% >>>> -msse%,$(MACHINE_CFLAGS)) >>>> endif >>>> + >>>> + ifeq ($(shell test $(GCC_VERSION) -lt 47 && echo 1), 1) >>>> + CONFIG_RTE_LIBRTE_THUNDERX_NICVF_PMD=n >>>> + endif >>> >>> In previous version you were disabling the PMD inside the PMD Makefile. >>> It was better. >> >> Agreed, but I that is causing a build error in applications. I have >> missed it in previous release because an .a file was already created. >> >> So, need a way to disable linking pmd against application. > > I see. > > If it is disabled here, we won't see the warning in the PMD Makefile?
Oh, you are right, warnings in PMD Makefile become useless. I can set another flag in compat headers and check it in pmd makefile, will it be too much noise?
