From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Wang, Zhihong" <zhihong.wang@intel.com>,
"Kavanagh, Mark B" <mark.b.kavanagh@intel.com>,
"Qiu, Michael" <michael.qiu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Panu Matilainen <pmatilai@redhat.com>
Subject: Re: [dpdk-dev] rte_memcpy.h: additional cflags required with OVS
Date: Wed, 11 Mar 2015 08:06:11 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2ECD28E@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <F60F360A2500CD45ACDB1D700268892D0E79FD30@SHSMSX101.ccr.corp.intel.com>
> -----Original Message-----
> From: Wang, Zhihong
> Sent: Wednesday, March 11, 2015 4:38 AM
> To: Kavanagh, Mark B; Mcnamara, John; Qiu, Michael; dev@dpdk.org; Panu
> Matilainen
> Subject: RE: [dpdk-dev] rte_memcpy.h: additional cflags required with OVS
>
>
> Add the "-mssse3" flag should be able to solve the 'implicit definition of
> function' error.
> BTW, current dpdk should compile with gcc 4.7.2, anything changed there
> that makes this flag mandatory?
H John,
DPDK does compile with gcc 4.7.2. The issue here is compiling OVS against DPDK HEAD. Passing -msse N to the OVS configure does fix the issue.
John
prev parent reply other threads:[~2015-03-11 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 16:44 Kavanagh, Mark B
2015-03-09 17:51 ` Mcnamara, John
2015-03-10 0:57 ` Mcnamara, John
2015-03-10 3:00 ` Qiu, Michael
2015-03-10 9:16 ` Kavanagh, Mark B
2015-03-10 3:04 ` Qiu, Michael
2015-03-10 7:52 ` Panu Matilainen
2015-03-10 8:27 ` Mcnamara, John
2015-03-10 10:03 ` Kavanagh, Mark B
2015-03-11 4:37 ` Wang, Zhihong
2015-03-11 8:06 ` Mcnamara, John [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=B27915DBBA3421428155699D51E4CFE2ECD28E@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=mark.b.kavanagh@intel.com \
--cc=michael.qiu@intel.com \
--cc=pmatilai@redhat.com \
--cc=zhihong.wang@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).