I was under the impression that 0.0.0 is actually a 'magic value' indicating that the linker shouldn't check versions *at all*. So even if it is the first release, it's not right. Does anybody know the details on the significance of 0.0.0?
Well, the package uses gnu libtool so 0:0:0 turns into compatibility version 1.0.0 current version 1.0.0 in a file named libfoo.0.0.0.dylib. It is not unversioned. If you do not specify -compatibility_version -current_version and are not using gnu libtool then ld will set the numbers to zero. They really only have significance to the dynamic linker which checks them at runtime. If a shared library client which has encoded the library it needs as libfoo.dylib compat 0 current 0 it will load libfoo.dylib with any value ot compat and current version. If it has libfoo.dylib compat 5 current 5, as far as I know it will not load a libfoo.dylib with any compatibility version less than 5 (including 0).
Peter -- Peter O'Gorman - http://www.pogma.com
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
