From: Michael Lekar <MichaelLe@Radware.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>
Subject: RE: dpdk-22.07
Date: Thu, 25 Aug 2022 08:50:45 +0000 [thread overview]
Message-ID: <DU2PR01MB8328F9CBD35F306563C5263FAD729@DU2PR01MB8328.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <CAOaVG15NpRGZLNkYyK9Ypr_yScMhCi8G8GjDfzaGqq596OdLow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]
Hello Stephen,
We see the same issue with stable 21.11 version of dpdk.
Regards,
Michael
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Wednesday, August 24, 2022 5:28 PM
To: Michael Lekar <MichaelLe@radware.com>
Cc: dev <dev@dpdk.org>
Subject: Re: dpdk-22.07
Please choose a stable version 22.11 soon, or 21.11. bugs in 22.07 will not be fixed
On Tue, Aug 23, 2022, 11:38 PM Michael Lekar <MichaelLe@radware.com<mailto:MichaelLe@radware.com>> 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]#
Regards,
Michael
[-- Attachment #2: Type: text/html, Size: 7288 bytes --]
prev parent reply other threads:[~2022-08-25 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 15:02 dpdk-22.07 Michael Lekar
2022-08-24 8:06 ` dpdk-22.07 Bruce Richardson
2022-08-24 8:32 ` dpdk-22.07 Michael Lekar
2022-08-24 8:45 ` dpdk-22.07 Bruce Richardson
2022-08-24 8:59 ` dpdk-22.07 Michael Lekar
2022-08-24 14:28 ` dpdk-22.07 Stephen Hemminger
2022-08-25 8:50 ` Michael Lekar [this message]
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=DU2PR01MB8328F9CBD35F306563C5263FAD729@DU2PR01MB8328.eurprd01.prod.exchangelabs.com \
--to=michaelle@radware.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).