On 10/04/2013 12:19 AM, Michal Privoznik wrote:
On 28.09.2013 04:55, Eric Blake wrote:
> I tried to test ./configure --without-lxc --without-remote.
> First, the build failed with some odd errors, such as an
> inability to build xen, or link failures for virNetTLSInit.
> But when you think about it, once there is no remote code,
> all of libvirtd is useless, any stateful driver that depends
> on libvirtd is also not worth compiling, and any libraries
> used only by RPC code are not needed. So I patched
> configure.ac to make for some saner defaults when an
> explicit disable is attempted. Similarly, since we have
> migrated virnetdevbridge into generic code, the workaround
> for Linux kernel stupidity must not depend on stateful
> drivers being in use.
>
ACK
Although I get this error when running 'make check'. Not a show stopper - this
patch fixes the build (I'm able to build --without-remote now), but would be nice if
you can get rid of it too.
Making check in src
make[1]: Entering directory `/home/zippy/work/libvirt/libvirt.git/src'
make check-am
make[2]: Entering directory `/home/zippy/work/libvirt/libvirt.git/src'
make check-local
make[3]: Entering directory `/home/zippy/work/libvirt/libvirt.git/src'
GEN check-symfile
GEN check-symsorting
GEN check-drivername
GEN check-driverimpls
Can't open ./remote/remote_protocol.c: No such file or directory at
./check-driverimpls.pl line 29, <> line 140903.
Eww - that's what I get for testing in an incremental tree, rather than
a fresh clone. I'll clean that up as a separate patch.
Meanwhile, I've pushed this one.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library
http://libvirt.org