| ... | ... | @@ -55,7 +55,7 @@ You can now navigate to the SERGHEI root directory `cd serghei` |
|
|
|
Check the path to the current directory using the `pwd` command. This should return be the absolute path to the local working copy of the repository (i.e., the `serghei` directory). This should look something like
|
|
|
|
|
|
|
|
```
|
|
|
|
/p/project/training2226/username1/serghei
|
|
|
|
/p/project/your_project_name/your_username/serghei
|
|
|
|
```
|
|
|
|
|
|
|
|
# 3. Preparing the environment
|
| ... | ... | @@ -119,7 +119,7 @@ It is therefore practical to write a script that will make this easier. This of |
|
|
|
|
|
|
|
Since we are using JURECA-DC, we should use the script for that machine. To load the environment defined in this script run
|
|
|
|
|
|
|
|
`source jurecaDCModules`
|
|
|
|
`source jureca.cpu`
|
|
|
|
|
|
|
|
If all goes well, we now should have the environment ready. You can check which module are loaded with
|
|
|
|
|
| ... | ... | @@ -143,7 +143,7 @@ cd $SERGHEIPATH/src |
|
|
|
3. Now we will use `make` to compile and build. Running `make` attempts to read the `Makefile`, which you can see exists in this directory. If you try to run `make` in a different directory which does not contain a `Makefile` you will get an error. `make` support parallel threads, so that the compilation is faster. For example
|
|
|
|
|
|
|
|
```bash
|
|
|
|
make -j 8
|
|
|
|
make -f Makefile.serghei -j 8
|
|
|
|
```
|
|
|
|
|
|
|
|
would use 8 threads to run the compilation. Give this a try. If everything is correctly set, you should see a message indicating a successful build.
|
| ... | ... | |
| ... | ... | |