Hi all, Yongqiang was able to compile ovs-dpctl & ovs-openflowd for ovs 1.0.3 on andoird. And I am trying to compile ovs-dpctl & ovs-openflowd for ovs 1.1.0pre2, as some patches have been pushed.
I am able to generate all the *.o file that ovs-dpctl needed, however when I tried to link them together, I got the following complains: route-table.o:(.debug_info+0x1735): undefined reference to `VLM_route_table' netlink-socket.o:(.debug_info+0x185e): undefined reference to `VLM_netlink_socket' stress.o:(.debug_info+0x5de): undefined reference to `VLM_stress' These VLM_* doesn't reside in any source code, but only in *.o files. Can anyone shed me some light on where these VLM_* label comes from and how to resolve this problem? I used "ovs_cv_use_linker_sections=no" as I configure the build environment. Many thanks! Cheers, Te-Yuan On Fri, Feb 4, 2011 at 4:08 PM, Yongqiang Liu <[email protected]> wrote: > Got it. > My mis-understanding, i thought "all datapaths" refer to all existing > datapaths which are created by ./ovs-dpctl add-dp dpx command. > No, it doesn't cause any problem for me. > > Thanks > > 2011/2/4 Ben Pfaff <[email protected]> >> >> On Fri, Feb 04, 2011 at 03:52:43PM -0800, Yongqiang Liu wrote: >> > Now there is an interesting problem with ./ovs-dpctl show command. >> > It will silently create many dpx devices in /dev/net. >> >> This is true. >> >> > 4. but if there in argument dp0, it has a problem: it creates extra 254 >> > devices in /dev/net/ >> > # ./ovs-dpctl show >> >> Do you mean, if there is *no* argument dp0? That is what your example >> shows. >> >> This is because the "show" command without any argument scans for every >> possible datapath. There are 256 possible datapaths numbered 0 through >> 255, so it has to create a device for each one in order to try to open >> it. >> >> It's not normally a problem. Does it cause a problem for you? >> >> At any rate, the current "master" branch in OVS does not create any >> devices at all. It uses Netlink instead. > > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org > > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
