From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: arch check in example dpdk_qat
Date: Thu, 24 Mar 2016 14:16:30 +0100 [thread overview]
Message-ID: <5066636.22jD4vx1yD@xps13> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973C8CF87A@IRSMSX108.ger.corp.intel.com>
2016-03-24 11:58, De Lara Guarch, Pablo:
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Sent: Thursday, March 24, 2016 11:01 AM
> > To: De Lara Guarch, Pablo
> > Cc: Richardson, Bruce; dev@dpdk.org
> > Subject: Re: arch check in example dpdk_qat
> >
> > 2016-03-24 10:50, De Lara Guarch, Pablo:
> > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > > When reading examples/dpdk_qat/Makefile, we can see this check:
> > > >
> > > > ifneq ($(CONFIG_RTE_ARCH),"x86_64")
> > > > ifneq ($(LBITS),i686)
> > > > $(error The RTE_TARGET chosen is not compatible with this
> > environment
> > > > \
> > > > (x86_64), for this application. Please change the definition of the \
> > > > RTE_TARGET environment variable, or run the application on a 32-bit
> > > > OS)
> > > > endif
> > > > endif
> > > >
> > > > Is it on purpose to limit the 32-bit support to i686 only?
> > > > Instead of the message "run the application on a 32-bit OS", should it be
> > > > "on an i686 OS"?
> > >
> > > i686 OS looks fine to me. Basically, when this app was made, the only 32-bit
> > target was i686,
> >
> > What about i386, i486, i586 builds ?
>
> We only support i686, no other 32-bit architectures.
So we need a small patch :)
prev parent reply other threads:[~2016-03-24 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 11:04 arch check in example dpdk_qat Thomas Monjalon
2016-03-24 10:50 ` De Lara Guarch, Pablo
2016-03-24 11:00 ` Thomas Monjalon
2016-03-24 11:58 ` De Lara Guarch, Pablo
2016-03-24 13:16 ` 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=5066636.22jD4vx1yD@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.