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

[Lionel Elie Mamane]

tags 505088 +patch
thanks

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.

The additional mucking in debian/rules is to ensure the "make
distclean" is made before undoing the quilt patches to the Makefile.in
and configure, etc" because else, the clean target reruns
config.status (after the quilt patches are undone...), which spoils
the whole thing again, because then libtoolise.patch does not apply
anymore. I'm not sure why config.status is rerun on clean, it really
should not be.

-- 
Lionel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 505088.patch
Type: text/x-diff
Size: 274560 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-alsa-devel/attachments/20081119/a3f7634a/attachment-0001.patch