Public bug reported:
The DPDK build system uses the RTE_KERNELDIR make variable to determine
which kernel version to build for. DKMS provides the kernel version to
build for in the $kernelver and $kernel_source_dir variables. Because
you use a custom MAKE command, this must be used in the MAKE v
I tested the updated packages in a VM and it appears to have fixed the
issue. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687492
Title:
DPDK dkms packages build for wrong kernel
To mana
(this was found on yakkety)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653179
Title:
dpdk-dev incorrect symlink under $RTE_SDK
To manage notifications about this bug go to:
https://bugs.launchp
Public bug reported:
$ ls -l /usr/share/dpdk/x86_64-default-linuxapp-gcc/lib/librte_eal.a
ls: cannot access
'/usr/share/dpdk/x86_64-default-linuxapp-gcc/lib/librte_eal.a': No such file or
directory
$ ls -l
/usr/share/dpdk/x86_64-default-linuxapp-gcc/lib/x86_64-linux-gnu/librte_eal.a
-rw-r--r--
I apologize that I did not make this more clear.
The library files themselves are in the correct location, according to
the Ubuntu multiarch spec. The issue is that the symlink does *not*
point to the correct location.
The reason this works for the DPDK examples themselves (including l2fwd)
is b
dpdk-rte-kni-dkms-16.07.2-0ubuntu0.16.10.2 appears to fix the issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687492
Title:
