From: Bruce Richardson <bruce.richardson@intel.com>
To: Gilbert Carrillo <gcarrillo@ampex.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: DPDK 22.11 Troubleshooting
Date: Wed, 3 May 2023 17:34:37 +0100 [thread overview]
Message-ID: <ZFKNHUj4KU0piBQT@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <SN7PR20MB6109732D4577CFEEF187EBB1B76C9@SN7PR20MB6109.namprd20.prod.outlook.com>
On Wed, May 03, 2023 at 04:22:05PM +0000, Gilbert Carrillo wrote:
> Hi Bruce,
>
> Thank you for the response.
>
> There is no errors when I run the makefile, however I do see a difference in the programs. I don't believe the makefile is linking all the libraries together as intended.
>
> For example, when I run the ethtool sample program and compile it using meson, it works fine and rte_eth_dev_count_avail() returns the correct amount. However, when I compile ethtool with the makefile and run it rte_eth_dev_count_avail() returns 0.
>
Note that by default the meson build will statically link the examples,
while the makefile will dynamically load the drivers at runtime. That may
explain the difference. Can you try building and running using "make
static" rather than just "make".
/Bruce
next prev parent reply other threads:[~2023-05-03 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 22:27 Gilbert Carrillo
2023-05-03 8:28 ` Bruce Richardson
2023-05-03 16:22 ` Gilbert Carrillo
2023-05-03 16:34 ` Bruce Richardson [this message]
2023-05-03 16:53 ` Gilbert Carrillo
2023-05-03 17:13 ` Bruce Richardson
2023-05-03 17:18 ` Bruce Richardson
2023-05-03 17:25 ` Gilbert Carrillo
2023-05-08 23:26 ` Gilbert Carrillo
2023-05-09 9:42 ` Bruce Richardson
2023-05-09 14:16 ` Gilbert Carrillo
2023-05-09 14:52 ` Bruce Richardson
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=ZFKNHUj4KU0piBQT@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gcarrillo@ampex.com \
/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).