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 D5E9B46A9D; Mon, 30 Jun 2025 16:28:30 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9233D402CB; Mon, 30 Jun 2025 16:28:30 +0200 (CEST) Received: from fhigh-a3-smtp.messagingengine.com (fhigh-a3-smtp.messagingengine.com [103.168.172.154]) by mails.dpdk.org (Postfix) with ESMTP id A75DC402CB for ; Mon, 30 Jun 2025 16:28:28 +0200 (CEST) Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfhigh.phl.internal (Postfix) with ESMTP id 29320140019D; Mon, 30 Jun 2025 10:28:28 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-09.internal (MEProxy); Mon, 30 Jun 2025 10:28:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1751293708; x=1751380108; bh=V8rYaseW3jxdR1nyu6Ls1JR19psD07iwXwKZv37my+8=; b= ESjz9sBLou6F3bSUUoUSTPJicAUV20MJ7YeVDqI9LTbBi3S8eSWznfNE//Y8Jqpe 6zW6i9iJivSVzSSn+KabGJ+lzRvAjpgCMYYr7wnjfwCU2OLPFomFtmURNNwPzgjk OE0v7qDHCPGQv7uagA0JVlzWHC7jPtuAiiuOm1Yddu37GFlQlFA5kHarSaka58xZ sbEhZj5b70YQabNmn3F0/21VNOqlUNOyIH9OGjXpzmZk6T7Wls04cqBUoAEJ0kqQ 5o2x3uKavlGYFTWLevaHlirpzDco8B1lKeWAdcb6gXOp8q0Uxx75SAp7mF6lCC5U u9zR+bYqIgoXfFVTyRt1bw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1751293708; x= 1751380108; bh=V8rYaseW3jxdR1nyu6Ls1JR19psD07iwXwKZv37my+8=; b=k 7n2THJ1TG1Js6dZdR1mnpAGV71UgQIFd14+5vZj8DwX22kbMlsyTe9bAezM2gkAQ BLbae5YtcV1yQ9Uv3H+3yb+Ei5tuhZHuEhw2M/k3jrNG7VlWFdOozcB+h9LZd1xa Ge3igzebmgRx7wohxTEGgV3KA+TJBGAzResxIsutCfGarIeesSWYE8fZHAdRWh6K 48/RTbji+t9ndLVycDI4WCKOEUjvfNLUzj5tbUFw2Ci50KbJjgEV7yo9jhejGeBg junpTB4NRmKPQHwrJi4GoquyzTxVSnEoOsvR+/5HaGw04PvIrMpSs292v+6pbbdy 9rqBC8n4SYquDwIX1pG6A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdduudelgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefhvfevufffkfgjfhgggfgtsehtufertddttdejnecuhfhrohhmpefvhhhomhgrshcu ofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuggftrf grthhtvghrnhepjeduveehieevuddutdevfffgtdegkeeuveejffejgedtgeegkefgvdeu gfefkeejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthdpnhgspghrtghpthhtohepkedpmhho uggvpehsmhhtphhouhhtpdhrtghpthhtohepshgthhhnvghiuggvsehqthhirdhquhgrlh gtohhmmhdrtghomhdprhgtphhtthhopeguvghvseguphgukhdrohhrghdprhgtphhtthho pehrvghshhhmrgdrphgrthhtrghnsehinhhtvghlrdgtohhmpdhrtghpthhtohepshhtvg hphhgvnhesnhgvthifohhrkhhplhhumhgsvghrrdhorhhgpdhrtghpthhtohepjhgvrhhi nhhjsehmrghrvhgvlhhlrdgtohhmpdhrtghpthhtohepkhhirhgrnhhkuhhmrghrkhesmh grrhhvvghllhdrtghomhdprhgtphhtthhopehnuggrsghilhhpuhhrrghmsehmrghrvhgv lhhlrdgtohhmpdhrtghpthhtohephigrnhiihhhirhhunhgpudeifeesudeifedrtghomh X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 30 Jun 2025 10:28:25 -0400 (EDT) From: Thomas Monjalon To: Dylan Schneider Cc: "dev@dpdk.org" , Reshma Pattan , Stephen Hemminger , Jerin Jacob , Kiran Kumar K , Nithin Dabilpuram , Zhirun Yan Subject: Re: [PATCH v2] pcapng: allow any protocol link type for the interface block Date: Mon, 30 Jun 2025 16:28:24 +0200 Message-ID: <4485771.rnzLaay6km@thomas> In-Reply-To: References: <20250529171609.2448832-1-schneide@qti.qualcomm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sorry I did not investigate, but there is probably a different installation of the pcap library. I have this in a config file: pcaparm=$deps/libpcap/build-aarch64/install # requires big changes in DPDK #export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:$pcaparm/lib/pkgconfig I don't remember what are the big changes required, and why it is disabled. Checking Meson, libpcap is indeed not found on aarch64: Run-time dependency libpcap found: NO (tried pkgconfig) Library pcap found: NO Can you check whether the error can be related to the absence of libpcap? 30/06/2025 15:50, Dylan Schneider: > Hey Thomas, just wanted to confirm, I see the ARM build passing in CI. Is there a reason it would pass there but not on your dev machine? > > > ________________________________ > From: Dylan Schneider > Sent: Friday, June 27, 2025 11:46 AM > To: Thomas Monjalon > Cc: dev@dpdk.org ; Reshma Pattan ; Stephen Hemminger ; Jerin Jacob ; Kiran Kumar K ; Nithin Dabilpuram ; Zhirun Yan > Subject: Re: [PATCH v2] pcapng: allow any protocol link type for the interface block > > > WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. > > Hey Thomas, > Thanks for the reply. > Can you tell me the build command you're using to produce those errors? I have ran the builds on my test machine and cannot reproduce these. Thanks! > Dylan > ________________________________ > From: Thomas Monjalon > Sent: Friday, June 27, 2025 11:39 AM > To: Dylan Schneider > Cc: dev@dpdk.org ; Reshma Pattan ; Stephen Hemminger ; Jerin Jacob ; Kiran Kumar K ; Nithin Dabilpuram ; Zhirun Yan > Subject: Re: [PATCH v2] pcapng: allow any protocol link type for the interface block > > WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. > > 09/06/2025 23:19, Schneide: > > From: Dylan Schneider > > > > Allow the user to specify protocol link type when creating pcapng files. > > This change is needed to specify the protocol type in the pcapng file, > > DLT_EN10MB specifies ethernet packets only. This will allow dissectors > > for other protocols to be used on files generated by pcapng. > > > > Includes a breaking change to rte_pcapng_add_interface to add link_type > > parameter. Existing calls to the function have been updated to pass > > DLT_EN10MB for the link type argument. > > > > Fixes: d1da6d0d04c7 ("pcapng: require per-interface information") > > Signed-off-by: Dylan Schneider > > Cc: stephen@networkplumber.org > > I doesn't pass compilation test on my machine: > > Error: cannot find librte_pcapng.so.25.1 in dpdk-build/build-arm64-generic-gcc/install > Error: cannot find librte_graph.so.25.1 in dpdk-build/build-arm64-generic-gcc/install > Error: cannot find librte_node.so.25.1 in dpdk-build/build-arm64-generic-gcc/install > Error: cannot find librte_pdump.so.25.1 in dpdk-build/build-arm64-generic-gcc/install > > > >