necessary info

John B Brown jbb at
Thu Apr 29 08:55:20 PDT 2010

Dear Folk,

	My version of findutils searches from /. Here is the locate result for 
libTIFF and libtiff. Might there be a problem with what is here?

jbb at pinball3:~
(6): % locate libTIFF

jbb at pinball3:~
(7): % locate libtiff

jbb at pinball3:~
(8): %

	'nm -a' is not providing a version number for the /System libTIFF. Its 
long since I've used nm but I faintly recall a top header line that 
listed version and compile information which I don't see here.

	'what' gives me nothing and 'whatis', "nothing appropriate."

	God, I hate debugging system problems.


	John B. Brown.
	[jbb at]
	358 High Street,
	Buffalo, Wyoming

"Freedom is not worth having if it does not include
the freedom to make mistakes"  Mahatma Gandhi
"If any question why we died, tell them,
because our fathers lied."  Rudyard Kipling
"A man who does not know the truth is just an idiot
but a man who knows the truth and calls it a lie
is a crook."  Bertolt Brecht
"I wonder whether the world is being run
by smart people who are putting us on
or by imbeciles who really mean it."  Mark Twain

On 4/29/10 8:29 AM, Daniel J. Luke wrote:
> On Apr 28, 2010, at 7:07 PM, John B Brown wrote:
>>> Dyld Error Message:
>>>   Library not loaded: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
>>>   Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
>>>   Reason: Incompatible library version: ImageIO requires version 1.0.0 or later, but libTIFF.dylib provides version 0.0.0
> On Apr 29, 2010, at 2:19 AM, John B Brown wrote:
>> jbb at pinball3:~
>> (1): % otool -L /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
>> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib:
>> 	/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib (compatibility version 1.0.0, current version 1.0.0)
>> 	/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib (compatibility version 1.0.0, current version 1.0.0)
>> 	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
>> 	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.0.1)
> Clearly, your crashing apps want libTIFF.dylib version 1.0.0 which they have a full path to (inside of ImageIO). For whatever reason, dyld lis loading some other libTIFF.dylib which has version 0.0.0
> As has been said before, you probably have a DYLD_* environment variable set that is causing your problem.
> I know you haven't found the problem libTIFF.dylib, but obviously the dynamic linker is finding one that is _not_ the one in ImageIO.
> --
> Daniel J. Luke
> +========================================================+
> | *---------------- dluke at ----------------* |
> | *-------------- -------------* |
> +========================================================+
> |   Opinions expressed are mine and do not necessarily   |
> |          reflect the opinions of my employer.          |
> +========================================================+

More information about the macports-users mailing list