Go to file
Panu Matilainen 05dc7b05da port: fix build without KNI
Commit 9fc37d1c07 is missing a conditional in the dependencies,
causing builds to fail when KNI is not enabled:
    == Build lib/librte_port
      LD librte_port.so.3
    /usr/bin/ld: cannot find -lrte_kni
    collect2: error: ld returned 1 exit status

Fixes: 9fc37d1c07 ("port: support KNI")

Signed-off-by: Panu Matilainen <pmatilai@redhat.com>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2016-06-27 12:28:10 +02:00
app mk: fix parallel build of test resources 2016-06-24 16:57:27 +02:00
config mbuf: use default mempool handler from config 2016-06-24 11:01:05 +02:00
doc hash: add scalable multi-writer insertion with Intel TSX 2016-06-24 16:25:07 +02:00
drivers net/virtio-user: fix 32-bit build 2016-06-23 22:54:41 +02:00
examples examples/vhost: add client option 2016-06-22 09:47:12 +02:00
lib port: fix build without KNI 2016-06-27 12:28:10 +02:00
mk crypto/snow3g: rename libsso reference due to library update 2016-06-20 22:38:44 +02:00
pkg version: 16.04 2016-04-11 23:56:34 +02:00
scripts crypto/snow3g: rename libsso reference due to library update 2016-06-20 22:38:44 +02:00
tools tools: allow binding to other network class devices 2016-05-19 12:24:18 +02:00
.gitignore init DPDK repository 2013-03-07 10:57:42 +01:00
GNUmakefile drivers: create new directory 2015-05-22 15:51:38 +02:00
LICENSE.GPL doc: GPL/LGPL licenses 2013-07-25 14:43:06 +02:00
LICENSE.LGPL doc: fix file format (dos to unix) 2013-09-06 11:43:07 +02:00
MAINTAINERS crypto/kasumi: add driver for KASUMI library 2016-06-20 22:25:32 +02:00
Makefile remove trailing whitespaces 2014-06-11 00:29:34 +02:00
README doc: add readme file 2015-12-13 22:06:58 +01:00

DPDK is a set of libraries and drivers for fast packet processing.
It supports many processor architectures and both FreeBSD and Linux.

The DPDK uses the Open Source BSD license for the core libraries and
drivers. The kernel components are GPLv2 licensed.

Please check the doc directory for release notes,
API documentation, and sample application information.

For questions and usage discussions, subscribe to: users@dpdk.org
Report bugs and issues to the development mailing list: dev@dpdk.org