> libnuma is a default dependency for DPDK 17.11 because
> CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES and CONFIG_RTE_LIBRTE_VHOST_NUMA are
> enabled by default for most architectures.
> libnuma-dev package installation fixes the DPDK build:
> 
>       eal_memory.c:56:18: fatal error:
>               numa.h: No such file or directory
> 
> CC: Mark Kavanagh <[email protected]>
> Fixes: 5e925ccc2a6f ("netdev-dpdk: DPDK v17.11 upgrade")
> Signed-off-by: Ilya Maximets <[email protected]>
> ---
>  .travis.yml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/.travis.yml b/.travis.yml
> index f217840..48acc8e 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -15,6 +15,7 @@ addons:
>        - llvm-dev
>        - libjemalloc1
>        - libjemalloc-dev
> +      - libnuma-dev
>        - python-sphinx
> 
>  before_install: ./.travis/${TRAVIS_OS_NAME}-prepare.sh


Verified with travis on my side.

As with part 1 of the patch set set I'm thinking it's better to merge this to 
master instead of dpdk_merge branch so as to enable the travis builds for dpdk?

Acked-by: Ian Stokes <[email protected]>
Tested-by: Ian Stokes <[email protected]>

> --
> 2.7.4

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to