DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Pascal Mazon <pascal.mazon@6wind.com>,
	Jan Viktorin <viktorin@rehivetech.com>,
	Jianbo Liu <jianbo.liu@arm.com>
Subject: [dpdk-dev]  [PATCH] net/tap: fix build issue with ARM32
Date: Wed, 31 Jan 2018 10:44:08 +0530	[thread overview]
Message-ID: <20180131051408.3652-1-jerin.jacob@caviumnetworks.com> (raw)

arm32 Linux does not support eBPF interface.
Since tap PMD driver has a dependency on eBPF(the symbol __NR_bpf),
disabling it armv7 config.

compilation error log:
In file included from /tmp/dpdk/drivers/net/tap/tap_bpf_api.c:15:0:
/tmp/dpdk/drivers/net/tap/tap_bpf.h:103:4: error: #error __NR_bpf not
defined
 #  error __NR_bpf not defined
    ^
/tmp/dpdk/drivers/net/tap/tap_bpf_api.c: In function ‘sys_bpf’:
/tmp/dpdk/drivers/net/tap/tap_bpf_api.c:92:17: error: ‘__NR_bpf’
undeclared (first use in this function)
  return syscall(__NR_bpf, cmd, attr, size);
                 ^
/tmp/dpdk/drivers/net/tap/tap_bpf_api.c:92:17: note: each undeclared
identifier is reported only once for each function it appears in
/tmp/dpdk/drivers/net/tap/tap_bpf_api.c:93:1: error: control reaches
end of non-void function [-Werror=return-type]
 }
 ^
cc1: all warnings being treated as errors

Fixes: b02d85e1 ("net/tap: add eBPF API")

Cc: Pascal Mazon <pascal.mazon@6wind.com>
Cc: Jan Viktorin <viktorin@rehivetech.com>
Cc: Jianbo Liu <jianbo.liu@arm.com>

Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
 config/defconfig_arm-armv7a-linuxapp-gcc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config/defconfig_arm-armv7a-linuxapp-gcc b/config/defconfig_arm-armv7a-linuxapp-gcc
index a20b7a85f..4a55bb397 100644
--- a/config/defconfig_arm-armv7a-linuxapp-gcc
+++ b/config/defconfig_arm-armv7a-linuxapp-gcc
@@ -80,3 +80,4 @@ CONFIG_RTE_LIBRTE_BNX2X_PMD=n
 CONFIG_RTE_LIBRTE_QEDE_PMD=n
 CONFIG_RTE_LIBRTE_SFC_EFX_PMD=n
 CONFIG_RTE_LIBRTE_AVP_PMD=n
+CONFIG_RTE_LIBRTE_PMD_TAP=n
-- 
2.16.1

             reply	other threads:[~2018-01-31  5:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  5:14 Jerin Jacob [this message]
2018-01-31  9:59 ` Ophir Munk
2018-01-31 10:23   ` Jerin Jacob
2018-01-31 10:38     ` Ophir Munk
2018-01-31 11:19       ` Thomas Monjalon
2018-01-31 11:30       ` Jerin Jacob
2018-01-31 11:57         ` Ophir Munk
2018-01-31 12:40           ` Jerin Jacob

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180131051408.3652-1-jerin.jacob@caviumnetworks.com \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=jianbo.liu@arm.com \
    --cc=pascal.mazon@6wind.com \
    --cc=thomas@monjalon.net \
    --cc=viktorin@rehivetech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).