06/09/2017 12:25, De Lara Guarch, Pablo: > From: Akhil Goyal [mailto:akhil.go...@nxp.com] > > > > Hi Pablo, > > On 9/4/2017 8:18 PM, De Lara Guarch, Pablo wrote: > > > From: Akhil Goyal [mailto:akhil.go...@nxp.com] > > >> --- a/config/defconfig_arm64-dpaa2-linuxapp-gcc > > >> +++ b/config/defconfig_arm64-dpaa2-linuxapp-gcc > > >> @@ -90,3 +90,9 @@ > > >> CONFIG_RTE_DPAA2_SEC_PMD_MAX_NB_SESSIONS=2048 > > >> # > > >> CONFIG_RTE_LIBRTE_PMD_DPAA2_EVENTDEV=y > > >> CONFIG_RTE_LIBRTE_PMD_DPAA2_EVENTDEV_DEBUG=n > > >> + > > >> +# > > >> +# Compile PMD for Software backed device # > > >> +CONFIG_RTE_LIBRTE_PMD_OPENSSL=y > > >> CONFIG_RTE_LIBRTE_PMD_OPENSSL_DEBUG=n > > >> -- > > >> 2.9.3 > > > > > > Is OpenSSL installed by default in that system, so this can be enabled by > > default for this target? > > > > > yes this is installed by default. > > Thanks for the reply. > > Applied to dpdk-next-crypto. > Thanks,
Where is it installed by default? On your machine? In your build system? It is at least not installed on my machine when I compile this target. This file is a defconfig, not your preferred config. This patch should be dropped.
