On 28-04-2009, at 07:22, Allin Cottrell wrote:
 I've put up a new gretltest.dmg which I think should fix that
 issue.
 
I have tested this on Mac OS X 10.5.6 and it worked for me.
Berend
BTW:
How did you get the @executable_path into gretcli?
Very interesting because if you can do the same with libgretl and the  
gretl gui, then you probably won't have to set and use the  
DYLD_LIBRARY_PATH variable any longer.
I did an otool -L on your gretlcli and got this
gretlcli:
         /Users/allin/newdist/Gretl.app/Contents/Resources/lib/ 
libgretl-1.0.0.dylib (compatibility version 1.0.0, current version  
1.50.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,  
current version 88.3.11)
         /usr/lib/libxml2.2.dylib (compatibility version 9.0.0,  
current version 9.16.0)
         /usr/lib/libz.1.dylib (compatibility version 1.0.0, current  
version 1.2.3)
         /Library/Frameworks/GTK+.framework/Versions/2.14.X11/ 
Resources/lib/libglib-2.0.0.dylib (compatibility version 1801.0.0,  
current version 1801.1.0)
         /Library/Frameworks/GTK+.framework/Versions/2.14.X11/ 
Resources/lib/libintl.8.dylib (compatibility version 9.0.0, current  
version 9.2.0)
         /usr/lib/libiconv.2.dylib (compatibility version 5.0.0,  
current version 5.0.0)
         @executable_path/../lib/libgmp.3.dylib (compatibility version  
7.0.0, current version 7.3.0)
         @executable_path/../lib/libreadline.5.2.dylib (compatibility  
version 5.0.0, current version 5.2.0)
         /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0,  
current version 5.4.0)