PENG WANG <peng.wang@...> writes:

> 
> Hello, Dear MEEP developers and users:
> 
>     I am a new user of MEEP software. I currently installed MEEP in Ubuntu,
which is suggested by Professor Steve
> as the best way to install MEEP.
> 
>     But when I call meep from Matlab by:
> 
>             unix('meep test.ctl >& test.out')
> 
>     The output file gives me an error below:
> 
>             meep: /usr/local/MATLAB/R2011a/sys/os/glnxa64/libgfortran.so.3:
version `GFORTRAN_1.4' not
> found (required by /usr/lib/liblapack.so.3gf)
> 
>     Could you please help me solve this problem? Expecting your kind
considerations and answers!
> 
> Thanks very much!
> Best Regards,
> 
> Peng Wang
> 11/10/2011
> 
> _______________________________________________
> meep-discuss mailing list
> meep-discuss@...
> http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
> 
> End of meep-discuss Digest, Vol 69, Issue 7
> *******************************************
> 



I know the original poster has probably solved the problem or moved on, but I
wanted to write this as a potentially helpful reference for others.

I ran into a very similar problem under different circumstances. I am calling
code written in Python/Numpy by shelling out with MATLAB's ``system`` command.
The solution that I found is described here:

http://www.mathworks.ca/matlabcentral/newsreader/view_thread/162466

To summarize, MATLAB tries to force code called from within it to use libraries
it provides. Unfortunately, these are often fairly old, and can be incompatible
with precompiled external code. Some people seem to be removing the packaged
libraries and linking them to the correct versions elsewhere, but a less
invasive approach is to modify the file

.matlab7rc.sh (in MATLAB's bin/ directory)

so that ``LDPATH_PREFIX`` points to the right directory. This is described by
user "luquesky luque," and worked for me. In my case (64-bit Linux), I changed

LDPATH_PREFIX=''

to

LDPATH_PREFIX='/usr/lib/x86_64-linux-gnu'

and saved the modified shell script to my home directory. Apparently, you can
also just save it to the project directory you're working from to avoid
user-wide changes. I think the path may not be the same for different
distributions, but you could try

find / 2>/dev/null | grep libgfortran.so.3

to verify.

Nat





_______________________________________________
meep-discuss mailing list
[email protected]
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss

Reply via email to