From: Stephen Hemminger <stephen@networkplumber.org>
To: Michael Lekar <MichaelLe@radware.com>
Cc: dev <dev@dpdk.org>
Subject: Re: dpdk-22.07
Date: Wed, 24 Aug 2022 07:28:12 -0700 [thread overview]
Message-ID: <CAOaVG15NpRGZLNkYyK9Ypr_yScMhCi8G8GjDfzaGqq596OdLow@mail.gmail.com> (raw)
In-Reply-To: <DU2PR01MB832826DAC0A3FCF0DB5BE976AD719@DU2PR01MB8328.eurprd01.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]
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> 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: 4872 bytes --]
next prev parent reply other threads:[~2022-08-24 14:28 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 ` Stephen Hemminger [this message]
2022-08-25 8:50 ` dpdk-22.07 Michael Lekar
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=CAOaVG15NpRGZLNkYyK9Ypr_yScMhCi8G8GjDfzaGqq596OdLow@mail.gmail.com \
--to=stephen@networkplumber.org \
--cc=MichaelLe@radware.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).