> >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: > > >I am currently using dpdk 2.0.0 with ovs 2.4.0 -
When you build DPDK v2.0.0, the name of the generated combined library is libintel_dpdk.a; however for DPDK v2.1.0 and later versions, that name has changed to libdpdk.a. OVS v2.4.0 links against the latter, so you should either upgrade your DPDK version, or change acinclude.m4 in OVS to link against libintel_dpdk.a instead. See the following patch for details on the library name change: http://openvswitch.org/pipermail/dev/2015-September/059616.html > > >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
