The Open Source content has been ported specifically for the NonStop platform from Open Source packages. The use of packages from this part of the ITUGLIB Technical Library is subject to the terms of the license for the particular package that was downloaded. Please read appropriate documentation in the downloaded package.

These packages were ported by Hewlett-Packard Enterprises and Connect Worldwide members, and are provided strictly on an 'As-Is' basis.

Installation instructions can be found at the bottom of this page.

Return to ITUGLIB Main menu

Error occurred on last download:

	Package	Description	Readme
	a2ps	GNU a2ps - 'Anything to PostScript' converter and pretty-printer
	aa3d	ASCII art stereogram generator
	aalib	An ASCII art gfx library
	ACE	Framework for concurrent communication software
	aim7	AIM Multiuser Benchmark - Suite VII
	aim9	AIM Independent Resource Benchmark - Suite IX
	amanda	Advanced Maryland Automatic Network Disk Archiver
	apache	Versatile, high-performance HTTP server
	apache-ant	A Java-based build tool
	apr	Apache Portable Runtime software libraries
	apr-util	Apache Portable Runtime Utility software libraries
	asciidoc	Text based document generation
	atk	The ATK accessibility library
	audiofile	Open-source version of SGI's audiofile library
	autoconf	Automatic configure script builder
	automake	Generates Makefile.in files
	aview	An image browser and animation player which renders its output as ASCII-art
	axis	An implementation of a SOAP server and client
	axl	An XML development toolkit
	barcode	Creates barcodes in .ps format

Hash Signature of Archive Download

Package:
Version:
Type:
File:
:
After download, verify the signature by running sha256sum <File> from coreutils

THIS SOFTWARE IS PROVIDED "AS-IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT SHALL HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP OR ITS SUBSIDIARIES OR AFFILIATES BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM OUT OF OR IN CONNECTION WITH THE SOFTWARE INCURRED BY YOU OR ANY THIRD PARTY.

Be aware that the import and export of and use of strong cryptographic software, use of cryptography hooks, or any form of communicating technical details and descriptions about cryptographic software, including designs and use cases is illegal in some parts of the world. When you download packages from ITUGLIB to your country, install it in your environment, make technical suggestions about the cryptographic portions of the software, redistribute the packages, or suggest software patches to the originating authors of these packages, or anyone else, you are strongly advised to ensure that you comply with any and all laws or regulations which may apply to you. The ITUGLIB Technical Committee and its members, Connect Worldwide, Hewlett Packard Enterprise, or anyone else associated with the management, production, and publication of these packages are not liable for any violations that you might inadvertently or deliberately make. It is entirely your responsibility to ensure compliance with all laws and regulations and you acknowledge this by using this website and its contents.

HPE has created a package called 'FLOSS' (Freeware Look for Open System Services) which is required if you want to build many of these packages.

Click the right arrow (>) in the left column to view all versions of a package.

If you have a NonStop Integrity X system or a Virtual NonStop running L-series NonStop OS, the binaries download is contained in the file with the 'TNS/X' link in the Type column.
If you have a NonStop Integrity I system running H- or J-series NonStop OS, the binaries download is contained in the file with the 'TNS/E' link in the Type column.
If you have a Himalaya running G-series NonStop OS, the binaries download is contained in the file with the 'TNS/R' link in the Type column.

Click on the short 'Hash' value link to see the full hash information for the archive.

First, either install HPE's coreutils (recommended), or install the packages "tar" and "gzip" from ITUGLIB. These are used to create all other packages, so it's best if you use them when installing. You can then install the ITUGLIB packages by using the following command:

cd /; /bin/zcat 'compressed_package_file' | /bin/tar -xf -

Once you have installed the "gzip" and "tar" packages, you can use this command to install a package:

export PATH=$PATH:/usr/coreutils/bin:/usr/local/bin

tar -C/ -xzf 'zipped_package_file'

After download, verify the signature by running sha256sum <File> from coreutils

The package sources will be installed in your home directory or under "/usr/local/Floss/" unless package documentation states differently. Similarly, the package executables, libraries, includes files, etc. will typically be installed under "/usr/local/" unless the package uses OpenSSL 1.1, in which case they should install into "/usr/local-ssl1.1". Any existing files with conflicting names may be overwritten. You can view the contents of a zipped package by using the following command:

tar -tzvf 'zipped_package_file'

It is a good idea to check the package first as some packages must be installed from the root (/) while others can be installed in /usr/local or other directories of your choosing. Consult the package notes for more information.

Note that most packages are pre-built and ready for use, just make sure to grab the packages that match your system type. Should you wish to recompile yourself, the package "floss" might be of great help. It sure has helped in providing everything you find on this page.

Some packages depend on OpenSSL, so you will need to set up the _RLD_LIB_PATH variable to point to your OpenSSL installation. Ensure that you download the correct package for the OpenSSL version you are running, for example:

export _RLD_LIB_PATH=$_RLD_LIB_PATH:/usr/local-ssl1.1/lib

Most packages have the source split off into a "src" archive, some come with a "diff" output (created by package "diffutils"), suitable for the "patch" program to apply all the changes needed to a vanilla source tree to get it compiled and working on NonStop.
If a package doesn't have a 'src' archive, it's very likely that the source from the package owner can be used as is. You can go to the website on the 'Package' line and check any appropriate README files.

Some packages are marked '(OSS)', which means that they've been built using as little of Floss as possible (e.g. linked against "T1248 Pthreads" instead of "GNU Pth", if applicable).

Some packages include "nroff"-formatted man pages. The OSS "man" command is able to display these man pages if the "groff" package is installed and a symbolic link is created from "/bin/nroff" to "/usr/local/bin/nroff". You can use the following command to create this link:

ln -s /usr/local/bin/nroff /bin/nroff

Some "src"-packages include a README_FLOSS file. Consult this file for NSK/OSS specific information. Other install information may be found in the Package- or Version-specific 'Readme' files in the grid above.

As a convenience, several packages have been placed into "Floss Personality" files. Together, these packages form much of the "Linux Standard Base Specification". Installation of all these packages creates an environment much like that of a base Linux installation. There is a personality file for the TNS/R servers ("floss_personality-nsr.tar") one for the TNS/E servers ("floss_personality-nse.tar"), and one for TNS/X servers ("floss_personality-nsx.tar"). Download the personality file, then use this command to extract the packages contained within the file:

tar -xvf 'floss_personality_file'

The packages will be placed in the current directory. You can then install the individual packages.

Paging and Searching Functionality

You can page through the contents, and optionally filter the packages.

To filter by Package Name, simply type into the input field underneath the package header. The contents of the table will automatically filter to anything that contains what you type.

The paging information at the top and bottom of the table allows you to pick a page number directly, go back or forward a page, or to the beginning or end. Also, you can change the number of packages per page by choosing the drop down on the right.

The package list contains one row for each package. To see all the versions of a package, you can click on the small 'Right Arrow' button in the left column. This allows you to more easily search for a package by name. You can close the detail by clicking the 'down' arrow button in the same left column.