[ovs-discuss] problems with kmod-openvswitch rpmbuild and kernel-2.6.32-279.2.1.el6

Ben Pfaff blp at nicira.com
Wed Jul 25 17:39:06 UTC 2012


On Wed, Jul 25, 2012 at 09:58:39AM +0200, Gianluca Cecchi wrote:
> On Wed, Jul 25, 2012 at 12:55 AM, Jesse Gross wrote:
> > Yes, that patch should solve the problem.  The newer kernels caused
> > conflicts with some of the backports in OVS.
> 
> Yes, the only problem was that due to acinclude.m4 between the modified files.
> So I also needed to run
> autoreconf -f -i
> but it fails on CentOS 6.3
> 
> configure.ac:15: error: Autoconf version 2.64 or higher is required
> configure.ac:15: the top level
> autom4te: /usr/bin/m4 failed with exit status: 63
> aclocal: autom4te failed with exit status: 63
> autoreconf: aclocal failed with exit status: 63
> 
> release packages are
> autoconf-2.63-5.1.el6.noarch
> automake-1.11.1-1.2.el6.noarch
> 
> I solved running the autoreconf command on a Fedora 17 system against
> the patched tree and then recomposing the tar.gz and then build
> successfully on CentOS 6.3 via the provided spec file.

Yes, that's what I'd recommend doing.

> Also, during build I got
> 
> Processing files: kmod-openvswitch-1.6.1-1.el6.x86_64
> Finding  Provides: /usr/lib/rpm/redhat/find-provides
> 
> ********************************************************************************
> *********************** KERNEL ABI COMPATIBILITY WARNING ***********************
> ********************************************************************************
> The kernel ABI reference files (provided by kabi-whitelists) were not found.
> No compatibility check was performed. Please install the kABI reference files
> and rebuild if you would like to verify compatibility with kernel ABI.
> It could be useful to include kabi-whitelists between the
> BuildRequires directives for openswitch-kmod

Can you show us what to do?  I don't know anything about this.

> btw: I also had to apply for 6.3 a workaround as in
> https://bugzilla.redhat.com/show_bug.cgi?id=842038
> to get at the end:

Is that something we need to apply to OVS or something that needs to
be applied on the system itself?



More information about the discuss mailing list