http://bugs.ghostscript.com/show_bug.cgi?id=692891
--- Comment #5 from Chris Liddell <chris.lidd...@artifex.com> 2012-03-02 12:07:56 UTC --- I've committed the first (possibly only) stage: http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=ceef32 So, we'll no longer do the libjpeg low level memory manager hackery if Ghostscript is linked with a shared libjpeg library. Now, I'm struggling to find an "official" way to setup memory management hooks described above. Currently the only way I see is writing our own version of jpeg_CreateCompress() (separate from the libjpeg one, not replacing the libjpeg one). I'm reluctant to do that because it could turn into a maintenance nightmare! It *looks* to me like that struct jpeg_memory_mgr stuff is still a *link* time option, not a run-time option. If anyone knows different, knows where I could ask (libjpeg development still seems a bit of a "black box"), or knows of an example that proves me wrong, please point me to it! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
