Bug#573881: alsa-lib: subsequent builds produce different library symbols

2010-12-27 Thread Andres Salomon
fixed 573881 1.0.23-2.1 thanks I've just tested smcv's debian/patches/libtool-out-of-tree.patch; it does indeed fix the problem in the latest package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#573881: alsa-lib: subsequent builds produce different library symbols

2010-12-24 Thread Daniel Chen
tags 573881 + fixed-upstream upstream thanks commit 443c1057379f167639acad5dc197bd50a915b5ab Author: Simon McVittie s...@debian.org Date: Fri Oct 8 09:06:29 2010 +0100 Version-check libtool correctly when doing an out-of-tree build libtool is only created at the end of ./configure, so

Bug#573881: alsa-lib: subsequent builds produce different library symbols

2010-10-08 Thread Simon McVittie
On Sun, 14 Mar 2010 at 13:48:19 -0400, Andres Salomon wrote: checking for library version... major 1 minor 0 subminor 22 extrastr extraver 100 -checking for versioned symbols... yes +checking for versioned symbols... grep: libtool: No such file or directory +./configure: line 11083:

Bug#573881: alsa-lib: subsequent builds produce different library symbols

2010-03-14 Thread Andres Salomon
Package: alsa-lib Version: 1.0.22-2 Severity: important The first time kicking off an alsa-lib build on a squeeze machine results in the following: dilin...@droptest:~/alsa-lib-1.0.22$ objdump -T debian/libasound2/usr/lib/libasound.so.2|grep snd_pcm_hw_params_get_channels_min 0004ce50 gDF

Bug#573881: alsa-lib: subsequent builds produce different library symbols

2010-03-14 Thread 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