User`s guide

4 Stand-Alone Applications
4-34
mbuild Works from Shell but Not from MATLAB (UNIX). If the command
mbuild ex1.c
works from the UNIX command prompt but does not work from the MATLAB
prompt, you may have a problem with your
.cshrc file. When MATLAB
launches a new C shell to perform compilations, it executes the
.cshrc script.
If this script causes unexpected changes to the
PATH environment variable, an
error may occur. You can test this by performing a
set SHELL=/bin/sh
prior to launching MATLAB. If this works correctly, then you should check
your
.cshrc file for problems setting the PATH environment variable.
Cannot Locate Your Compiler (PC). If mbuild has difficulty locating your installed
compilers, it is useful to know how it goes about finding compilers.
mbuild
automatically detects your installed compilers by first searching for locations
specified in the following environment variables:
•
BORLAND for Borland C/C++, Version 5.3
•
MSVCDIR for Microsoft Visual C/C++, Version 5.0, 6.0, or 7.0
Next,
mbuild searches the Windows registry for compiler entries.
Internal Error When Using mbuild -setup (PC). Some antivirus software packages
such as Cheyenne AntiVirus and Dr. Solomon may conflict with the
mbuild -setup process. If you get an error message during mbuild -setup of
the following form
mex.bat: internal error in sub get_compiler_info(): don't
recognize <string>
then you need to disable your antivirus software temporarily and rerun
mbuild -setup. After you have successfully run the setup option, you can
reenable your antivirus software.
Verification of mbuild Fails. If none of the previous solutions addresses your
difficulty with
mbuild, contact Technical Support at The MathWorks at
[e-mail].