From: Ali Alnubani <alialnu@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
David Christensen <drc@linux.vnet.ibm.com>
Subject: RE: [PATCH] config: set pkgconfig for ppc64le
Date: Wed, 13 Jul 2022 10:51:25 +0000 [thread overview]
Message-ID: <DM4PR12MB51677417E1604C646E1F9518DA899@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM4PR12MB5167FDBA99BFE502EF13FFB3DA899@DM4PR12MB5167.namprd12.prod.outlook.com>
> -----Original Message-----
> From: Ali Alnubani
> Sent: Wednesday, July 13, 2022 1:14 PM
> To: Thomas Monjalon <thomas@monjalon.net>
> Cc: dev@dpdk.org; David Christensen <drc@linux.vnet.ibm.com>
> Subject: RE: [PATCH] config: set pkgconfig for ppc64le
>
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Wednesday, July 13, 2022 12:12 PM
> > To: Ali Alnubani <alialnu@nvidia.com>
> > Cc: dev@dpdk.org; David Christensen <drc@linux.vnet.ibm.com>
> > Subject: Re: [PATCH] config: set pkgconfig for ppc64le
> >
> > 13/07/2022 09:39, Ali Alnubani:
> > > > -----Original Message-----
> > > > From: Thomas Monjalon <thomas@monjalon.net>
> > > > Sent: Monday, July 11, 2022 11:11 PM
> > > > To: Ali Alnubani <alialnu@nvidia.com>
> > > > Cc: dev@dpdk.org; David Christensen <drc@linux.vnet.ibm.com>
> > > > Subject: Re: [PATCH] config: set pkgconfig for ppc64le
> > > >
> > > > + PPC maintainer
> > > >
> > > > 07/07/2022 13:41, Ali Alnubani:
> > > > > Meson fails to detect the dependencies that are included
> > > > > in PKG_CONFIG_PATH and built for ppc64le if binaries.pkgconfig
> > > > > is not set in the ppc64le cross-file for Ubuntu.
> > > > >
> > > > > This fixes the issue by setting binaries.pkgconfig to the
> > > > > binary provided by the package 'pkg-config-powerpc64le-linux-gnu'.
> > > > >
> > > > > Signed-off-by: Ali Alnubani <alialnu@nvidia.com>
> > > > > ---
> > > > > config/ppc/ppc64le-power8-linux-gcc-ubuntu | 1 +
> > > >
> > > > Why not adding the same for ppc64le-power8-linux-gcc?
> > > >
> > > > > +pkgconfig = 'powerpc64le-linux-gnu-pkg-config'
> > >
> > > I didn't find any operating systems that distribute the powerpc64le cross-
> > compiler with the binary names found in config/ppc/ppc64le-power8-linux-
> > gcc.
> > > Both Ubuntu and Fedora use the -gnu suffix. Fedora doesn't seem to
> have
> > a pkg-config binary for powerpc64le though.
> >
> > So how does it work on Fedora?
> >
>
> On Fedora, the pcc64 cross-compiler is provided by package 'gcc-
> powerpc64le-linux-gnu' with binary names /usr/bin/powerpc64le-linux-gnu-
> *, same as in Ubuntu.
> The cross-file config/ppc/ppc64le-power8-linux-gcc doesn't work with
> Fedora since the binary names in the file don't have the -gnu suffix, so I'm
> not sure where this cross-file is being used.
>
> Another issue I found is that when I set the correct binary names in
> config/ppc/ppc64le-power8-linux-gcc or use config/ppc/ppc64le-power8-
> linux-gcc-ubuntu, I get the following error on Fedora:
> config/ppc/meson.build:6:4: ERROR: Problem encountered: Only 64-bit
> compiles are supported for this platform type
> It happens because cc.sizeof('void *') in
> https://git.dpdk.org/dpdk/tree/config/meson.build#n144 returns '-1'. I'm on
> Fedora 35.
I believe that's because the Fedora package doesn't provide stdio.h for ppc64le.
>
> Is anyone able to cross-build for ppc64le in Fedora?
next prev parent reply other threads:[~2022-07-13 10:51 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 [this message]
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
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=DM4PR12MB51677417E1604C646E1F9518DA899@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--cc=drc@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).