Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42696 - libfreeimage bundled libjpeg conflicts with system libjpeg

Attached to Project: Community Packages
Opened by Alex (nylocx) - Thursday, 06 November 2014, 14:14 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 06 November 2014, 15:16 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The current upstrem version of libfreeimage supplied by the community/freeimage package in version 3.16.0 staticly links against libjpeg.so.9 the supplied libjpeg version in arch by the extra/libjpeg-turbo package is in version 8 and as they state on their website they have no intention of upgrading the api/abi.See: www.libjpeg-turbo.org/About/Jpeg-9

So when ever you link a tool against libfreeimage and libjpeg, for example by linking a Qt application which loads libjpeg as dependency of the imageformats plugins, your application will crash with an error like: Wrong JPEG library version: library is 90, caller expects 80
Or it won't even link.

The only solution I see (if the developers of libfreeimage can't be convinced to downgrade their bundled libjpeg) is to patch the package which will be quiet complicated or to stick with 3.15.0 of libfreeimage.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 06 November 2014, 15:16 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#31761 

Loading...