Difference between revisions of "Troubleshooting GridPACK Builds"
(Created page with "<span style="color:red">'''This page is under construction'''</span> This page is a collection of trouble shooting tips that have proven useful in the past. If you run into p...") |
(No difference)
|
Revision as of 21:14, 27 June 2018
This page is under construction
This page is a collection of trouble shooting tips that have proven useful in the past. If you run into problems building GridPACK or its associated libraries, you may find some useful suggestions here. If you continue to have problems, feel free to contact us.
PETSc
Configuration Error Messages: The error messages that PETSc provides during configuration are frequently informative and can provide important information on why configuration failed, as well as pointing to potential solutions. Check these first.
configure.log: The configure.log file in the PETSc build directory can provide additional information on diagnosing build problems. You can identify which test failed and possibly get information on compiler errors from this file.
Noexec flag on /tmp: This error (which is currently rare) occurs if /tmp has been mounted on your system with the noexec flag set. This flag will prevent you from executing anything in /tmp, even if the executable bit has been set on the file. PETSc uses this directory to create temporary files as part of its configuration process. For PETSc versions later than 3.6, you should be able to get around this problem by setting the TMPDIR environment to some directory where you have both write and execute permissions. This problem is difficult to diagnose and your best bet may be to just try setting TMPDIR and see if your configuration problems go away. The PETSc development team is aware of this problem and may provide a fix in a later release (post 3.9.2).
