MATLAB Answers

Running mex files compiled on Linux

54 views (last 30 days)
Bogdan Cristea Eugen
Bogdan Cristea Eugen on 30 Aug 2012
Commented: An Tran Lam on 2 Jun 2014
When I am running from MATLAB a mex file compiled from a cpp source file I get the following error:
Invalid MEX-file '/home/bogdan/C++/IT++/mex/test.mexa64': /usr/local/MATLAB/R2012a/bin/glnxa64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /usr/local/lib64/libitpp.so.8)
The solution seems to create soft links in MATLAB library folder to newer version of these libraries as provided by a particular Linux distribution (in my case openSUSE 12.1 x86_64).
My question is if this is the standard solution recommended by Mathworks? Are there any issues with this approach (should all libraries be updated to newer versions, since incompatibility issues might arise)?

  1 Comment

An Tran Lam
An Tran Lam on 2 Jun 2014
I have same questions as you. Even I set LD_LIBRARY_PATH, it does no solve the problem. Does anyone know why LD_LIBRARY_PATH won't have the effect on Matlab.

Sign in to comment.

Answers (2)

Ken Atwell
Ken Atwell on 30 Aug 2012
Before soft-linking from the MATLAB folder, I would first try unsetting LD_LIBRARY_PATH within MATLAB
>> setenv('LD_LIBRARY_PATH', '')
There is, at least in theory, a possibility that MATLAB will crash because there will be two C++ libraries in memory, but it is worth a shot. Let us know how you make out.

  0 Comments

Sign in to comment.


Bogdan Cristea Eugen
Bogdan Cristea Eugen on 30 Aug 2012
Well, I am not sure what you mean by soft-linking. I have tried to run my mex file before and after I have used
setenv('LD_LIBRARY_PATH', '')
but I get the same error
Invalid MEX-file '/home/bogdan/C++/IT++/mex/test.mexa64': /usr/local/MATLAB/R2012a/bin/glnxa64/libstdc++.so.6:
version `GLIBCXX_3.4.15' not found (required by /usr/local/lib64/libitpp.so.8)
Even if, after running setenv(), I see that LD_LIBRARY_PATH is empty, it seems that MATLAB stores in some kind of cache the library path.

  4 Comments

Show 1 older comment
Bogdan Cristea Eugen
Bogdan Cristea Eugen on 31 Aug 2012
I am aware about this solution, but I would like to know what is the Mathworks' recommended way to cope with this problem when using MATLAB.
Friedrich
Friedrich on 31 Aug 2012
Since its a general System problem which happens with any compiled application (so not only mex files, also plain C files compiled outside of MATLAB) I doubt there is a MathWork specific solution. Its a general GCC Bug on Linux.
An Tran Lam
An Tran Lam on 2 Jun 2014
Even I set LD_LIBRARY_PATH, it does no solve the problem. Does anyone know why LD_LIBRARY_PATH won't have the effect on Matlab. Strange phenomenon is that why Matlab uses /usr/local/MATLAB/R2012a/bin/glnxa64/libstdc++.so.6 first. While in LD_LIBRARY_PATH it should be in the second. LD_LIBRARY_PATH=/usr/local/MATLAB/R2012a/sys/os/glnxa64:/usr/local/MATLAB/R2012a/bin/glnxa64

Sign in to comment.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!