From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Long Li <longli@microsoft.com>,
Shreesh Adiga <16567adigashreesh@gmail.com>,
Wei Hu <weh@microsoft.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [PATCH] net/mana: support rdma-core via pkg-config in meson
Date: Sun, 22 Sep 2024 01:15:43 +0100 [thread overview]
Message-ID: <4fb2ce8c-9ff9-4e94-a23a-cddc66e31398@amd.com> (raw)
In-Reply-To: <PH0PR21MB4456B4248C35A741CE6AFF6ECE6C2@PH0PR21MB4456.namprd21.prod.outlook.com>
On 9/20/2024 6:14 PM, Long Li wrote:
>> Subject: [PATCH] net/mana: support rdma-core via pkg-config in meson
>>
>> Currently building with custom rdma-core installed in /opt/rdma-core after
>> setting PKG_CONFIG_PATH=/opt/rdma-core/lib64/pkgconfig/ results in the below
>> meson logs:
>> Run-time dependency libmana found: YES 1.0.54.0 Header
>> "infiniband/manadv.h" has symbol "manadv_set_context_attr" : NO
>>
>> Thus to fix this, the libs is updated in meson.build and is passed to the
>> cc.has_header_symbol call using dependencies. After this change, the libmana
>> header files are getting included and net/mana is successfully enabled.
>>
>> Fixes: 517ed6e2d590 ("net/mana: add basic driver with build environment")
>> Cc: longli@microsoft.com
>> Cc: stable@dpdk.org
>> Signed-off-by: Shreesh Adiga <16567adigashreesh@gmail.com>
>
> Acked-by: Long Li <longli@microsoft.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-09-22 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 11:11 Shreesh Adiga
2024-09-20 17:14 ` Long Li
2024-09-22 0:15 ` Ferruh Yigit [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=4fb2ce8c-9ff9-4e94-a23a-cddc66e31398@amd.com \
--to=ferruh.yigit@amd.com \
--cc=16567adigashreesh@gmail.com \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=weh@microsoft.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).