From: Thomas Monjalon <thomas@monjalon.net>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"Zhang, XuemingX" <xuemingx.zhang@intel.com>
Cc: dev@dpdk.org, "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"Ma, LihongX" <lihongx.ma@intel.com>
Subject: Re: [dpdk-dev] [PATCH V1] add meson build 32-bits on x86_64
Date: Fri, 06 Nov 2020 18:59:06 +0100 [thread overview]
Message-ID: <2129306.NRWLvje8d3@thomas> (raw)
In-Reply-To: <dfb56e5fc6f54176a25a65a090182487@intel.com>
23/04/2020 10:23, Zhang, XuemingX:
> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> >On Wed, Apr 22, 2020 at 09:48:54AM +0000, xueming wrote:
> >> Add user interaction features. The default build is 64-bits.
> >> if you want to build 32-bits on x86_64, need to pass parameters of i686.
> >> Merge -vv and -v into the method
> >>
> >> Signed-off-by: xueming <xuemingx.zhang@intel.com>
> >> ---
> >I'm wondering if this would be better done using a cross-file, rather than
> >overriding a bunch of environment variables - the pkg-config one would be
> >especially relevant. A separate cross-file could be used for debian-based
> >and fedora-based OS's with correct 32-bit paths and parameters in each.
> >
> >What do you think?
> >
> Many thanks Bruce,
> Your suggestion is very good, I will try to do it
Eventually the approach of this patch has been merged:
http://git.dpdk.org/dpdk/commit/?id=9b83106d
prev parent reply other threads:[~2020-11-06 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 9:48 xueming
2020-04-22 11:12 ` Bruce Richardson
2020-04-23 8:23 ` Zhang, XuemingX
2020-11-06 17:59 ` Thomas Monjalon [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=2129306.NRWLvje8d3@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=lihongx.ma@intel.com \
--cc=xuemingx.zhang@intel.com \
--cc=zhaoyan.chen@intel.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).