On Wed, Apr 04, 2012 at 01:47:59PM +0100, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Every now & then, with parallel builds, we get a failure to
> validate hvsupport.html.in. I eventually noticed that this
> is because we get 2 instances of the generator running at
> once.
Gah
On Wed, Apr 04, 2012 at 09:17:46AM -0600, Eric Blake wrote:
> On 04/04/2012 07:04 AM, Jiri Denemark wrote:
>
> >>
> >> We already list hvsupport.html.in in BUILT_SOURCES but this
> >> was not working. It turns out the flaw is that we were
> >> adding deps to the 'all:' target instead of the 'all-a
On 04/04/2012 07:04 AM, Jiri Denemark wrote:
>>
>> We already list hvsupport.html.in in BUILT_SOURCES but this
>> was not working. It turns out the flaw is that we were
>> adding deps to the 'all:' target instead of the 'all-am:'
>
> Oh, cool. I saw this several times myself and I was wondering
On Wed, Apr 04, 2012 at 13:47:59 +0100, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Every now & then, with parallel builds, we get a failure to
> validate hvsupport.html.in. I eventually noticed that this
> is because we get 2 instances of the generator running at
> once.
>
> We
From: "Daniel P. Berrange"
Every now & then, with parallel builds, we get a failure to
validate hvsupport.html.in. I eventually noticed that this
is because we get 2 instances of the generator running at
once.
We already list hvsupport.html.in in BUILT_SOURCES but this
was not working. It turns
