Stampede3 - clariried sudo warning

TACC · Feb 15, 2024 · 83f643d · 83f643d
1 parent 8acf375
commit 83f643d
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 4 deletions.
diff --git a/docs/hpc/3stampede/building.md b/docs/hpc/3stampede/building.md
@@ -98,7 +98,13 @@ $ mpicc -show  # Show compile line generated by call to mpicc; similarly for oth
 
 ### [Building Third-Party Software](#building-thirdparty) { #building-thirdparty }
 
-You are welcome to download third-party research software and install it in your own account. In most cases you'll want to download the source code and build the software so it's compatible with the Stampede3 software environment. **You cannot use the `sudo` command or any package manage or other installation process that requires elevated user privileges**, but this is almost never necessary. The key is to specify an installation directory for which you have write permissions. Details vary; you should consult the package's documentation and be prepared to experiment. Using the [three-step autotools](https://www.gnu.org/software/automake/manual/html_node/Autotools-Introduction.html) build process, the standard approach is to use the `PREFIX` environment variable to specify a non-default, user-owned installation directory at the time you execute `configure` or `make`:
+You are welcome to download third-party research software and install it in your own account. In most cases you'll want to download the source code and build the software so it's compatible with the Stampede3 software environment. 
+
+!!! Warning 
+	You cannot use the `sudo` command or any package manager or installation process that requires elevated or "root" user privileges.
+
+
+Instead, the key is to specify an installation directory for which you have write permissions. Details vary; you should consult the package's documentation and be prepared to experiment. Using the [three-step autotools](https://www.gnu.org/software/automake/manual/html_node/Autotools-Introduction.html) build process, the standard approach is to use the `PREFIX` environment variable to specify a non-default, user-owned installation directory at the time you execute `configure` or `make`:
 
 	$ export INSTALLDIR=$WORK/apps/t3pio
 	$ ./configure --prefix=$INSTALLDIR

diff --git a/docs/hpc/3stampede/notices.md b/docs/hpc/3stampede/notices.md
@@ -1,6 +1,6 @@
 # Stampede3 User Guide 
 
-*Last update: February 13, 2024*
+*Last update: February 15, 2024*
 
 ## [Notices](#notices) { #notices }
 

diff --git a/docs/hpc/stampede3.md b/docs/hpc/stampede3.md
@@ -1,6 +1,6 @@
 # Stampede3 User Guide 
 
-*Last update: February 13, 2024*
+*Last update: February 15, 2024*
 
 ## [Notices](#notices) { #notices }
 
@@ -539,7 +539,13 @@ $ mpicc -show  # Show compile line generated by call to mpicc; similarly for oth
 
 ### [Building Third-Party Software](#building-thirdparty) { #building-thirdparty }
 
-You are welcome to download third-party research software and install it in your own account. In most cases you'll want to download the source code and build the software so it's compatible with the Stampede3 software environment. **You cannot use the `sudo` command or any package manage or other installation process that requires elevated user privileges**, but this is almost never necessary. The key is to specify an installation directory for which you have write permissions. Details vary; you should consult the package's documentation and be prepared to experiment. Using the [three-step autotools](https://www.gnu.org/software/automake/manual/html_node/Autotools-Introduction.html) build process, the standard approach is to use the `PREFIX` environment variable to specify a non-default, user-owned installation directory at the time you execute `configure` or `make`:
+You are welcome to download third-party research software and install it in your own account. In most cases you'll want to download the source code and build the software so it's compatible with the Stampede3 software environment. 
+
+!!! Warning 
+	You cannot use the `sudo` command or any package manager or installation process that requires elevated or "root" user privileges.
+
+
+Instead, the key is to specify an installation directory for which you have write permissions. Details vary; you should consult the package's documentation and be prepared to experiment. Using the [three-step autotools](https://www.gnu.org/software/automake/manual/html_node/Autotools-Introduction.html) build process, the standard approach is to use the `PREFIX` environment variable to specify a non-default, user-owned installation directory at the time you execute `configure` or `make`:
 
 	$ export INSTALLDIR=$WORK/apps/t3pio
 	$ ./configure --prefix=$INSTALLDIR