Bug#786438: libmp3lame0: general protection error in libmp3lame.so.0.0.0

Felipe Sateler fsateler at debian.org
Mon Jun 1 15:12:36 UTC 2015


Trimming cc list because this is only semi-related to the bug, but...

On 1 June 2015 at 02:45, Fabian Greffrath <fabian at debian.org> wrote:
> This is from the diff of both build logs (wheezy and jessie) during
> the ./configure phase:
>
> @@ -440,9 +566,9 @@
> checking sys/time.h presence... yes
> checking for sys/time.h... yes
> checking for unistd.h... (cached) yes
> -checking xmmintrin.h usability... no
> -checking xmmintrin.h presence... no
> -checking for xmmintrin.h... no
> +checking xmmintrin.h usability... yes
> +checking xmmintrin.h presence... yes
> +checking for xmmintrin.h... yes
> checking linux/soundcard.h usability... yes
> checking linux/soundcard.h presence... yes
> checking for linux/soundcard.h... yes
> [...]
> @@ -516,11 +642,12 @@
> checking if dynamic linking of the frontends is requested... yes
> checking glibc mathinline bug... no
> checking for termcap... yes
> -checking if I have to build the internal vector lib... no
> +checking if I have to build the internal vector lib... yes
> checking for nasm... /usr/bin/nasm
> checking for assembler routines for this processor type... yes
> checking for additional optimizations... full
> checking for debug options... no
> +checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating libmp3lame/Makefile
>
> I have no idea why xmmintrin.h was not detected on wheezy, but this is
> clearly the reason why different code paths have been chosen between
> wheezy and jessie and why the bug is only encountered in the latter.

In general I would strongly advise to specify all the flags you want
to enable and have the build system fail if they cannot be enabled. At
the same time, explicitly disable all flags not used in the debian
package.

Surprises are a lot less likely this way, and the build is less
brittle to build-in-dirty-env issues.

-- 

Saludos,
Felipe Sateler



More information about the pkg-multimedia-maintainers mailing list