Re: foreign-library-directories (Was Re: [Matlisp-commit] [matlisp-git]matlisp branch master updated. 2012-02-23-12-gb4755e8)

On 03/11/2012 08:21 AM, Raymond Toy wrote:
> On 3/10/12 9:35 AM, Akshay Srinivasan wrote:
>> On 03/10/2012 10:54 PM, Raymond Toy wrote: Dang.  You're right.
>> I read the description of *f-l-d* backwards. I think your
>> solution is probably the right one, and we should add @libdir@ to
>> all the library paths.
>> 
>> I think the backward description makes more sense. Oh well. Added
>> @libdir@ to all the library paths.
>> 
> Unfortunately, this breaks matlisp for me on osx.  It tries to load
> the library but can't find all the dependent fortran libraries so
> it dies because of missing symbols.
That's odd. Are you using gfortran ? BLAS compiled with gfortran on my
machine looks like it has already been linked with the gfortran stuff.

I wonder if this has something do with *darwin-framework-directories*
in cffi. I'm not sure what it means though.

> 
> I think the only option we have is to undo this and set
> LD_LIBRARY_PATH to include libdir.  This will work if you use make.
> If you do something else, this won't.  We could add a script,
> matlisp, that sets up LD_LIBRARY_PATH correctly and runs the
> appropriate lisp.
I'm not happy with that because then it won't work, when loading
matlisp on slime, unless I remember to set the LD_LIBRARY_PATH before
actually opening Emacs. Can't we just set LD_LIBRARY_PATH through
(run-system ..) inside start.lisp ?

Akshay

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/