DPDK usage discussions
 help / color / mirror / Atom feed
From: Pankaj Gupta <pagupta@vmware.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: Jochen Behrens <jbehrens@vmware.com>, Hayden Fowler <hfowler@vmware.com>
Subject: How to use specific OPENSSL
Date: Thu, 1 Dec 2022 18:25:29 +0000	[thread overview]
Message-ID: <BYAPR05MB56247172027401F845BE9B3EC9139@BYAPR05MB5624.namprd05.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3280 bytes --]

Hi All,
We want to use specific downloaded openssl while compiling the DPDKv21.11.
We don’t want to use the openssl installed in the build machine.

We tried adding -Dc_args and -Dc_link_args to meson configure to specify the director of external openssl but build still seems to be linking to installed verson of the open ssl.

meson setup build
meson configure -Dc_args="-I /thirdparty/gobuild/compcache/cayman_openssl/ob-20569149/linux64/lin64+gcc6/include" -Dc_link_args="-L thirdparty/gobuild/compcache/cayman_openssl/ob-20569149/linux64/lin64+gcc6/lib64/"
ninja -C build


ldd ./dpdk/build/drivers/librte_common_qat.so
        linux-vdso.so.1 (0x00007ffceffea000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fe7d445b000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fe7d4455000)
        libnuma.so.1 => /lib/x86_64-linux-gnu/libnuma.so.1 (0x00007fe7d4448000)
        librte_bus_pci.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/librte_bus_pci.so.22 (0x00007fe7d4438000)
        librte_eal.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_eal.so.22 (0x00007fe7d432d000)
       librte_kvargs.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_kvargs.so.22 (0x00007fe7d4326000)
        librte_telemetry.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_telemetry.so.22 (0x00007fe7d431b000)
        librte_pci.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_pci.so.22 (0x00007fe7d4316000)
        librte_cryptodev.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_cryptodev.so.22 (0x00007fe7d42fa000)
        librte_mbuf.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_mbuf.so.22 (0x00007fe7d42ec000)
        librte_mempool.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_mempool.so.22 (0x00007fe7d42dd000)
        librte_ring.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_ring.so.22 (0x00007fe7d42d8000)
        librte_rcu.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_rcu.so.22 (0x00007fe7d42d1000)
        librte_net.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_net.so.22 (0x00007fe7d42c7000)
        librte_compressdev.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_compressdev.so.22 (0x00007fe7d42bd000)
        librte_security.so.22 => /root/nsx-edge-datapath-dpdk-21-11/thirdparty/./dpdk/build/drivers/../lib/librte_security.so.22 (0x00007fe7d42b4000)
        libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007fe7d3df4000) <<< This is the installed version of the openssl not the external version
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fe7d3dd1000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe7d3bdf000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fe7d45f3000)

Please suggest how do we achieve this in meson/ninja?

Thanks,
Pankaj

[-- Attachment #2: Type: text/html, Size: 9557 bytes --]

                 reply	other threads:[~2022-12-01 18:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BYAPR05MB56247172027401F845BE9B3EC9139@BYAPR05MB5624.namprd05.prod.outlook.com \
    --to=pagupta@vmware.com \
    --cc=hfowler@vmware.com \
    --cc=jbehrens@vmware.com \
    --cc=users@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).