Bug#693040: libav: Strange build failure on several archs

2012-11-14 Thread Reinhard Tartler
On Wed, Nov 14, 2012 at 9:29 AM, Fabian Greffrath wrote: > Am 13.11.2012 16:45, schrieb Reinhard Tartler: > >> The problem is upstream and has been identified now. Reverting >> upstream commit 468ea9d5b14f92fe61f47f034e67066f65163f5f seems to fix >> the issue, albeit a better solution is currently

Bug#693040: libav: Strange build failure on several archs

2012-11-14 Thread Fabian Greffrath
Am 13.11.2012 16:45, schrieb Reinhard Tartler: The problem is upstream and has been identified now. Reverting upstream commit 468ea9d5b14f92fe61f47f034e67066f65163f5f seems to fix the issue, albeit a better solution is currently being worked on. Good to know that you've succeeded to narrow down

Processed: Re: Bug#693040: libav: Strange build failure on several archs

2012-11-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 693040 +upstream -help Bug #693040 [libav] libav: Strange build failure on several archs Added tag(s) upstream. Bug #693040 [libav] libav: Strange build failure on several archs Removed tag(s) help. > stop Stopping processing here. Please co

Bug#693040: libav: Strange build failure on several archs

2012-11-13 Thread Reinhard Tartler
tags 693040 +upstream -help stop On Mon, Nov 12, 2012 at 12:09 PM, Reinhard Tartler wrote: > I require assistance from a toolchain savy expert. I have uploaded a new > upstream version of libav to experimental. The problem is upstream and has been identified now. Reverting upstream commit 468ea

Bug#693040: libav: Strange build failure on several archs

2012-11-13 Thread Reinhard Tartler
On Mon, Nov 12, 2012 at 1:09 PM, Fabian Greffrath wrote: > Am 12.11.2012 12:09, schrieb Reinhard Tartler: > >> I don't get it. The symbol ff_log2_tab is defined in this file: >> >> http://anonscm.debian.org/gitweb/?p=pkg-multimedia/libav.git;a=blob;f=libavutil/log2_tab.c, >> and libavutil is being

Bug#693040: libav: Strange build failure on several archs

2012-11-13 Thread Reinhard Tartler
[CC'ing debian-gcc@ for additional input, libav fails to link on armel, s390, s390x, ia64 and sparc. see bug #693040 for full context] On Mon, Nov 12, 2012 at 12:45 PM, Bastian Blank wrote: > On Mon, Nov 12, 2012 at 12:09:57PM +0100, Reinhard Tartler wrote: >> I've tried to reproduce the problem

Bug#693040: libav: Strange build failure on several archs

2012-11-12 Thread Paul Gevers
> Oh, and a third possibility: at the time of linking avconv (i.e. the > command that fails) dependency of libavfilter/libavfilter.so to libavutil > is resolved using a wrong library (not the one from /usr which is fine and > not libavutil/libavutil.so which we assume to be fine). In the compiler

Bug#693040: libav: Strange build failure on several archs

2012-11-12 Thread Fabian Greffrath
Am 12.11.2012 12:09, schrieb Reinhard Tartler: I don't get it. The symbol ff_log2_tab is defined in this file: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/libav.git;a=blob;f=libavutil/log2_tab.c, and libavutil is being linked into the library. Moreover, only armel, s390, s390x and sparc ar

Re: Bug#693040: libav: Strange build failure on several archs

2012-11-12 Thread Reinhard Tartler
On Mon, Nov 12, 2012 at 12:09 PM, Reinhard Tartler wrote: > The symbol ff_log2_tab is defined in this file: > http://anonscm.debian.org/gitweb/?p=pkg-multimedia/libav.git;a=blob;f=libavutil/log2_tab.c, > and libavutil is being linked into the library. Moreover, only armel, > s390, s390x and sparc

Bug#693040: libav: Strange build failure on several archs

2012-11-12 Thread Reinhard Tartler
Package: libav Version: 6:9~beta2-2 Severity: important Tags: help I require assistance from a toolchain savy expert. I have uploaded a new upstream version of libav to experimental. Unfortunately, it fails to build on several architectures with the following error: gcc -Llibavcodec -Llibavdevic