Home / 1.3.1
Name Modified Size InfoDownloads / Week
Parent folder
README.md 2016-09-23 3.0 kB
libjpeg-turbo-1.3.1.tar.gz.sig 2016-09-23 72 Bytes
libjpeg-turbo-official-1.3.1.i386.rpm 2015-08-15 931.9 kB
libjpeg-turbo-official-1.3.1.src.rpm 2015-08-15 1.4 MB
libjpeg-turbo-official-1.3.1.x86_64.rpm 2015-08-15 818.5 kB
libjpeg-turbo-official_1.3.1_i386.deb 2015-08-15 927.3 kB
libjpeg-turbo-official_1.3.1_amd64.deb 2015-08-15 854.0 kB
libjpeg-turbo-official32_1.3.1_amd64.deb 2015-08-15 685.5 kB
libjpeg-turbo-1.3.1-vc64.exe 2015-08-15 1.1 MB
libjpeg-turbo-1.3.1-vc.exe 2015-08-15 991.9 kB
libjpeg-turbo-1.3.1-gcc64.exe 2015-08-15 1.1 MB
libjpeg-turbo-1.3.1-gcc.exe 2015-08-15 1.2 MB
libjpeg-turbo-1.3.1.tar.gz 2014-03-22 1.4 MB
libjpeg-turbo-1.3.1.dmg 2014-03-22 2.2 MB
libjpeg-turbo-1.3.1-jws.zip 2014-03-22 947.8 kB
Totals: 15 Items   14.6 MB 210

Package signatures

To ensure the integrity of the libjpeg-turbo binary packages, the RPM and DEB files and the source tarball are signed using the following key:
http://www.libjpeg-turbo.org/key/LJT-GPG-KEY-1024
http://pgp.mit.edu/pks/lookup?op=get&search=0x85C7044E033FDE16
and the Windows installers are signed using a code signing certificate.

Packaging changes

  • The libjpeg-turbo Project is now maintaining its own repository for Cygwin packages. See http://www.libjpeg-turbo.org/Documentation/Cygwin for more details.
  • A new copy of libjpeg-turbo-1.3.1-gcc64.exe was uploaded on 2014-04-20 to fix a segfault that occurred when an application that was built with a recent (GCC 4.8.x) implementation of MinGW tried to use setjmp/longjmp to trap/throw libjpeg errors via a custom error manager. It is unknown why this segfault occurred, but the 64-bit GCC version of libjpeg-turbo was formerly built with GCC 4.5.x, and upgrading the build machine to use GCC 4.8.x instead seems to have fixed the issue-- as well as maintained the ability to use the libjpeg-turbo libraries with older versions of GCC.

1.3.1

Significant changes relative to 1.3.0:

  1. On Un*x systems, make install now installs the libjpeg-turbo libraries into /opt/libjpeg-turbo/lib32 by default on any 32-bit system, not just x86, and into /opt/libjpeg-turbo/lib64 by default on any 64-bit system, not just x86-64. You can override this by overriding either the prefix or libdir configure variables.

  2. The Windows installer now places a copy of the TurboJPEG DLLs in the same directory as the rest of the libjpeg-turbo binaries. This was mainly done to support TurboVNC 1.3, which bundles the DLLs in its Windows installation. When using a 32-bit version of CMake on 64-bit Windows, it is impossible to access the c:\WINDOWS\system32 directory, which made it impossible for the TurboVNC build scripts to bundle the 64-bit TurboJPEG DLL.

  3. Fixed a bug whereby attempting to encode a progressive JPEG with arithmetic entropy coding (by passing arguments of -progressive -arithmetic to cjpeg or jpegtran, for instance) would result in an error, Requested feature was omitted at compile time.

  4. Fixed a couple of issues (CVE-2013-6629 and CVE-2013-6630) whereby malformed JPEG images would cause libjpeg-turbo to use uninitialized memory during decompression.

  5. Fixed an error (Buffer passed to JPEG library is too small) that occurred when calling the TurboJPEG YUV encoding function with a very small (< 5x5) source image, and added a unit test to check for this error.

  6. The Java classes should now build properly under Visual Studio 2010 and later.

  7. Fixed an issue that prevented SRPMs generated using the in-tree packaging tools from being rebuilt on certain newer Linux distributions.

  8. Numerous minor fixes to eliminate compilation and build/packaging system warnings, fix cosmetic issues, improve documentation clarity, and other general source cleanup.

Source: README.md, updated 2016-09-23