Most of these problems stem from bad association of Matlab’s C++ (or Fortran) libraries. The solution is often to create a soft-link and point to the corresponding system libraries. This blog article provides a very nice summary of this!
Or: the painful journey to shift into 64-bit era!
Matlab 2009a made radical changes such that all mex functions calling BLAS and LAPACK libraries assume 64-bit integers (instead of 32-bit) on 64-bit system. This means lots of mex functions before this need to be upgraded to run properly, otherwise checked with segmentation failure. It so happened I encountered this today, and cried with my workstation several hours, and turned down by the fact the fixes provided by Matlab seem not working.
External links:
Matlab: Mex-files calling BLAS and LAPACK functions must be updated on 64-bit platforms
Installing, running matlab and compiling Matlab extensions in a 64 bit Ubuntu system
Finally, I shall go to IDMI to fetch my 32-bit laptop … I fully understand why they called it bleeding-edge.
Vision and around 