-
Notifications
You must be signed in to change notification settings - Fork 0
/
aclocal.m4
108 lines (100 loc) · 4.51 KB
/
aclocal.m4
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
# SYNOPSIS
#
# Summarizes configuration settings.
#
# AX_SUMMARIZE_CONFIG([, ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND]]])
#
# DESCRIPTION
#
# Outputs a summary of relevant configuration settings.
#
AC_DEFUN([AX_SUMMARIZE_CONFIG],
[
echo
echo '----------------------------------- SUMMARY ----------------------------------'
echo
echo "Package version............................." : Lmod-$LmodV
echo "Package version (git) ......................" : $lmodV
echo
echo "LUA_INCLUDE................................." : $LUA_INCLUDE
echo "Lua executable.............................." : $luaprog
echo "Luac executable............................." : $PATH_TO_LUAC
echo "Prefix......................................" : $prefix
echo "Actual Install dir.........................." : $prefix/lmod/$LmodV
echo
echo "MODULEPATH_ROOT............................." : $MODULEPATH_ROOT
echo "Wait (s) before rebuilting cache............" : $ANCIENT
echo "Allow Duplicate Paths......................." : $DUPLICATE_PATHS
echo "Do not save Cache if build time < .........." : $SHORT_TIME
echo "SPIDER_CACHE_DIRS..........................." : $SPIDER_CACHE_DIRS
echo "Prepending multiple dirs (NORMAL / REVERSED)" : $PREPEND_BLOCK
echo "Colorized output supported.................." : $COLORIZE
echo "File that is touched when system is updated." : $UPDATE_SYSTEM_FN
echo "Allow duplicate entry in PATHs.............." : $DUPLICATE_PATHS
echo "Allow tcl modulefiles......................." : $ALLOW_TCL_MFILES
echo "ZSH Tab Completion Functions Site Directory." : $ZSH_SITE_FUNCTIONS_DIRS
echo "Use Dot files in ~/.lmod.d.................." : $USE_DOT_FILES
echo "Full Settarg support........................" : $SETTARG
echo "Have lua-term..............................." : $HAVE_LUA_TERM
echo "Have lua-json..............................." : $HAVE_LUA_JSON
echo "Support Auto Swap when using families......." : $AUTO_SWAP
echo "Export the module shell function in Bash...." : $EXPORT_MODULE
echo "Disable same name autoswapping.............." : $DISABLE_NAME_AUTOSWAP
echo "Legacy version ordering....................." : $LEGACY_ORDERING
echo "Use Spider Cache on Loads..................." : $CACHED_LOADS
echo "Pager used inside Lmod......................" : $PATH_TO_PAGER
echo "Hashsum program used........................" : $PATH_TO_HASHSUM
echo
echo '------------------------------------------------------------------------------'
echo
echo '******************************************************************************'
echo
echo Lmod overwrites the env var BASH_ENV to make the module command available in
echo bash scripts. If your site does not set BASH_ENV then you can ignore the
echo comments below.
echo
echo If your site already uses BASH_ENV to point to a site specific script, please
echo consider sourcing Lmod\'s init/bash from your site\'s file.
echo
echo BASH_ENV is defined both in:
echo " $prefix/lmod/$LmodV/init/profile"
echo " $prefix/lmod/$LmodV/init/cshrc"
echo
echo '******************************************************************************'
echo
a=$(echo $EXPORT_MODULE | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz)
if test "$a" != no; then
echo
echo '******************************************************************************'
echo
echo Lmod is exporting the module command for Bash users. Some sites may have some
echo problems. First:
echo
echo " 0. Make sure that all your machines have shellshock bash patch."
echo
echo If that does not fix things then you have two choices:
echo
echo " 1. You configure Lmod not to export the module command."
echo " 2. You can filter out the exported functions in the users environment"
echo " during job submission"
echo
echo If there is a way to do step 2, please try to do so. Otherwise do step 1.
echo The advantage of exporting the module command is that it is defined in
echo /bin/sh scripts. Because Lmod defines BASH_ENV to point to init/bash,
echo "it will be defined for /bin/bash scripts. The trouble is that users"
echo "have to remember to put #!/bin/bash at the first line of their shell"
echo script to make that work. We used to see tickets where users would
echo submit jobs as /bin/sh scripts and wonder why the module command did
echo not work.
echo
echo '******************************************************************************'
echo
fi
echo
echo Configure complete, Now do:
echo
echo " $ make install # -> A complete install"
echo or
echo " $ make pre-install # -> Install everything but the symbolic link"
echo
])