User`s guide

Troubleshooting
4-33
Troubleshooting
Troubleshooting mbuild
This section identifies some of the more common problems that might occur
when configuring
mbuild to create stand-alone applications.
Options File Not Writeable. When you run mbuild -setup, mbuild makes a copy of
the appropriate options file and writes some information to it. If the options file
is not writeable, you are asked if you want to overwrite the existing options file.
If you choose to do so, the existing options file is copied to a new location and a
new options file is created.
Out of Environment Space Running mex or mbuild. On Windows 98 systems, the mex
and
mbuild scripts require more than the default amount of environment
space. If you get the error,
out of environment space, add this line to your
config.sys file:
shell=c:\command.com /e:32768 /p
On Windows Me systems, if you encounter this problem and are using the
MATLAB add-in for Visual Studio, follow the procedure in “Configuring on
Windows 98 and Windows Me Systems” on page 4-25.
Directory or File Not Writeable. If a destination directory or file is not writeable,
ensure that the permissions are properly set. In certain cases, make sure that
the file is not in use.
mbuild Generates Errors. On UNIX, if you run mbuild filename and get errors, it
may be because you are not using the proper options file. Run
mbuild -setup
to ensure proper compiler and linker settings.
Compiler and/or Linker Not Found. On PCs running Windows, if you get errors
such as
unrecognized command or file not found, make sure the command
line tools are installed and the path and other environment variables are set
correctly in the options file.
mbuild Not a Recognized Command. If mbuild is not recognized, verify that
<MATLAB>\bin is on your path. On UNIX, it may be necessary to rehash.