Re: 2.9.4 on mac OSX tiger

[Marius Schamschula]

Dmitri,

I have the following (Note: otool -L on Darwin == ldd on Linux):

Atlas:~/Development/mports/hdf marius$ otool -L /usr/local/bin/octave
/usr/local/bin/octave:
        /usr/local/lib/libmpi.0.dylib (compatibility version 1.0.0,  
current version 1.0.0)
        /usr/local/lib/liblam.0.dylib (compatibility version 1.0.0,  
current version 1.0.0)
        /usr/local/lib/octave-2.1.72/liboctinterp.dylib  
(compatibility version 0.0.0, current version 0.0.0)
        /usr/local/lib/octave-2.1.72/liboctave.dylib (compatibility  
version 0.0.0, current version 0.0.0)
        /usr/local/lib/octave-2.1.72/libcruft.dylib (compatibility  
version 0.0.0, current version 0.0.0)
        /System/Library/Frameworks/vecLib.framework/Versions/A/ 
vecLib (compatibility version 1.0.0, current version 176.1.0)
        /usr/local/lib/libreadline.5.0.dylib (compatibility version  
5.0.0, current version 5.0.0)
        /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0,  
current version 5.4.0)
        /usr/local/lib/libhdf5.0.dylib (compatibility version 1.0.0,  
current version 1.0.0)
        /usr/local/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 88.1.2)
        /usr/local/lib/libg2c.0.dylib (compatibility version 1.0.0,  
current version 1.0.0)
        /usr/local/lib/libgcc_s.1.0.dylib (compatibility version  
1.0.0, current version 1.0.0)
        /usr/local/gcc-3.4/lib/gcc-3.4/libstdc++.6.dylib  
(compatibility version 7.0.0, current version 7.3.0)

So why would Apple change anything in this picture if they were to  
change /usr/lib/readline.dylib?
There is no fiddling with loadpaths.

On Jan 22, 2006, at 3:54 PM, Dmitri A. Sergatskov wrote:

> Marius Schamschula wrote:
>
> > I have a proper readline.5.dylib installed in /usr/local/lib, so  
> > why should I use readline.a?
>
> If you have multiple readline.dylib libraries installed, then linker
> will use the first in its search path. You may tweak the linker  
> search path to
> make sure that the correct library is the first one.
> That may work for you, but if you want to make an executable he  
> other people
> may want to use, it might be too imposing
> to force your users to fiddle with the linker loadpath.
> Also installing next OSX update could mess it up again.
> So linking a static library would produce an executable which would
> not need a dynamic readline library.
>
> Dmitri.
> --



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------