Yes I have used DPDK as a combined library. I still get the same result.
On Monday, January 11, 2016 12:05 PM, "Kavanagh, Mark B"
<[email protected]> wrote:
#yiv1845341625 #yiv1845341625 -- _filtered #yiv1845341625
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv1845341625
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv1845341625
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv1845341625
#yiv1845341625 p.yiv1845341625MsoNormal, #yiv1845341625
li.yiv1845341625MsoNormal, #yiv1845341625 div.yiv1845341625MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv1845341625 a:link,
#yiv1845341625 span.yiv1845341625MsoHyperlink
{color:blue;text-decoration:underline;}#yiv1845341625 a:visited, #yiv1845341625
span.yiv1845341625MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv1845341625
span.yiv1845341625EmailStyle17 {color:#1F497D;}#yiv1845341625
.yiv1845341625MsoChpDefault {font-size:10.0pt;} _filtered #yiv1845341625
{margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv1845341625
div.yiv1845341625WordSection1 {}#yiv1845341625 I am currently using dpdk
2.0.0 with ovs 2.4.0 - checking for stdio.h... yes checking for
string.h... (cached) yes checking whether gcc -std=gnu99 accepts -Werror... yes
checking whether gcc -std=gnu99 accepts -Wall... yes checking whether gcc
-std=gnu99 accepts -Wextra... yes checking whether gcc -std=gnu99 accepts
-Wno-sign-compare... yes checking whether gcc -std=gnu99 accepts
-Wpointer-arith... yes checking whether gcc -std=gnu99 accepts
-Wformat-security... no checking whether gcc -std=gnu99 accepts
-Wswitch-enum... yes checking whether gcc -std=gnu99 accepts
-Wunused-parameter... yes checking whether gcc -std=gnu99 accepts
-Wbad-function-cast... yes checking whether gcc -std=gnu99 accepts
-Wcast-align... yes checking whether gcc -std=gnu99 accepts
-Wstrict-prototypes... no checking whether gcc -std=gnu99 accepts
-Wold-style-definition... no checking whether gcc -std=gnu99 accepts
-Wmissing-prototypes... yes checking whether gcc -std=gnu99 accepts
-Wmissing-field-initializers... yes checking whether gcc -std=gnu99 accepts
-Wthread-safety... no checking whether gcc -std=gnu99 accepts
-fno-strict-aliasing... yes checking whether gcc -std=gnu99 accepts
-Qunused-arguments... no checking whether gcc -std=gnu99 accepts -Wno-unused...
yes checking whether gcc -std=gnu99 accepts -Wno-unused-parameter... yes
checking target hint for cgcc... x86_64 checking whether make has GNU make
$(if) extension... yes configure: error: cannot link with dpdk attached
config.log for debug purposes. I am still stuck and unable to figure out
what the problem. Thanks -sundar Have you built DPDK as a combined
library? Try adding the following option when building DPDK: make install
T=<rest of DPDK build command> CONFIG_RTE_BUILD_COMBINE_LIBS=y On Monday,
January 11, 2016 5:14 AM, "Traynor, Kevin" <[email protected]> wrote:
> -----Original Message-----
> From: discuss [mailto:[email protected]] On Behalf Of Ben Pfaff
> Sent: Friday, January 8, 2016 7:11 PM
> To: Sundar Ramakrishnan
> Cc: [email protected]
> Subject: Re: [ovs-discuss] Openvswitch Compatibility With DPDK on CentOS 7
>
> On Fri, Jan 08, 2016 at 05:02:44PM +0000, Sundar Ramakrishnan wrote:
> > I am trying to install openvswitch 2.4.0 with dpdk 2.2.0 but I seem to
> > hit the same issue in spite of following several documentation guides
> > available on Openvswitch/Intel/DPDK etc.,
>
> INSTALL.DPDK.md says that OVS requires DPDK 2.1.
That's true for head of master (although DPDK 2.2 should work and there's a
pending patch to update docs/travis)
For OVS 2.4.0, INSTALL.DPDK.md says DPDK 2.0.0 is required. If you want
OVS 2.4.0 to work with a later build of DPDK then you'll need to backport
the OVS patches that were applied to master to enable this.
> _______________________________________________
> discuss mailing list
> [email protected]
> http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
