[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] [PATCH] Fixes for check and rpm builds without sanlock (and qemu)

Martin help me find a root reason, I don't know when the src/locking/test_libvirt_sanlock.aug.in
is deleted from my git repo, in fact, I have never manually done it by myself except running
'make', 'make clean' or 'make rpm' ago, it's weird for me. 

Martin, Thanks.

----- Original Message -----
From: "Alex Jia" <ajia redhat com>
To: "Eric Blake" <eblake redhat com>
Cc: libvir-list redhat com, "Martin Kletzander" <mkletzan redhat com>
Sent: Monday, June 4, 2012 10:34:44 AM
Subject: Re: [libvirt] [PATCH] Fixes for check and rpm builds without sanlock (and qemu)

On 06/01/2012 10:50 PM, Eric Blake wrote:
> On 05/31/2012 08:22 PM, Alex Jia wrote:
>>>> make[3]: Entering directory `/home/ajia/Workspace/libvirt/src'
>>>> make[3]: *** No rule to make target
>>>> `locking/test_libvirt_sanlock.aug.in', needed by
>>>> `test_libvirt_sanlock.aug'.  Stop.
>>>> </snip>
>>> How is that possible?  Are you building from libvirt.git (where
>>> src/locking/test_libvirt_sanlock.aug.in is part of the repo) or from a
>>> tarball (and if so, how did you create the tarball)?  Are you doing an
I worked at libvirt upstream without trying/making any tarball.
>>> in-tree build or a VPATH build?
I have ever done 'make rpm' then 'make clean' to clean my env, but it 
seems some garbage
are reserved on my repo. Isn't 'make clean' okay to clean up previous env?
>> Ah, I need to clarify this problem, I shouldn't directly reply this
>> mail, in fact, my problem hasn't
>> relationship with this fixing, it just is a compiling error when run
>> 'make' not 'make rpm', then I
>> will meet the above issue.
> I still need exact steps to reproduce the issue before I can fix
> anything, if there is anything to be reproduced.  You answered that you
> triggered it with 'make', but was this on a fresh 'git clone' or an
> incremental tree that might have garbage lying around from earlier
I guess it's a root reason for my dirty env, but I still can meet the 
issue after running 'make clean', I don't want to run 'git clone' to get 
a new repo, it will miss a chance to find a final reason, so I reserve
my old repo, please feel free to contact me on #libvirt-qe IRC then 
check it. thanks.
> builds?  And you didn't answer whether you were doing a VPATH or in-tree
> build.
I just done regular libvirt compiling without any build now then meet 
the problem again.


libvir-list mailing list
libvir-list redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]