Thanks a lot for your answer. We need fully statically application, because we want to run it on device with older kernel, than building one.
Regards, Michael -----Original Message----- From: Bruce Richardson <bruce.richard...@intel.com> Sent: Wednesday, August 24, 2022 11:07 AM To: Michael Lekar <michae...@radware.com> Cc: dev@dpdk.org Subject: Re: dpdk-22.07 On Mon, Aug 22, 2022 at 03:02:38PM +0000, Michael Lekar wrote: > Hi All, > > > My name is Michaele and I work in Radware Ltd . Currently we use > 17.11.3 version of dpdk in our product. Now we want to evaluate 22.07 > version of dpdk. We want to build statically linkage dpdk-test > application and run it on our device. We use 7.5 version of gcc. By > default, dpdk-test uses shared library, and we don’t find how to > configure meson for build these test application static. We will be > very applicate for any help with issue. > > > > [ulp-ng]# ldd dpdk-test > > ./dpdk-test: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.16' not > found (required by ./dpdk-test) > > ./dpdk-test: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not > found (required by ./dpdk-test) > > ./dpdk-test: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not > found (required by ./dpdk-test) > > ./dpdk-test: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not > found (required by ./dpdk-test) > > linux-vdso.so.1 => (0x00007ffff7ffd000) > > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 > (0x00007ffff7cfd000) > > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 > (0x00007ffff7af9000) > > libnuma.so.1 => /usr/lib/libnuma.so.1 (0x00007ffff78ed000) > > libpcap.so.1 => /usr/lib/libpcap.so.1 (0x00007ffff76ac000) > > libatomic.so.1 => /usr/lib/libatomic.so.1 > (0x00007ffff74a4000) > > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007ffff7286000) > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 > (0x00007ffff6ec9000) > > /lib64/ld-linux-x86-64.so.2 (0x0000555555554000) > > [ulp-ng]# > This is not something we have ever looked to do with DPDK builds. Normally, we consider static builds to be builds where we link in all the DPDK libraries statically, but don't consider OS-libs for static linking. Is there a particular reason why you need a fully-static version of the code - can you compile and run on the same system, or build on a system with the same OS version as you intend running the code on? /Bruce
