openvswitch icon indicating copy to clipboard operation
openvswitch copied to clipboard

compile error

Open ashkal opened this issue 12 years ago • 5 comments

/home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0/datapath/linux/actions.c: In function 'pop_vlan': /home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0/datapath/linux/actions.c:104:2: error: too few arguments to function '__vlan_hwaccel_put_tag' include/linux/if_vlan.h:237:31: note: declared here /home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0/datapath/linux/actions.c: In function 'push_vlan': /home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0/datapath/linux/actions.c:124:2: error: too few arguments to function '__vlan_hwaccel_put_tag' include/linux/if_vlan.h:237:31: note: declared here make[8]: *** [/home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0/datapath/linux/actions.o] Error 1 make[7]: *** [module/home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0/datapath/linux] Error 2 make[7]: Leaving directory /home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/linux-3.10.3' make[6]: *** [default] Error 2 make[6]: Leaving directory/home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0/datapath/linux' make[6]: Entering directory /home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0' make[6]: Leaving directory/home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory /home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0' make[4]: *** [all] Error 2 make[4]: Leaving directory/home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0' make[3]: *** [/home/ashkan/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openvswitch-1.9.0/.built] Error 2 make[3]: Leaving directory /home/ashkan/openwrt/openwrt/feeds/openvswitch/openvswitch' make[2]: *** [package/feeds/openvswitch/openvswitch/compile] Error 2 make[2]: Leaving directory/home/ashkan/openwrt/openwrt' make[1]: *** [/home/ashkan/openwrt/openwrt/staging_dir/target-mips_r2_uClibc-0.9.33.2/stamp/.package_compile] Error 2 make[1]: Leaving directory `/home/ashkan/openwrt/openwrt' make: *** [world] Error 2

ashkal avatar Jul 29 '13 21:07 ashkal

Unfortunately, there is no easy fix to this. Only OvS 1.12.x supports kernel 3.10 but lacks the bridge compat stuff which is required for compatibility with netifd. I would love to have OvS support in the netifd, but right now I don't have the time to do this. Hence, the easiest is to pick another kernel for your target if available. With "Attitude Adjustment" it should work, since it has kernel 3.3 support for the common targets. Could you please provide a dump of the output of "cat .config | grep -e '^CONFIG_TARGET'" from your OpenWrt config file.

The OvS FAQ lists the supported kernel versions and OvS releases: 141 Open vSwitch Linux kernel 142 ------------ ------------- 143 1.4.x 2.6.18 to 3.2 144 1.5.x 2.6.18 to 3.2 145 1.6.x 2.6.18 to 3.2 146 1.7.x 2.6.18 to 3.3 147 1.8.x 2.6.18 to 3.4 148 1.9.x 2.6.18 to 3.8 149 1.10.x 2.6.18 to 3.8 150 1.11.x 2.6.18 to 3.8 151 1.12.x 2.6.18 to 3.10

schuza avatar Aug 16 '13 00:08 schuza

BTW if you don't need netifd support I can push a Makefile for OvS 1.12 or trunk in a separate branch!

schuza avatar Aug 16 '13 00:08 schuza

Hi, could you push the makefile for OvS 1.12 as you offered in the previos post? THX

krumpligumo avatar Nov 20 '13 23:11 krumpligumo

I'm working with 2.0 already. Since all recent versions have no support for br-compat anymore I don't really wan't to push it to master. The reason is, that all newer versions have the requirement, that someone has a serial line attached to the node! I could push it to a branch, though.

Make sure, that you have a serial console attached to the node. Otherwise, just use Attitude Adjustment and this repo as a feed for OvS.

schuza avatar Nov 22 '13 23:11 schuza

JFI, here's a first RFC patch integrating openvswitch into netifd: https://www.mail-archive.com/[email protected]/msg20974.html

helmut-jacob avatar Dec 04 '13 16:12 helmut-jacob