Weird. I'd expect the jpeg symbols in gs to be resolved against the internal versions when the library is linked. Would it help to supply an exported symbol list? That would break anyone trying to use the graphics library directly, of course.
Ghostscript can actually link against the system libjpeg, but at the cost of not being able to support some files. The DCTDecode filter in Postscript was finalized before the baseline jpeg standard, and block runs are allowed to be longer that stock libjpeg will accept. It's just a define change, but that's why we compile against an internal version. -- libjpeg conflict in libgs https://bugs.launchpad.net/bugs/182623 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
