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
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
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
[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
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 in the porter sid chroot on
>> zelenka.debian.org, but was not able to reproduce the situation. All
>> archs also seem to have the same
On Mon, Nov 12, 2012 at 12:09:57PM +0100, Reinhard Tartler wrote:
> I've tried to reproduce the problem in the porter sid chroot on
> zelenka.debian.org, but was not able to reproduce the situation. All
> archs also seem to have the same version of binutils/gcc.
Do you try it with -j2 or higher?
On Mon, Nov 12, 2012 at 12:09:57PM +0100, Reinhard Tartler wrote:
> 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 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
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
9 matches
Mail list logo
