[CLAM] CLAM 0.7 Configuration on OS X.3

[Paul Kosek]

Thank you very much.  I ran the script exactly as you described and there 
is no longer a problem; I can double click the application and it opens.

Here are the log files, just as you predicted them to be.

Thank you very much for your help.

P.S.  When I was looking at console.log I noticed the output of 
printf(""); statements I had put into the program yesterday.  This will be 
great for debug!

--Paul

console.log:

dyld: 
/Code_resources/clam_builds/CLAM-0.7.0/build/Examples/SMSTools2-0.2/build/Tools/SMSTools.app/Contents/MacOS/SMSTools 
can't open library: /CLAM_EXTERNAL_LIBS/oggvorbis//lib/libogg.0.dylib  (No 
such file or directory, errno = 2)

SMSTools.crash.log:

**********

Host Name:      computer.local
Date/Time:      2005-01-14 09:29:39 -0500
OS Version:     10.3.7 (Build 7S215)
Report Version: 2

Command: SMSTools
Path:    
/Code_resources/clam_builds/CLAM-0.7.0/build/Examples/SMSTools2-0.2/build/Tools/SMSTools.app/Contents/MacOS/SMSTools
Version: ??? (???)
PID:     3085
Thread:  Unknown

Link (dyld) error:

dyld: 
/Code_resources/clam_builds/CLAM-0.7.0/build/Examples/SMSTools2-0.2/build/Tools/SMSTools.app/Contents/MacOS/SMSTools 
can't open library: /CLAM_EXTERNAL_LIBS/oggvorbis//lib/libogg.0.dylib  (No 
such file or directory, errno = 2)

----------

On Fri, 14 Jan 2005, Maarten de Boer wrote:

> 
> [OSX only]
> 
> I believe the problem is related with the dynamic-library bindings.
> After linking, all library binding (paths of the used libraries) in the
> resulting executable are "corrected" in the CLAM makefile, but if those
> libraries themself contain wrong path, running the executable by
> clicking the icon will fail.
> 
> You can correct  bindings among the different libraries in your sandbox
> using the "correct-all-dylibs.sh" script in CLAM/build/macosx-utils.
> 
> $ cd <your clam sandbox>
> $ ./CLAM-0.7.0/build/macosx-utils/correct-all-dylibs.sh */*/*.dylib
> 
> I wrote this script for this purpose, but it might not have been correctly documented. I will file a bugreport so this will be solved in the next 
> release.
> 
> Could you please confirm, Paul, if this solves your problem?
> 
> maarten
>