From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 88FA1A034E for ; Mon, 14 Mar 2022 11:51:54 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8438541150; Mon, 14 Mar 2022 11:51:54 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id 65B7940DDD; Mon, 14 Mar 2022 11:51:52 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id CA36D5C0158; Mon, 14 Mar 2022 06:51:51 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 14 Mar 2022 06:51:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; bh=m0SLgdSxEKj9p6 yIPZhEGAOglT/DFZuCl+HEpcjvjVs=; b=pHkGSOXfC08R+FAM4GpTcGUphTHv3C R0pvubV1yIMpZFE0r0TtaIaIIT7oVdCTh0zpNFdT/4AjaupNAqTJHWWYuh4UKT7H d3UanYRCrlPXMZwBYKz0OzUlOeUoW3YhkDXp57YuliFVuCZylaiawf++RuUl/d68 5OBm5xFK1eq+l5mW11oskuGsr+zNPILP8CKXBJi5OMWD8XNIrvNO7Yl0iCsJ17pz Cj3ITdYNZLxkGAHgjBapixfGlt5hKb3oVHBhkyi6SLeXBEVAx/F2XLlyStx9AG0H n5y2gd65L1fLKiPAYVfRv6z6Kty3NzP8J+aPMx+2s06D1xlo+cG1Bhkg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=m0SLgdSxEKj9p6yIPZhEGAOglT/DFZuCl+HEpcjvj Vs=; b=XXBWovxMkgnoR5pYxzw3lOshQ+J7C1UO5S6GPpd6ygQo4unXUh3I/VUTJ bZoCao+IgYsySe9oUlD3N3k7mIYU59Xp/yv3Iju7xIQCFE/BeC86ReMITzrHLFSk P6cZLmyM+7Dq92A3YPMreXmz7oMkTtKkouZkv7NzJgCOqaPAT60VD+vKuila6KRV Nhj5XzMCwABatY7f+vB7TpU4IiLOAUzmNkC+A0zt70YeQ1cnC4fSmGPcQLTtUFAE AZjo29WDI6zdUzcjs6WuUl6qkDI7m8HL/mfI/xi1mTtPnllLNr/DLkfB5dW3hNhT +OQieX/9xXlr0H0VU5wm8xgW0PrYg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvkedgudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepgeejfffhhfeghfetveffgeffteelveekhffghfefgedvleeuveet fffgudelvefhnecuffhomhgrihhnpehgihhthhhusgdrtghomhenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 14 Mar 2022 06:51:50 -0400 (EDT) From: Thomas Monjalon To: David Marchand Cc: dev@dpdk.org, blo@iol.unh.edu, stable@dpdk.org, Konstantin Ananyev , Ferruh Yigit , Stephen Hemminger Subject: Re: [PATCH] bpf: fix build with some libpcap version on FreeBSD Date: Mon, 14 Mar 2022 11:51:49 +0100 Message-ID: <109819028.nniJfEyVGO@thomas> In-Reply-To: <20220310105458.24ee6d94@hermes.local> References: <20220310183040.31724-1-david.marchand@redhat.com> <20220310105458.24ee6d94@hermes.local> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org 10/03/2022 19:54, Stephen Hemminger: > On Thu, 10 Mar 2022 19:30:40 +0100 > David Marchand wrote: > > > This is something caught in UNH FreeBSD env. > > > > For some reason [1], the pcap/bpf.h header started to define _BPF_H_. > > > > It happens that the bpf_impl.h internal DPDK header uses this define as > > an internal guard. > > This triggers a build failure in bpf_convert.c which can't find > > RTE_BPF_LOG macro. > > > > Fix the include guard to use the filename and remove _. > > > > 1: https://github.com/the-tcpdump-group/libpcap/pull/1074 > > > > Fixes: 94972f35a02e ("bpf: add BPF loading and execution framework") > > Cc: stable@dpdk.org > > > > Signed-off-by: David Marchand > > Acked-by: Stephen Hemminger Applied, thanks.