From: Bruce Richardson <bruce.richardson@intel.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] build: support i686 target on x86 64-bit hosts
Date: Fri, 25 Sep 2020 15:28:30 +0100 [thread overview]
Message-ID: <20200925142830.GC943@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CADyeNEAfzhNEDv3vs_CfU3w6TDzb=X5Cc0QcrFuLnnz4Nt-vag@mail.gmail.com>
On Fri, Sep 25, 2020 at 10:08:35AM -0400, Lance Richardson wrote:
> On Fri, Sep 25, 2020 at 9:44 AM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > On Fri, Sep 25, 2020 at 09:27:25AM -0400, Lance Richardson wrote:
> > > On Fri, Sep 25, 2020 at 5:13 AM Bruce Richardson
> > > <bruce.richardson@intel.com> wrote:
> > > >
> > > > On Thu, Sep 24, 2020 at 12:37:42PM -0400, Lance Richardson wrote:
> > > > > Add meson cross files for building i686 targets using gcc on x86_64
> > > > > linux hosts.
> > > > >
> > > > > Uusage example:
> > > > >
> > > > > meson --cross-file config/x86/cross-i686-linux-gcc build-i686
> > > > > ninja -C build-i686
> > > > >
> > > > > Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
> > > > > ---
> > > > > Red Hat distros use a different name for the 32-bit pkg-config
> > > > > command from most other distros, maybe there is a better way
> > > > > to handle this than using separate files.
> > > > >
> > > > > Others will probably have better naming suggestions for the files.
> > > > >
> > > > Just to note that rather than using cross-files, building i686 on x86_64
> > > > should be possible by just setting environment variables.
> > > >
> > > > For example, on Ubuntu 20.04, this works for me:
> > > >
> > > > PKG_CONFIG_LIBDIR=/usr/lib/i386-linux-gnu/pkgconfig CFLAGS='-m32' LDFLAGS='-m32' meson --werror build-32bit
> > > > ninja -C build-32bit/
> > > >
> > > > For Fedora or Redhat system the PKG_CONFIG_LIBDIR will be different (I
> > > > think just /usr/lib/pkgconfig), but the rest should work identically.
> > > >
> > > > /Bruce
> > >
> > > Thanks, that does work, although I'll have some trouble remembering it
> > > for future
> > > use (unlike using cross-files). Googling for "PKG_CONFIG_LIBDIR meson dpdk"
> > > did lead me to this discussion, which makes it sound like cross-files
> > > might still
> > > worthy of consideration:
> > >
> > > https://patches.dpdk.org/patch/69067/
> > >
> >
> > Yes, absolutely the cross-file is worthy of consideration. The most awkward
> > part in both cases is getting the 32-bit pkg-config right.
>
> Agreed, having the distro-specific bits is not pretty.
>
> Would it be possible to set the pkgconfig binary name or
> PKG_CONFIG_LIBDIR in config/x86/meson.build? If so,
> maybe we could have a single cross-file and probe for the
> distro-specifics in meson.build.
Sadly, I'm not aware of any way to do that right now. It probably requires
changes in meson itself. :-(
next prev parent reply other threads:[~2020-09-25 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 16:37 Lance Richardson
2020-09-25 9:13 ` Bruce Richardson
2020-09-25 13:27 ` Lance Richardson
2020-09-25 13:44 ` Bruce Richardson
2020-09-25 14:08 ` Lance Richardson
2020-09-25 14:28 ` Bruce Richardson [this message]
2020-09-25 14:48 ` Ferruh Yigit
2020-10-06 8:30 ` Thomas Monjalon
2020-10-06 14:35 ` Lance Richardson
2020-11-06 17:54 ` Thomas Monjalon
2020-11-06 18:02 ` Lance 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=20200925142830.GC943@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=lance.richardson@broadcom.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).