DPDK patches and discussions
 help / color / mirror / Atom feed
From: Truring Team <truring12@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK 20.11 Static vs Dynamic Linking- l2fwd issue
Date: Tue, 19 Jan 2021 16:54:28 +0530	[thread overview]
Message-ID: <CALvshjMfb-ay9DyxzOd7t1tXsAEs3=oAHVd2TM=rLi9S7Kjm3A@mail.gmail.com> (raw)
In-Reply-To: <CALvshjOZXxCthUxxN86mJQjCCYOOmssA-majghf68QN+VeJrSQ@mail.gmail.com>

export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig


pkg-config --static --libs libdpdk
-Wl,--whole-archive -Wl,--no-whole-archive -Wl,--as-needed -pthread
-L/usr/local/lib64 -l:librte_common_cpt.a -l:librte_common_dpaax.a
-l:librte_common_iavf.a -l:librte_common_octeontx.a
-l:librte_common_octeontx2.a -l:librte_common_sfc_efx.a
-l:librte_bus_dpaa.a -l:librte_bus_fslmc.a -l:librte_bus_ifpga.a
-l:librte_bus_pci.a -l:librte_bus_vdev.a -l:librte_bus_vmbus.a
-l:librte_common_qat.a -l:librte_mempool_bucket.a -l:librte_mempool_dpaa.a
-l:librte_mempool_dpaa2.a -l:librte_mempool_octeontx.a
-l:librte_mempool_octeontx2.a -l:librte_mempool_ring.a
-l:librte_mempool_stack.a -l:librte_net_af_packet.a -l:librte_net_ark.a
-l:librte_net_atlantic.a -l:librte_net_avp.a -l:librte_net_axgbe.a
-l:librte_net_bond.a -l:librte_net_bnx2x.a -l:librte_net_bnxt.a
-l:librte_net_cxgbe.a -l:librte_net_dpaa.a -l:librte_net_dpaa2.a
-l:librte_net_e1000.a -l:librte_net_ena.a -l:librte_net_enetc.a
-l:librte_net_enic.a -l:librte_net_failsafe.a -l:librte_net_fm10k.a
-l:librte_net_i40e.a -l:librte_net_hinic.a -l:librte_net_hns3.a
-l:librte_net_iavf.a -l:librte_net_ice.a -l:librte_net_igc.a
-l:librte_net_ixgbe.a -l:librte_net_kni.a -l:librte_net_liquidio.a
-l:librte_net_memif.a -l:librte_net_netvsc.a -l:librte_net_nfp.a
-l:librte_net_null.a -l:librte_net_octeontx.a -l:librte_net_octeontx2.a
-l:librte_net_pcap.a -l:librte_net_pfe.a -l:librte_net_qede.a
-l:librte_net_ring.a -l:librte_net_sfc.a -l:librte_net_softnic.a
-l:librte_net_tap.a -l:librte_net_thunderx.a -l:librte_net_txgbe.a
-l:librte_net_vdev_netvsc.a -l:librte_net_vhost.a -l:librte_net_virtio.a
-l:librte_net_vmxnet3.a -l:librte_raw_dpaa2_cmdif.a
-l:librte_raw_dpaa2_qdma.a -l:librte_raw_ioat.a -l:librte_raw_ntb.a
-l:librte_raw_octeontx2_dma.a -l:librte_raw_octeontx2_ep.a
-l:librte_raw_skeleton.a -l:librte_crypto_bcmfs.a
-l:librte_crypto_caam_jr.a -l:librte_crypto_ccp.a
-l:librte_crypto_dpaa_sec.a -l:librte_crypto_dpaa2_sec.a
-l:librte_crypto_nitrox.a -l:librte_crypto_null.a
-l:librte_crypto_octeontx.a -l:librte_crypto_octeontx2.a
-l:librte_crypto_openssl.a -l:librte_crypto_scheduler.a
-l:librte_crypto_virtio.a -l:librte_compress_octeontx.a
-l:librte_compress_zlib.a -l:librte_regex_octeontx2.a -l:librte_vdpa_ifc.a
-l:librte_event_dlb.a -l:librte_event_dlb2.a -l:librte_event_dpaa.a
-l:librte_event_dpaa2.a -l:librte_event_octeontx2.a -l:librte_event_opdl.a
-l:librte_event_skeleton.a -l:librte_event_sw.a -l:librte_event_dsw.a
-l:librte_event_octeontx.a -l:librte_baseband_null.a
-l:librte_baseband_turbo_sw.a -l:librte_baseband_fpga_lte_fec.a
-l:librte_baseband_fpga_5gnr_fec.a -l:librte_baseband_acc100.a
-l:librte_node.a -l:librte_graph.a -l:librte_bpf.a
-l:librte_flow_classify.a -l:librte_pipeline.a -l:librte_table.a
-l:librte_port.a -l:librte_fib.a -l:librte_ipsec.a -l:librte_vhost.a
-l:librte_stack.a -l:librte_security.a -l:librte_sched.a
-l:librte_reorder.a -l:librte_rib.a -l:librte_regexdev.a -l:librte_rawdev.a
-l:librte_pdump.a -l:librte_power.a -l:librte_member.a -l:librte_lpm.a
-l:librte_latencystats.a -l:librte_kni.a -l:librte_jobstats.a
-l:librte_ip_frag.a -l:librte_gso.a -l:librte_gro.a -l:librte_eventdev.a
-l:librte_efd.a -l:librte_distributor.a -l:librte_cryptodev.a
-l:librte_compressdev.a -l:librte_cfgfile.a -l:librte_bitratestats.a
-l:librte_bbdev.a -l:librte_acl.a -l:librte_timer.a -l:librte_hash.a
-l:librte_metrics.a -l:librte_cmdline.a -l:librte_pci.a -l:librte_ethdev.a
-l:librte_meter.a -l:librte_net.a -l:librte_mbuf.a -l:librte_mempool.a
-l:librte_rcu.a -l:librte_ring.a -l:librte_eal.a -l:librte_telemetry.a
-l:librte_kvargs.a -lcrypto -lz -ljansson -lrte_node -lrte_graph -lrte_bpf
-lrte_flow_classify -lrte_pipeline -lrte_table -lrte_port -lrte_fib
-lrte_ipsec -lrte_vhost -lrte_stack -lrte_security -lrte_sched
-lrte_reorder -lrte_rib -lrte_regexdev -lrte_rawdev -lrte_pdump -lrte_power
-lrte_member -lrte_lpm -lrte_latencystats -lrte_kni -lrte_jobstats
-lrte_ip_frag -lrte_gso -lrte_gro -lrte_eventdev -lrte_efd
-lrte_distributor -lrte_cryptodev -lrte_compressdev -lrte_cfgfile
-lrte_bitratestats -lrte_bbdev -lrte_acl -lrte_timer -lrte_hash
-lrte_metrics -lrte_cmdline -lrte_pci -lrte_ethdev -lrte_meter -lrte_net
-lrte_mbuf -lrte_mempool -lrte_rcu -lrte_ring -lrte_eal -lrte_telemetry
-lrte_kvargs -lm -ldl -lnuma -lpcap

On Tue, 19 Jan 2021 at 16:51, Truring Team <truring12@gmail.com> wrote:

> cat /etc/redhat-release
> CentOS Linux release 7.8.2003 (Core)
>
>
> pkg-config --version
> 0.27.1
>
>
> pkg-config --static --libs libdpdk
> Package libdpdk was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libdpdk.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'libdpdk' found
>
> locate libdpdk.pc
> /home/user/dpdk-20.11/build/meson-private/libdpdk.pc
> /usr/local/lib64/pkgconfig/libdpdk.pc
>
>
> Thanks
>
> On Tue, 19 Jan 2021 at 16:12, Bruce Richardson <bruce.richardson@intel.com>
> wrote:
>
>> On Tue, Jan 19, 2021 at 10:40:10AM +0000, Bruce Richardson wrote:
>> > On Tue, Jan 19, 2021 at 03:36:18PM +0530, Truring Team wrote:
>> > > Hi Team,
>> > >
>> > > I am facing one issue with dpdk 20.11 Release, compiled the l2fwd app
>> with
>> > > make static , its throwing following error while running the app:
>> > >
>> > > Problematic Use Case:
>> > > cd dpdk-20.11/examples/l2fwd
>> > > export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
>> > > *make static *
>> > > ./build/l2fwd -l 0-3 -n 4 -- -q 1 -p 1
>> > > EAL: Detected 6 lcore(s)
>> > > EAL: Detected 1 NUMA nodes
>> > > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
>> > > EAL: Selected IOVA mode 'PA'
>> > > EAL: No available hugepages reported in hugepages-1048576kB
>> > > EAL: Probing VFIO support...
>> > > EAL: No legacy callbacks, legacy socket not created
>> > > MAC updating enabled
>> > >
>> > > *EAL: Error - exiting with code: 1  Cause: No Ethernet ports - bye*
>> > >
>> > <snip>
>> > > Can someone help me to figure out the root cause why this happening.
>> > >
>> >
>> > It seems like the static libs for the drivers are not linked in for the
>> > "make static" case. Can you please check the following:
>> >
>> > * What OS/distro are you using, and what is the pkg-config version? The
>> >   version of pkg-config included in RHEL/Centos is known to have some
>> >   issues in linking DPDK.
>> Missed clarification - RHEL/Centos *7* only. RHEL 8 is fine.
>>
>> > * What is the output when you run "pkg-config --static --libs libdpdk"
>>
>

  reply	other threads:[~2021-01-19 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 10:06 Truring Team
2021-01-19 10:40 ` Bruce Richardson
2021-01-19 10:42   ` Bruce Richardson
2021-01-19 11:21     ` Truring Team
2021-01-19 11:24       ` Truring Team [this message]
2021-01-19 12:44         ` Bruce Richardson

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='CALvshjMfb-ay9DyxzOd7t1tXsAEs3=oAHVd2TM=rLi9S7Kjm3A@mail.gmail.com' \
    --to=truring12@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    /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).