[Pkg-alsa-devel] Bug#573881: alsa-lib: subsequent builds produce different library symbols

[Andres Salomon]

Hi,

The problems is the deletion of the top-level libtool script.  An easy
fix for this is to just remove the distclean rule that does it; the
patch below does just that.

However, this isn't really the correct fix.  The libtool script
shouldn't be listed in EXTRA_DIST, and it shouldn't really be relied
upon.  See
http://stackoverflow.com/questions/1436758/libtool-deleted-by-make-distclean
for a description of the problem, and how it should be handled.

Note that this should be applied *after*
debian/patches/relibtoolise.patch!




From 7047af1f3b3554d7bf5d1a3d1af7465dc4f65fa2 Mon Sep 17 00:00:00 2001
From: Andres Salomon <dilinger at collabora.co.uk>
Date: Sun, 14 Mar 2010 15:17:40 -0400
Subject: [PATCH] alsa-lib: don't remove libtool script on distclean

Removing the top-level libtool script causes configure to fail to handle
symbols properly.  This is a temporary fix; the real fix would be to not
use the top-level libtool script at all.

See
http://stackoverflow.com/questions/1436758/libtool-deleted-by-make-distclean
for an example of someone w/ the same problem ($(topdir)/libtool being
removed despite it being listed in EXTRA_DIST).

Signed-off-by: Andres Salomon <dilinger at collabora.co.uk>
---
 Makefile.in |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Makefile.in b/Makefile.in
index aaac740..fc9d622 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -289,7 +289,7 @@ clean-libtool:
 	-rm -rf .libs _libs
 
 distclean-libtool:
-	-rm -f libtool config.lt
+	-rm -f config.lt
 
 # This directory's subdirectories are mostly independent; you can cd
 # into them and run `make' without going through this Makefile.
-- 
1.7.0