@@ -67,7 +67,9 @@ compiler. Alternatively the "Developer/quick-start instructions"
67
67
installation using CMake directly, without calling [ ` install.sh ` ] . The
68
68
compilers are specified using the ` FC ` , ` CC ` and ` CXX ` environment
69
69
variables, and all prerequisites (GFortran, CMake, and a suitable MPI
70
- implementation) are assumed to be already installed on the system.
70
+ implementation) are assumed to be already installed on the system. If
71
+ you pass one compiler-specification argument (e.g., ` -f ` ), it is best
72
+ to pass all three (e.g., ` -f ` , ` -c ` , and ` -C ` ) to ensure consistency.
71
73
72
74
## 4. How can I uninstall OpenCoarrays? ##
73
75
@@ -104,6 +106,18 @@ such as the `-s` flag to show the underlying command, or the `-np <N>`
104
106
flag to specify the number of images in the ` cafrun ` script and before
105
107
any files such as Fortran source files or Coarray Fortran executables.
106
108
109
+ ## 7. When ` install.sh ` builds the GCC compilers, it takes forever (hours). How can I speed up the build? ##
110
+
111
+ To increase the odds of success, ` install.sh ` defaults to a GCC
112
+ bootstrap build, which builds a minimal compiler to build the ultimate
113
+ compiler (not every version of GCC can build every other version of
114
+ GCC). For a much faster build process that has a somewhat higher
115
+ chance of failing, pass the ` --disable-bootstrap ` or ` -z ` argument and
116
+ use more threads by passing, for example, ` --num-threads -4 ` or ` -j 4 `
117
+ to use four threads. In combination, these two recommendations can
118
+ decrease the GCC build time from several hours to 15 or fewer minutes.
119
+
120
+
107
121
[ `install.sh` ] : https://github.com/sourceryinstitute/OpenCoarrays/blob/master/install.sh
108
122
[ `INSTALL' ] : https://github.com/sourceryinstitute/OpenCoarrays/blob/master/INSTALL
109
123
[ new issue ] : https://github.com/sourceryinstitute/OpenCoarrays/issues/new
0 commit comments