From: Ali Alnubani <alialnu@nvidia.com>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Thinh Tran <thinhtr@linux.vnet.ibm.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: RE: [PATCH] config: set pkgconfig for ppc64le
Date: Tue, 30 Aug 2022 18:36:01 +0000 [thread overview]
Message-ID: <DM4PR12MB5167E5AF013105707495F7C4DA799@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <c704cedc-4293-7893-6480-5a2a75711bf1@linux.vnet.ibm.com>
> On 8/29/22 3:30 AM, Thomas Monjalon wrote:
> > What is the conclusion on this patch?
> > It is good to go? Acked?
>
> Not from me yet.
>
> Just asked about the test environment so I can duplicate the issue. My
> understanding is that Ubuntu cross-compiles for CI/CD are still working
> so I'd like to understand the test case the drives this need.
>
> Dave
Trying to enable the mlx drivers when cross-building for ppc64le, I added the directory containing
the .pc files from an rdma-core (https://github.com/linux-rdma/rdma-core) ppc64le cross build, but Meson
didn't detect the dependencies without installing pkg-config-powerpc64le-linux-gnu and setting
binaries.pkgconfig as powerpc64le-linux-gnu-pkg-config.
I just tried to reproduce the issue with a cross build of numactl, but Meson will not
detect it, even with my change. Seems that PKG_CONFIG_PATH=:/path/to/numactl/build/lib/pkgconfig
gets ignored.
- Ali
next prev parent reply other threads:[~2022-08-30 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 11:41 Ali Alnubani
2022-07-11 20:10 ` Thomas Monjalon
2022-07-13 7:39 ` Ali Alnubani
2022-07-13 9:12 ` Thomas Monjalon
2022-07-13 10:14 ` Ali Alnubani
2022-07-13 10:51 ` Ali Alnubani
2022-07-13 19:49 ` Thinh Tran
2022-07-14 6:58 ` Ali Alnubani
2022-07-18 20:16 ` Thinh Tran
2022-07-19 23:02 ` David Christensen
2022-08-29 10:30 ` Thomas Monjalon
2022-08-30 17:39 ` David Christensen
2022-08-30 18:36 ` Ali Alnubani [this message]
2022-10-26 16:21 ` Ali Alnubani
2022-08-30 17:36 ` David Christensen
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=DM4PR12MB5167E5AF013105707495F7C4DA799@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=thinhtr@linux.vnet.ibm.com \
--cc=thomas@monjalon.net \
/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).