Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For software requests that have wide appeal to many groups and users, this software will typically be built in the public fileshare, e.g., /packages/apps and will be accompanied by a public environment modulefile which can be loaded with module load <package/version>.

...

Requesting software to be built

Requests for software installations can be made in a support ticket.

...

Software explicitly requiring Debian, Ubuntu, etc., may compile and we will make a best-effort attempt to help build the software. Beyond that, seek a container solution, as other Linux distributions rely on software managers and libraries likely incompatible with RedHat-compatible Rocky Linux.

Compiling software from source

Luckily, many of the compilation considerations mentioned above can be handled automatically, with provided build scripts and makefiles from the software author. At the minimum, an understanding of Linux filesystem permissions is required to build software, as most software defaults to installing files in locations not permissible by regular, non-admin users.

Filesystem Permissions & Shared Storage

A valid--albeit abbreviated--installation of python might go like this:

...

This error is not an indication of a failed build, but simple a failure to copy the binaries to root-owned paths on a node. Many users may recognize this as a sudo-solvable problem, but in HPC environments, that is not the case.

sudo access

Sudo access is reserved explicitly for Research Computing admins. If a software installation attempts to install to a local directory and fails, the answer is not to request more permission to be able to install to a local directory. Instead redirect the installation to a shared storage space, like your HOME directory or group shared storage.

Info

If you did have sudo access, you would be able to install software to the default location /usr/local/…. However, when you disconnect and reconnect to the supercomputer, you can not reasonably expect to be on the exact same node, which means your build is inaccessible to your job. /home/[asurite]/ on the other hand is available on every node.

Changing build directories

The above installation could therefore be adjusted in a very simple way to install to your HOME directory:

Code Block
...
$ ./configure --prefix=/home/[asurite]/.local/opt/python-3.9.7 
$ make
$ make install

Container solutions

/wiki/spaces/RC/pages/54099969 is available on the RC supercomputers. Many times, software is distributed in an easy-to-download package (.sif file) which can be uploaded to your HOME directory and used immediately.

...

Please check this dedicated page for more information Apptainer usage .

Additional Help

If you require further assistance on this topic, please don't hesitate to contact the Research Computing Team. To create a support ticket, kindly send an email to rtshelp@asu.edu. For quick inquiries, you're welcome to reach out via our #rc-support Slack Channel or attend our office hours for live assistance

We also offer a series of workshops. More information here: Educational Opportunities and Workshops