AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2012.09.22 18:36 "[Tiff] Libtiff 3.9.7 released", by Bob Friesenhahn
2012.10.17 18:26 "Re: [Tiff] Que: ZIPSetupDecode errorhandling", by Henk Jan Priester
2012.10.17 17:23 "[Tiff] Que: ZIPSetupDecode errorhandling", by Henk Jan Priester
2012.10.17 17:35 "Re: [Tiff] Que: ZIPSetupDecode errorhandling", by Bob Friesenhahn
2012.10.17 17:54 "Re: [Tiff] Que: ZIPSetupDecode errorhandling", by Henk Jan Priester
2012.10.17 18:19 "Re: [Tiff] Que: ZIPSetupDecode errorhandling", by Bob Friesenhahn
2012.10.17 22:28 "Re: [Tiff] Que: ZIPSetupDecode errorhandling", by Graeme Gill
2012.10.18 08:09 "Re: [Tiff] Que: ZIPSetupDecode errorhandling", by Henk Jan Priester
2012.10.18 17:39 "Re: [Tiff] Que: ZIPSetupDecode errorhandling", by Frank Warmerdam
2012.10.19 07:23 "Re: [Tiff] Que: ZIPSetupDecode errorhandling", by Henk Jan Priester

2012.10.17 22:28 "Re: [Tiff] Que: ZIPSetupDecode errorhandling", by Graeme Gill

It is a common problem to build with one library and then find out that a different one is being used at run-time. If ldd shows that the system version is used rather than the one you built libtiff with, then that would be a problem.

Yes. If you want robust deployment, nothing beats static linking.

Graeme Gill.