[ovs-discuss] Installing OVS 1.7.1 on SLES 10.1

Jesse Gross jesse at nicira.com
Mon Nov 26 21:30:14 UTC 2012


On Mon, Nov 26, 2012 at 3:56 AM, Arindam Choudhury
<arindamchoudhury0 at gmail.com> wrote:
> Hi,
>
> I am trying to install ovs 1.7.1 on SLES 10.1 (kernel 2.6.32.60, make 3.80,
> gcc 4.1.2). I am getting the following errors:
>
> openvswitch-1.7.1> make
> make  all-recursive
> make[1]: Entering directory `/home/arindam/Desktop/openvswitch-1.7.1'
> Making all in datapath
> make[2]: Entering directory
> `/home/arindam/Desktop/openvswitch-1.7.1/datapath'
> Making all in linux
> make[3]: Entering directory
> `/home/arindam/Desktop/openvswitch-1.7.1/datapath/li nux'
> make -C /lib/modules/2.6.32.60-PAPI-KVM/build
> M=/home/arindam/Desktop/openvswitc h-1.7.1/datapath/linux modules
> make[4]: Entering directory
> `/usr/src/packages/BUILD/kernel-2.6.32.60PAPIKVM'
>   CC [M]
> /home/arindam/Desktop/openvswitch-1.7.1/datapath/linux/genetlink-brcom pat.o
> In file included from include/linux/gfp.h:4,
>                  from include/linux/kmod.h:22,
>                  from include/linux/module.h:13,
>                  from include/linux/textsearch.h:7,
>                  from include/linux/skbuff.h:27,
>                  from
> /home/arindam/Desktop/openvswitch-1.7.1/datapath/linux/com
> pat/include/linux/skbuff.h:4,
>                  from
> /home/arindam/Desktop/openvswitch-1.7.1/datapath/linux/com
> pat/include/linux/netlink.h:4,
>                  from
> /home/arindam/Desktop/openvswitch-1.7.1/datapath/linux/com
> pat/include/net/genetlink.h:5,
>                  from
> /home/arindam/Desktop/openvswitch-1.7.1/datapath/linux/com
> pat/genetlink.inc:3,
>                  from
> /home/arindam/Desktop/openvswitch-1.7.1/datapath/linux/gen
> etlink-brcompat.c:10:
> include/linux/mmzone.h:18:26: error: linux/bounds.h: No such file or
> directory
> include/linux/mmzone.h:258:5: warning: "MAX_NR_ZONES" is not defined

bounds.h (which contains all the constants that can't be found) is an
autogenerated fine.  Are you sure that you are pointing to the right
kernel header directory and that they are properly configured?



More information about the discuss mailing list