From: Bruce Richardson <bruce.richardson@intel.com>
To: Michael Lekar <MichaelLe@Radware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: dpdk-22.07
Date: Wed, 24 Aug 2022 09:45:17 +0100 [thread overview]
Message-ID: <YwXlHchvaSTbBeO8@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <DU2PR01MB8328F7A585E40569C00B9241AD739@DU2PR01MB8328.eurprd01.prod.exchangelabs.com>
On Wed, Aug 24, 2022 at 08:32:34AM +0000, Michael Lekar wrote:
> 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.
>
It's probably more the libc version that would be an issue rather than the
kernel itself. This should be possible to do, but may need some changes to
our build system.
Some suggestions (all untested):
* You can use the meson "c_link_args" option to set additional linking
flags, so perhaps try that to get static versions of some libraries
linked in
* If that doesn't work, if you remove the .so version of the libs (other than
libc) that DPDK is linking against and only have the .a file available, I
would expect DPDK build to use those .a files instead, which should give
a binary only requiring a dynamic libc version.
* the c_link_args may then allow you to statically link in your libc too,
if you can find the right parameters.
/Bruce
next prev parent reply other threads:[~2022-08-24 8:45 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 ` Bruce Richardson [this message]
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 ` 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=YwXlHchvaSTbBeO8@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--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).