Bug#653061: libgs9 exports symbols conflicting with the same symbols in libjpeg8

[Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>]

On Fri, Dec 23, 2011 at 11:27:18PM +0100, Bill Allombert wrote:
> On Fri, Dec 23, 2011 at 03:46:59PM -0600, Jonathan Nieder wrote:
> > Hi,
> > 
> > Jean Brefort wrote:
> > 
> > > Three symbols are concerned:
> > > jpeg_mem_init, jpeg_mem_term and jpeg_mem_available.
> > >
> > > Building an executable using the two libraries might crash. This happens for me
> > > with gnumeric (from git) when goffice is built with eps support and when I try
> > > to add a jpeg image inside a sheet.
> 
> Hello,
> 
> Since libjpeg8 uses versionned symbols, I would suggest libgs9 to use different
> symbol version for these three symbols.
> 
> > More details would be useful, including a stacktrace or error messages
> > if possible.
> > 
> > >From gs/base/sjpegc.c:
> > 
> > 	  Ghostscript uses a non-public interface to libjpeg in order to
> > 	  override the library's default memory manager implementation.
> 
> Is it still necessary with libjpeg8 ?
> 
> > Do you know if libjpeg provides a way to use a custom allocator
> > without interfering with other modules in the same process image
> > that might not want to use it?
> 
> I will ask upstream.

The short answer is that it is not possible.
But you can use versionned symbols.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.