[Pkg-alsa-devel] Bug#505088: alsa-lib: fails to build twice in a row

[Lionel Elie Mamane]

On Thu, Sep 03, 2009 at 04:16:57PM +0200, Elimar Riesebieter wrote:
> * Lionel Elie Mamane [081119 00:55 +0100]
>> On Tue, Nov 18, 2008 at 07:47:05PM +0100, Elimar Riesebieter wrote:
>>> * Lionel Elie Mamane [081111 12:30 +0100]

>>>> Usually, a cleaner solution is using AM_MAINTAINER_MODE; you seem
>>>> to patch it into configure.ac, but not in configure... So my
>>>> suggestion would be to put the add-maintainer-mode patch BEFORE
>>>> the relibtoolise patch, and then regenerate the relibtoolise
>>>> patch (so that AM_MAINTAINER_MODE is active when this patch
>>>> regenerates ./configure and the Makefile.in's, and then
>>>> AM_MAINTAINER_MODE is actually active).

>>> The range of patching shouldn't matter in that case. Could you
>>> please try the following patch against debian/rules

>> No, it does not fix the problem. I tested it, the second build still
>> fails, with the same symptoms for the same reasons.

>> The problem is that the configure which is run (the one that is there
>> after "make -f debian/rules patch") does not support the concept of
>> maintainer mode, because it was generated from a configure.ac that did
>> not have AM_MAINTAINER_MODE. I already described how to fix that,
>> above.

>> Here is a patch that makes what I described. It works.

> It's not reproducible.

Have you tried with a nanosecond-timestamp-precision filesystem, with
the autotools installed? Or by emulating the effect of a
high-precision-timestamp filesystem by slowing down quilt as I
described previously in the bug? As explained previously, the bug only
shows up reliably under these conditions; on a
second-timestamp-precision filesystem like ext2/ext3, it shows up
pretty rarely (depending on speed of the machine).

> Please confirm to close this bug.

I still get the bug with 1.0.20-3, so I don't think it should be
closed.

-- 
Lionel