Hi!
On 11/09/2017 05:30 PM, Ondřej Surý wrote:
this has been already fixed by upstream:
https://github.com/libjpeg-turbo/libjpeg-turbo/commit/02fa8f244e549edd3f3acf174b97157590d1b71e
Ah, nice. I didn't see that. Thanks for reporting the issue and
getting it fixed. Much appreciated!
(I gave
Hi,
this has been already fixed by upstream:
https://github.com/libjpeg-turbo/libjpeg-turbo/commit/02fa8f244e549edd3f3acf174b97157590d1b71e
(I gave DRC a Turris 1.x remote shell access for a proper fix...)
I'll pull the fix when I run the next maintenance rounds on my packages.
Ondrej
--
Ondř
Source: libjpeg-turbo
Version: 1:1.5.2-2
Followup-For: Bug #830180
User: debian-powe...@lists.debian.org
Usertags: powerpcspe
So, I just found this bug report because I noticed libjpeg-turbo FTBFS
on powerpcspe because the source code apparently blindly assumes that
all powerpc machines support Al
Control: tags -1 fixed-upstream
See:
https://github.com/libjpeg-turbo/libjpeg-turbo/issues/88#issuecomment-231820117
Package: src:libjpeg-turbo
Version: 1:1.5.0-1
Forwarded: https://github.com/libjpeg-turbo/libjpeg-turbo/issues/88
Tags: upstream patch
Dear packager,
jpeg-turbo does not currently works on PowerPC without altivec. This
has been reported upstream, so until this gets fixed properly, we are
suggesti
5 matches
Mail list logo