On 07/01/2013 07:17 AM, chandrashekar shastri wrote:
On 06/29/2013 11:43 PM, Eric Blake wrote:
> On 06/17/2013 03:57 AM, chandrashekar shastri wrote:
>> Hi,
>>
>> I am compiling the libvirt from source and I am getting the following
>> error:
> We need more details - are you trying to compile libvirt.git (if so,
> what commit are you on), or a tarball (and if so, where did you download
> the tarball from)? What platform are you on? What versions of automake
> and autoconf do you have installed? Unless I can reproduce the failure,
> I can't do much to help debug it.
We pull from libvirt.git
Branch master SHA1 24d0e67aba6b9d62cfee95582f211b4d850373d3
Fedora ( x86_64) kernel version : 3.10.0-rc5+
That's not an actual Fedora release; I was asking more along the lines
of "Fedora 18" or "Fedora 19". Your automake version matched Fedora
18;
but your kernel version was more like Fedora 19; you're definitely
running a mixed-mode system. But thanks to some chatting on IRC, I
think I understand the problem well enough that I was still able to
write my patch on a stock F18 machine.
It looks like automake is failing because autogen.sh was not completely
run; and this in turn is due to bugs in the --no-git option. I think I
fixed the --no-git bugs with this patch pending review:
https://www.redhat.com/archives/libvir-list/2013-July/msg00232.html
Also, be sure that when you use --no-git that your copy of GNULIB_SRCDIR
matches the exact commit of gnulib.git that is recorded in libvirt.git.
As of today's commits, it is the latest gnulib.git commit; but this is
not always the case, and there have been historical instances where
using the latest gnulib is not compatible with latest libvirt.git
without further tweaks to libvirt (which is why we only do .gnulib
submodule updates to libvirt when we are not in release freeze).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library
http://libvirt.org