From GridLAB-D Wiki
Linux Systems
- When installing GridLAB-D on a Linux system
./configure
reportsrm: core: is a directory
- This is normal. Ignore it. In retrospect the choice of core for the name of the GridLAB-D's core module was a poor one.
- When installing GridLAB-D on a Linux system
./configure
reportserror: Missing xerces-c headers
- Xerces is not property installed and is required for the build and install to complete. Either install Xerces from the Web or install the copy in the third_party folder in the source distribution. Be aware that prior to Hassayampa (Version 3.0) you should use Xerces 2.8 and for Hassayampa (Version 3.0) and later use Xerces 3.1.
- When installing GridLAB-D on a Linux system
./configure
reportschecking for cppunit/config-auto.h... no
- This is not a fatal build problem, but will result in self-test code being disabled. You can install cppunit from the Web or from the third_party folder in the source distribution. Note: as of Hassayampa (Version 3.0) cppunit is deprecated.
Mac OS X
- When building GridLAB-D on a Mac
autoreconf -isf
reports' already registered with AC_CONFIG_FILES
- A solution to this problem has not yet been identified. If you find one, please contact the GridLAB-D team.
- On some system, an error message like undefined reference to rpl_malloc is displayed when make is run.
- To solve this problem try
host% export ac_cv_func_malloc_0_nonnull=yes
- and rerun the autoreconf -isf command. If this happens with realloc or other functions, you can do the same for them also.
MATLAB Problems
- When building modules that use Matlab, autoconf fails to find Matlab even though it is installed.
- Make sure that the matlab -e command works. If it doesn't, add the Matlab bin folder to the PATH environment variable.
- When running models that use Matlab, libeng.dylib is not found
dyld: Library not loaded: @loader_path/libeng.dylib Referenced from: /usr/lib/gridlabd/gridlabd.bin Reason: image not found /usr/bin/gridlabd: line 22: 18284 Trace/BPT trap "$GRIDLABD/gridlabd.bin" "$@"
- The dynamic library path does not include Matlab's libraries. Add the following to your system's /etc/bashrc file
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:matlab-library-path
- On Macs, use
export DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:/Applications/MATLAB_version.app/bin/maci64
- When running models that use Matlab, the command matlab is not found.
- There is a problem with the control of PATH environment variable in Matlab. This can be solved by using the command option in the matlab link control file. Set the command to a local script that calls matlab directly, e.g.,
- Matlab link control file:
command ./runmatlab
- runmatlab script:
#!/bin/bash export PATH=/usr/bin:/bin:/Applications/MATLAB_R2011a.app/bin matlab
MySQL Problems
- When building modules that use MySQL, autoconf fails to find MySQL even though it is installed.
- Make sure that the MySQL Connector C libraries are installed in /usr/local/mysql-connector-c. If they are installed in another folder, make a link to that folder from the correct path, e.g.,
- host% ln -s /usr/local/mysql-connector-c-6.0.2-osx10.5-x86_64bit /usr/local/mysql-connector-ctt>
- When running models that use MySQL, libmysql.dylib is not found
dyld: Library not loaded: libmysql.16.dylib Referenced from: /usr/lib/gridlabd/gridlabd.bin Reason: image not found /usr/bin/gridlabd: line 22: 25468 Trace/BPT trap "$GRIDLABD/gridlabd.bin" "$@"
- The dynamic library path does not include MySQL's Connector-C libraries. Add the following to your system's /etc/bashrc file
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:mysql-connector-c-library-path
- On Macs, use
export DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:/usr/local/mysql-connector-c/lib