"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
Jan> Yes, but on many platforms static linking is a no-no
anyway.
Jan> Especially binaries for linux distributions (that can control
Jan> the versions of all the libraries) should not be statically
Jan> linked.
Bull.
No its not. There are simply exceptions to the rule. I would be very
annoyed if my linux distributor started linking everything static.
There are all sorts of good reasons for static linking, even on
Linux. For example, due to Adobe brain-deadness (sm), the standard
libjpeg is incompatible with Adobe Postscript (tm) usage. So
Ghostscript by default statically links a modified version of libjpeg,
with the Adobe brain-deadness built in.
So Ghostscript does not need to be linked with libjpeg but with
libadobe-jpeg-braindamage (probably conveniently named libjpeg by the
Ghostscript sources.)
(Most Linux distributors ignore this for some reason. Sigh.)
Because previously the ghostscript came with its own libjpeg just for
convenience. Probably the Ghostscript documentation was not clear
enough about the change [which doesn't surprise me because
Ghostscripts documentation is at the very least "incoherent"].
Jan