Thanks Dimitris,

> 
> 
> On Tue, Dec 6, 2016 at 8:46 PM Dimitris Chloupis <kilon.al...@gmail.com> 
> wrote:
> because you run a very old macos version it may be possible that because 
> Cairo lib has been compiled for more recent macos that this is the source of 
> your problems.
> 
> Try the following commands from inside the folder you installed pharo 
> following my previous instructions

The 
> otool -L ./pharo-vm/Pharo.app/Contents/MacOS/Plugins/libcairo.2.dylib

        Answer:

        ./pharo-vm/Pharo.app/Contents/MacOS/Plugins/libcairo.2.dylib:
        @executable_path/Plugins/libcairo.2.dylib (compatibility version 
11203.0.0, current version 11203.14.0)
        @executable_path/Plugins/libpixman-1.0.dylib (compatibility version 
27.0.0, current version 27.0.0)
        @executable_path/Plugins/libfreetype.6.dylib (compatibility version 
15.0.0, current version 15.1.0)
        @executable_path/Plugins/libpng12.0.dylib (compatibility version 
50.0.0, current version 50.0.0)
        /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 
1.2.5)
        
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
 (compatibility version 1.0.0, current version 48.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 1225.1.1)
        
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 
(compatibility version 150.0.0, current version 1253.0.0)
        
/System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 
(compatibility version 64.0.0, current version 600.0.0)


> 
> This command will print the dependencies of the library and whether your OS 
> libraries are enough to support this library. If one dependency fail then the 
> whole library may fail.
> 
> In that case you will need to locate a build for Cairo for the version of 
> MacOS you are using and replace the dylib file or build it yourself, 

Without load anything           the     VGTigerDemo runDemo             report 
into the error debug     and into relative terminal ( where a launch the pharo 
):

dtr$ ./pharo-ui Pharo.image
Error: External module not found
ExternalLibraryFunction(Object)>>error:
ExternalLibraryFunction(Object)>>externalCallFailed
ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments:
AthensCairoSurface class>>primImage:width:height:
FFICalloutAPI>>function:module:
AthensCairoSurface class(Object)>>nbCall:
AthensCairoSurface class>>primImage:width:height:
AthensCairoSurface class>>extent:format:
AthensCairoSurface class>>extent:
VGTigerDemo>>initialize
VGTigerDemo class(Behavior)>>new
VGTigerDemo class>>runDemo

> 
> As you may imagine its very difficult for us to continue supporting very old 
> OS , because we are a small community.  

I do not want to bother.

Just see if the issue is resolved on my system,

or whether to postpone everything when update the operating system.

But the gitFileTree support would be very useful to continue in a certain 
direction.

Cheers,

                Dario





Reply via email to