Statically linking to a library that's also "included" in a shared library

Statically linking to a library that's also "included" in a shared library

Post by Joe Pfeiff » Fri, 21 Aug 2009 00:23:01


fia_wrc_fanatic < XXXX@XXXXX.COM > writes:


After reading several later posts in the thread, this just sounds very
unlikely to me. I don't, off the top of my head, see a reason why
calling ghostscript's version of libjpeg will cause the memory
corruption and segfault you're seeing (absent a bug in either
ghostscript or libjpeg, of course). I'd put that on a back burner
and look elsewhere for the problem for a while.
--
Klingon programs don't have parameters. They have arguments and win
them (Walter Bushell)