All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Dylan Schneider <schneide@qti.qualcomm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Reshma Pattan <reshma.pattan@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Jerin Jacob <jerinj@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Zhirun Yan <yanzhirun_163@163.com>
Subject: Re: [PATCH v2] pcapng: allow any protocol link type for the interface block
Date: Fri, 27 Jun 2025 20:27:20 +0200	[thread overview]
Message-ID: <5716686.dhzUhtFnW9@thomas> (raw)
In-Reply-To: <IA3PR02MB10771799502C67457C7CBE257E945A@IA3PR02MB10771.namprd02.prod.outlook.com>

27/06/2025 19:46, Dylan Schneider:
> 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!

I run devtools/test-meson-builds.sh with an Arm toolchain installed.

Message: 
=================
Libraries Enabled
=================

libs:
        log, kvargs, argparse, telemetry, pmu, eal, ptr_compress, ring, 
        rcu, mempool, mbuf, net, meter, ethdev, pci, cmdline, 
        metrics, hash, timer, acl, bbdev, bitratestats, bpf, cfgfile, 
        compressdev, cryptodev, distributor, dmadev, efd, eventdev, dispatcher, gpudev, 
        gro, gso, ip_frag, jobstats, latencystats, lpm, member, power, 
        rawdev, regexdev, mldev, rib, reorder, sched, security, stack, 
        vhost, ipsec, pdcp, fib, port, table, pipeline, 

Message: 
===============
Drivers Enabled
===============

common:
        cpt, dpaax, ionic, mvep, octeontx, cnxk, mlx5, nfp, 
        nitrox, qat, sfc_efx, zsda, 
bus:
        auxiliary, cdx, dpaa, fslmc, ifpga, pci, platform, uacce, 
        vdev, vmbus, 
mempool:
        bucket, cnxk, dpaa, dpaa2, octeontx, ring, stack, 
dma:
        cnxk, dpaa, dpaa2, hisilicon, odm, skeleton, 
net:
        af_packet, ark, atlantic, avp, axgbe, bnx2x, bnxt, bond, 
        cnxk, cxgbe, dpaa, dpaa2, ena, enetc, enetfec, enic, 
        failsafe, gve, hinic, hns3, e1000, fm10k, i40e, iavf, 
        ice, idpf, ixgbe, cpfl, ionic, mana, memif, mlx4, 
        mlx5, mvneta, mvpp2, netvsc, nfp, ngbe, null, octeontx, 
        octeon_ep, pfe, qede, r8169, ring, rnp, sfc, softnic, 
        tap, thunderx, txgbe, vdev_netvsc, vhost, virtio, vmxnet3, xsc, 

raw:
        cnxk_bphy, cnxk_gpio, cnxk_rvu_lf, dpaa2_cmdif, gdtc, ntb, skeleton, 
crypto:
        armv8, bcmfs, caam_jr, cnxk, dpaa_sec, dpaa2_sec, ionic, mlx5, 
        mvsam, nitrox, null, octeontx, scheduler, virtio, 
compress:
        mlx5, nitrox, octeontx, zlib, 
regex:
        mlx5, cn9k, 
ml:
        cnxk, 
vdpa:
        ifc, mlx5, nfp, sfc, 
event:
        cnxk, dpaa, dpaa2, dsw, opdl, skeleton, sw, octeontx, 

baseband:
        acc, fpga_5gnr_fec, fpga_lte_fec, la12xx, null, turbo_sw, 
gpu:

power:
        acpi, amd_pstate, cppc, intel_pstate, intel_uncore, kvm_vm, 

[...]
  User defined options
    Cross files           : dpdk/config/arm/arm64_armv8_linux_gcc
    buildtype             : debugoptimized
    default_library       : shared
    enable_deprecated_libs: *
    examples              : all
    werror                : True

Found ninja-1.12.1 at /usr/bin/ninja
Cleaning... 75 files.                                                                                
[3652/3653] Linking target drivers/librte_event_cnxk.so.25.2
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




  reply	other threads:[~2025-06-27 18:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 17:16 [PATCH] pcapng: allow any protocol link type for the interface block Schneide
2025-05-29 19:31 ` Stephen Hemminger
2025-05-29 19:57 ` Stephen Hemminger
2025-06-05 23:02 ` [PATCH v2] " Schneide
2025-06-06 15:13   ` Stephen Hemminger
2025-06-06 21:52 ` Schneide
2025-06-08 22:16   ` Stephen Hemminger
2025-06-08 22:19   ` Stephen Hemminger
2025-06-08 22:23   ` Stephen Hemminger
2025-06-08 22:30   ` Stephen Hemminger
2025-06-08 22:34   ` Stephen Hemminger
2025-06-09 15:51     ` Dylan Schneider
2025-06-09 16:24       ` Stephen Hemminger
2025-06-16 14:29   ` Dylan Schneider
2025-06-24 15:15     ` Dylan Schneider
2025-06-09 21:19 ` Schneide
2025-06-16 18:05   ` Stephen Hemminger
2025-06-26 13:57   ` Stephen Hemminger
2025-06-27 16:05   ` Thomas Monjalon
2025-06-27 17:39   ` Thomas Monjalon
2025-06-27 17:46     ` Dylan Schneider
2025-06-27 18:27       ` Thomas Monjalon [this message]
2025-06-30 13:50       ` Dylan Schneider
2025-06-30 14:28         ` Thomas Monjalon
2025-07-02 19:30           ` Dylan Schneider
2025-07-03 13:27             ` Thomas Monjalon
2025-07-03 16:29               ` Dylan Schneider
2025-07-03 16:41                 ` Thomas Monjalon
2025-07-08 21:02   ` [PATCH v3] " Schneide
2025-07-08 21:56     ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2025-08-27 15:38 [PATCH v1] " Schneide
2025-08-27 22:32 ` [PATCH v2] " Schneide
2025-09-25 23:54   ` Stephen Hemminger
2025-10-15 19:24     ` Thomas Monjalon
2025-09-26  0:04   ` Stephen Hemminger
2025-09-27  9:28     ` Thomas Monjalon
2025-09-29 17:34       ` Dylan Schneider

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=5716686.dhzUhtFnW9@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=reshma.pattan@intel.com \
    --cc=schneide@qti.qualcomm.com \
    --cc=stephen@networkplumber.org \
    --cc=yanzhirun_163@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.