-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C_INCLUDE_PATH not set #4
Comments
Looks like just setting CPATH is equivalent to these variables (and cuts in half the environment polution). |
In many cases that is true, but I have found cases where either only C_INCLUDE_PATH works or only CPATH works. There is a similar issue with LD_LIBRARY_PATH versus LIBRARY_PATH. I haven't tracked down the history of this split. I'm sorry I can't give specific examples. |
ok, good to know your experiences. CPATH seems to work for the gcc versions I have tried so far. I'll try to finish up some remaining tests today and then install a full test on carver. -Ted On Dec 10, 2012, at 7:41 PM, esheldon wrote:
|
Conversion to CPATH and LIBRARY_PATH now complete. CPATH works fine in all packages, including having the fortran compiler find module files. Still have to re-install at NERSC (shortly). |
Looks like I spoke too soon. gfortran does not use CPATH, but does accept "-I " include directives. There is some discussion on the gcc forums. Re-opening until I have a resolution for this. |
For all compilers we care about (GCC, Intel, IBM), we can use C_INCLUDE_PATH and CPLUS_INCLUDE_PATH to specify directories to search for headers. Add this to modulefiles and package shell snippets. Need to find equivalent variables for fortran module search.
The text was updated successfully, but these errors were encountered: