Hi Ben, hi Reinhard, On Di 24 Jan 2012 16:42:09 CET Benjamin Shadwick wrote:
Those bug threads actually make me *less* nervous. The first one explains that libjpeg-turbo is just a derivative of standard libjpeg that uses SIMD instructions to accelerate functionality by 2-4x. The second mentions that there have been improvements to libjpeg-turbo to make it ABI-compatible with libjpeg8. Looking at the readme ( http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/trunk/README-turbo.txt) on the (still active) sourceforge project shows that by default it is API/ABI compatible with libjpeg v6b, which is what is currently most widely used. It can also be configured to be compatible with v7 or v8 instead, but there are a few v7+ features that are not supported. -- - Ben S.
after some more reading I must say I (at least by theory) agree with Benjamin. It is rather simple to enable libjpeg v8 emulation in libjpeg-turbo. So for squeeze, I will leave 6b emulation mode in our package, and for wheezy+ I enable v8 emulation and build new packages.
Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: [email protected], http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgpCUEzeGM0id.pgp
Description: Digitale PGP-Unterschrift
_______________________________________________ X2go-Dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-dev
