Problem with matlab compiler after upgrading to R2017b. matlabshar​ed.support​pkg.intern​al.getSupp​ortPackage​RootNoCrea​te

Hello, I recently upgraded R2016b to R2017b on my Linux machine. However, when I try to use the matlab compiler from the "apps" tab on the home screen, the compiler fails, with this message in the log file:

mcc -o FODforPRT2 -W main:FODforPRT2 -T link:exe -d /home/neilley/opt/matlab/src/misc/FODforPRT2/for_testing -v /home/neilley/opt/matlab/src/misc/FODforPRT2.m 
  Compiler version: 6.5 (R2017b)

    Dependency analysis by REQUIREMENTS.

    {Undefined function or variable
    'matlabshared.supportpkg.internal.getSupportPackageRootNoCreate'.} 
    Unable to locate support package root__

However, if I run the "mcc" command from that log file from a linux shell, the compiler runs to completion without error and produces an executable file, but that executable file won't run because it can't find some of the dependent functions that it needs that are elsewhere in my matlab source code path (that is, the compiler failed to include these dependent functions during compiling).

Any idea what's going on here?

Answer 1

[Manan Mishra]

The error which you are receiving could be due an incorrect MATLABPATH setting, which is likely the result of working with a pathdef.m which was created in an older MATLAB release.The default paths of MATLAB may not be configured properly on your workstation.

To resolve this issue use "restoredefaultpath" to make sure all directories which MATLAB R2017b requires are on the path and then save this new path as the default using "savepath".

In order to reset MATLAB path, please execute the following commands in your MATLAB command window:

>> restoredefaultpath
>> savepath

Please note that executing the above commands would delete all the previous path information and replace it with the factory settings. Hence, you might want to back up the old 'pathdef.m' file so that you can use other path information from it at a later period.

Please refer the following link for details about this:

How will running the restoredefaultpath and savepath commands affect my custom paths and how do I back up my custom paths?