John,

The readme I linked explains how to do it. Basically, you have to re-run the configure script and re-build the library from source to produce a v7 or v8 ABI-compatible version.

On Tue, Jan 24, 2012 at 9:53 AM, John Williams <jwilliams4200@gmail.com> wrote:
On Tue, Jan 24, 2012 at 9:04 AM, Mike Gabriel
<mike.gabriel@das-netzwerkteam.de> wrote:

> 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.

How does one enable "v8 emulation" for libjpeg-turbo?

I've been using x2go on Archlinux, and Arch uses libjpeg-turbo by
default. I have not noticed any specific x2go problems that I can
attribute to libjpeg-turbo, but I have been plagued by a lot of issues
that I have assumed were due to x2goclient, but perhaps not all of
them are the client's fault.
_______________________________________________
X2go-Dev mailing list
X2go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev



--
- Ben S.