"source" not available in all systems #4260
Assignees
Labels
Comments
|
Grepping the CCS for "source" is fun but I don't think there's anywhere else this is used. |
|
@rljacob I'll make this update and double check it's not needed anywhere else. |
|
I think I saw @sarich push a branch with some fixes. |
|
Nevermind, that was part of some other development. Go ahead @jasonb5 |
Merged
jedwards4b
added a commit
that referenced
this issue
Jun 30, 2022
Fixes source command Changes source command from source to . for sh shell, leaves source for csh. Test suite: scripts_regression_tests.py Test baseline: n/a Test namelist changes: n/a Test status: n/a Fixes #4260 User interface changes?: N Update gh-pages html (Y/N)?: N
billsacks
added a commit
to ESCOMP/CTSM
that referenced
this issue
Jul 18, 2022
This PR includes a number of minor fixes and updates associated with FATES. A duplicate filter for all soils that was introduced during the the initial implementation of FATES-SP mode is removed. A small set of FATES history variable names have been updated necessitating an update to the testmod user namelists. The ccs_config and cime externals have been updated to include the FATES development workstation, lobata. The cime tag update is necessary to include a fix enabling support for module initilization on certain linux distributions (ESMCI/cime#4260). Finally, a minor fix was included to the initialization of the fates_levcdam dimension that was introduced with the last fates api update. Fixes #1794 Fixes #1488
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
env_mach_specific.py has this line:
source_cmd = "source {} && ".format(init_path)Turns out "source" is not available in Ubuntu. Most systems link "/bin/sh" to bash but Ubuntu links it to "dash" which is faster and does not define the "source" command.
Solution is to use "." which is POSIX-standard command for executing commands from a file.
source_cmd = ". {} && ".format(init_path)Thanks to @dqwu who found this and the solution.
The text was updated successfully, but these errors were encountered: