[ovs-dev] Bug#651798: Bug#651798: Fails to build against Linux 3.1

Simon Horman horms at verge.net.au
Mon Dec 12 08:26:08 UTC 2011


On Mon, Dec 12, 2011 at 08:00:25AM +0000, Ben Hutchings wrote:
> Package: openvswitch-datapath-source
> Version: 1.2.2-2
> Severity: grave
> 
> This module fails to build against Linux 3.1:
> 
> make[3]: Entering directory `/usr/src/linux-headers-3.1.0-1-amd64'
> /usr/src/linux-headers-3.1.0-1-common/arch/x86/Makefile:81: stack protector enabled but no compiler support
>   CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/genetlink-brcompat.o
>   CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/brcompat.o
>   CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/actions.o
>   CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/checksum.o
>   CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/datapath.o
> /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/datapath.c:58:2: error: #error Kernels before 2.6.18 or after 3.0 are not supported by this version of Open vSwitch.
> make[6]: *** [/usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/datapath.o] Error 1
> make[5]: *** [_module_/usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux] Error 2
> make[4]: *** [sub-make] Error 2
> make[3]: *** [all] Error 2
> make[3]: Leaving directory `/usr/src/linux-headers-3.1.0-1-amd64'
> 
> Since a version of Open vSwitch has been accepted for inclusion in
> mainline Linux 3.3, perhaps it could be included in Debian kernel
> packages starting with Linux 3.2 and then this binary package could be
> removed.  However I don't know whether the mainline version is fully-
> featured.

Hi Ben,

the mainline version is fully featured and I envisage that the
openvswitch-datapath package can be removed from the archive at some point.
I would value your input on how that might be best achieved.

As for the compile problem below, this is intended by upstream,
though perhaps isn't appropriate for Debian. I'll take guidance
on that issue from upstream.





More information about the dev mailing list