2012.01.22 16:53 "[Tiff] update on tiff 4.x in debian", by Jay Berkenbilt
- 2012.01.22 17:17 "Re: [Tiff] update on tiff 4.x in debian", by Bob Friesenhahn
-
2012.01.22 19:54 "Re: [Tiff] update on tiff 4.x in debian", by Bob Friesenhahn
-
2012.01.22 20:42 "Re: [Tiff] update on tiff 4.x in debian", by Bob Friesenhahn
-
2012.01.23 01:48 "Re: [Tiff] update on tiff 4.x in debian", by Jay Berkenbilt
- 2012.01.23 05:24 "Re: [Tiff] update on tiff 4.x in debian", by Tom Lane
-
2012.01.23 15:13 "Re: [Tiff] update on tiff 4.x in debian", by Bob Friesenhahn
-
2012.01.23 15:52 "Re: [Tiff] update on tiff 4.x in debian", by Jay Berkenbilt
- 2012.01.23 16:26 "Re: [Tiff] update on tiff 4.x in debian", by Tom Lane
- 2012.01.23 17:48 "Re: [Tiff] update on tiff 4.x in debian", by Jürgen_Buchmüller
-
2012.01.23 15:52 "Re: [Tiff] update on tiff 4.x in debian", by Jay Berkenbilt
-
2012.01.23 01:48 "Re: [Tiff] update on tiff 4.x in debian", by Jay Berkenbilt
-
2012.01.22 20:42 "Re: [Tiff] update on tiff 4.x in debian", by Bob Friesenhahn
2012.01.22 18:51 "Re: [Tiff] update on tiff 4.x in debian", by Olivier Paquet
On Sun, Jan 22, 2012 at 12:17 PM, Bob Friesenhahn <bfriesen@simple.dallas.tx.us> wrote:
to the 4.0.0 release. we are faced with the situation that an Now application built against a libtiff which does not use versioned symbols will stop working if a libtiff which uses versioned symbols is inserted in its place. defense against that is to increment A
Really? I thought only the opposite was true. Meaning if you link with a lib which has versioned symbols, you will always need them but if you link with a lib which doesn't have them, you can use any lib. It's still annoying but not quite as much.
Olivier