On certain occasions, when upgrading to a new MacOSX system, you can find yourself stuck
at the link phase of the matlab wrappers, with unresolved symbols from the libmx.dylib library,
such as _mxAlloc, __mxErrorMsgTxt, etc ...
This occurs because sometimes the MacOSX system bypasses your Matlab path, and goes to /usr/lib/libmx.dylib
to resolve the mx dependency.
Solutions:
- move the /usr/lib/libmx libraries somewhere Matlab can't find them (back them up first). Reconfigure and recompile your system.
- if this does not work, in the m4/issm_options.m4, hardcode the path to the libmx.lib library (found in your externalpackages/matlab/install/lib) under MEXLIB, instead of a relative reference "-lmx". Reconfigure and recompile.
