Table 3 lists the 81 GNV components updgraded to the latest GNU versions.

Table 3 GNV Components Upgraded to the Latest GNU Versions

awk	basename	bzcat	bzip2	bzip2recover	cat	chgrp
chmod	chown	cksum	cmp	comm	cp	csplit
cut	date	dd	df	diff	dirname	du
egrep	env	expand	expr	false	fgrep	file
find	fmt	fold	gawk	gnutar	grep	gunzip
gzip	head	hostname	id	install	join	less
ln	ls	man	manpath	mkdir	more	mv
nl	od	paste	patch	printenv	ps	pwd
rm	rmdir	sleep	sort	split	sum	tac
tail	tar	tee	touch	tr	True	Uname
Unexpand	Uniq	Unzip	Unzipsfx	Wc	Which	Whoami
Xargs	Xxd	Zcat	Zip

14.2 New GNV Components

Table 4 lists the new GNV components.

Table 4 New GNV Components

base64	diff3	dir	factor	kill
locate	logname	md5sum	mktemp	pathchk
pr	ptx	sdiff	seq	sha1sum
sha224sum	sha256sum	sha384sum	sha512sum	shuf
stat	test	timeout	truncate	vdir

14.3 GNV Version 3.0-1 Sources and Build Procedure

The GNV sources are copied to GNU:[SRC] directory during the installation. This directory contains the following files:

$ DIR GNU:[SRC] Directory GNU:[SRC] GNV_SOURCE.BCK;1 RESTORE_GNV_SOURCE.COM;1

Complete GNV build areas are packaged into the PCSI kit as backup saveset (GNV_SOURCE.BCK) . Backup saveset file can be extracted using RESTORE_GNV_SOURCE.COM . The backup saveset contains the complete source file along with the automated build procedure.

To build GNV:

1. Start and setup GNV procedure:

   $ @SYS$STARTUP:GNV$STARTUP.COM $ @GNU:[LIB]GNV_SETUP.COM

2. Invoke the GNV build:

   $ @[.build]build.com ALL BUILD

All normal problem-reporting channels are available for GNV users to report problems with the GNV software provided with OpenVMS Alpha and OpenVMS Integrity servers. Please note that OpenVMS engineering cannot guarantee resolution of all reported problems in this kit but will do its best to address all reports in a timely manner.

16 Bug Fixes

The latest GNV software includes fixes to bugs found on the indicated version of GNV. The fixes will apply to GNV running on either Alpha or Integrity server systems, except where specified otherwise.

16.1 Since Version 2.1-3

• GNV setup --- The result of pwd command does not display the same directory on the subshell and the main shell. Therefore, in the GNV$STARTUP.COM, SYS$POSIX_ROOT logical is defined as /TRANSLATION=CONCEALED. Now, the pwd command displays the same directory on the subshell and the main shell.
• GNV setup --- A system crash occurs, if the BIN logical is not defined to GNU:[BIN] in [LIB]GNV_SETUP.COM. Now, the BIN logical is created in the process table by the [LIB]GNV_SETUP.COM. By default, the BIN logical is defined in the SYS$SYSTEM.
• bash --- Sometimes bash does not clean the SYS$LOGIN:SH*.; temporary files. Instead it creates a new version without deleting the older versions. Now, SYS$LOGIN:SH*.; temporary files are deleted.
• cc --- The following problems are observed:
  • cc wrapper library lookup is unable to process any OpenVMS symbolic link and search the OpenVMS library such as TCPIP$LIBRARY:TCPIP$LIB.OLB. Now, the cc wrapper library lookup can process OpenVMS symbolic link and search the OpenVMS library.
  • The fix for -input_to_ld parameter to cc GNV wrapper is not able to process correctly . Instead the -input_to_ld parameter generates /OPT=file. Now, the cc GNV wrapper appends the ",\n`pwd`<file>/opt" after SYS$INPUT:/OPT.
• ld --- Linker wrapper ld does not match the linking order to Linux linking order. Now, linker wrapper ld matches the linking order to Linux linking order.

  Note -auto_symvec parameter is used only for linking and is valid only on ld command.

• Product removal fixes
  • This release fixes the GNV product removal issues on a standalone system. Issues with deassigning the GNV_OPTION_SOURCES logical while removing GNV is fixed to address this issue.
  • This release fixes the GNV product removal issue in a cluster. Issue while removing GNV from another node in a cluster other than installation node is fixed. The GNV$MNTROOT.COM procedure is added, which will be run before product removal to create a GNV mount point on a node other than the installation node.
• cc -l command --- To make GNV compatible with the UNIX environment, the search mechanism for library is modified when using the cc -l option.
• ZIP --- Zip issue with .DIR extension is fixed.
• Disk Free (DF) Utility --- The DF utility crashed on Alpha systems with an ACCVIO error, and on Integrity server systems, the DF utility failed to display the result. This release fixes these problems.
• g++ complier--- The G++ compiler was not working, bash is fixed to resolve this problem.
• bash --- While running the configure script, the conftest creates an empty file. The configure scripts receives an error from the C compiler that makes the script to consider that there is no functioning C compiler on the system.

• Installation creates undesired mount points.
  The installed start-up script PSX$UP_STARTUP.COM still includes the DoMountPoints subroutine, but the call to it is commented out. Customers who wish to enable this feature may remove the comment mark.
• Installation on Alpha and Integrity systems in a heterogeneous cluster
  The generated file SYS$STARTUP:GNV_DESTINATION.COM has been replaced by the file SYS$STARTUP:GNV_DESTINATION_archname.COM to avoid conflict.

• CONFIGURE scripts and config.h
  GNV is often used on OpenVMS systems to port and configure OpenSource software. Most OpenSource packages are distributed in source form. A configure script is run to determine the features of the system it is running on, and to configure the build files, especially the make files and one or more include files ( .h ).
  The configure script often generates an include file called config.h . This file contains the results of many of the tests performed by the configure script. The configure script runs numerous tests to determine features implemented by the local system. It then writes records to config.h based on the results of these tests.
  In the past, many of the results written to the config.h file have been wrong. This has been traced to a bug in bash . This problem is resolved in the version of bash shipped with this release of GNV. The problem with bash is illustrated by the following example, where the wrong branch of the if statement was taken.

  echo foo | true if test `eval echo no` = yes then echo Writing to confdefs.h else echo Not writing to anywhere. fi

  
  With this bug fix, configure scripts can be expected to generate more useful config.h files.

• Redirection of DCL commands on OpenVMS Integrity server systems
  Redirection of DCL commands now works reliably.
  OpenVMS on Integrity server systems tends to generate mailbox devices with five-digit unit numbers. On Alpha, these unit numbers were limited to four digits. Code used for redirection of DCL commands depended on four-digit unit numbers. For consistency with Integrity server systems, Alpha unit numbers have been increased to five digits.
• Definition of SYS$POSIX_ROOT
  The GNV startup file (SYS$STARTUP:GNV$STARTUP.COM) defines the logical name SYS$POSIX_ROOT, if that is not already defined. This allows GNV utilities to make use of a UNIX-like system root.
  This release defines SYS$POSIX_ROOT in a format that more closely matches the format expected by RMS. No directory is specified in the definition of this logical.
• Pipe to cut -f bug fixed
  In previous releases of GNV, piping output to a cut -fn command would hang. For example:

  bash$ cat nosuchfile | cut -f2

  
  This problem is resolved in GNV Version 1.6.

• Pipe operations hang
  Certain forms of pipe operations are known to have problems. For example:

  bash$ (cat t.txt) | less

  
  This command works fine for a small enough t.txt . If the file is larger, the command hangs.
  One workaround to this and certain other pipe hangs is to use the Run-Time Library's feature to increase the buffer size of the mailboxes used to implement pipes, as in the following example:

  $ DEFINE DECC$PIPE_BUFFER_SIZE 65000

  
  Do not use a value much larger than 65000. For example, 65535 does not work.
  For more information, refer to the discussion of the DECC$PIPE_BUFFER_SIZE feature in the Introduction Chapter of the HP C Run-Time Library Reference Manual for OpenVMS Systems.
  This allows the command to work for moderately large files. However, sufficiently large files will still hang.
  Another workaround to the hang is to use a temporary file as in the following example. Of course, this requires editing the script file.

  bash$ (cat t.txt) > s.txt; less s.txt; rm s.txt;

  
  The real problem is that bash should execute both the cat and the less child processes asynchronously. However, it does not currently do this. Instead, the less command does not get processed until the cat has completed. The output of the cat command is buffered in the pipe. If the pipe is not large enough to hold the entire output, then cat waits for the less function to read, but less does not run until the cat function completes. The result is a hang.
  HP will resolve this problem in a future release of GNV.

• bash Command Line Editing
  There are numerous problems with the bash History File and Command-Line Editing.
  HP will resolve these in some future release of GNV.
• $! shell variable returns a bad process id
  $! is supposed to return the process id of the most recently executed background job. Currently, it instead returns a job number, which is not useful for most purposes.
  HP will fix this problem in a future release of GNV.

Table 5 lists documentation provided with the GNV kit. Once you have installed the GNV software, you can find the documentation files in the directories indicated.

Table 6 lists sources of information on the Internet.

GNV includes the MAN utility, ported from GNU MAN. Also included are MAN page files for most of the utilities included in the GNV kit. Again, these MAN page files are extracted from GNU sources and might not exactly represent the utilities included with GNV.

In the following table, page counts are provided where appropriate and are approximations.

Table 5 GNV-Supplied Documentation

	File Name	Description and Comments
GNU:[000000] or /gnu
	GNVREADME_FIRST. (.HTML, .PDF, .PS, .TXT)	This document, which provides GNV product information and installation/setup instructions. Also available on the Open Source Tools CD documentation area. 30 pages.
GNU:[SRC.GNV.BASH] or /gnu/src/gnv/bash
	INSTALL.	Provides build and installation instructions for bash on GNU; not necessarily applicable to GNV on OpenVMS. Four pages.
	NEWS.	Lists recently fixed bash bugs. One page.
	RELEASE.	Describes new features of bash . Five pages.
GNU:[SRC.GNV.BASH.DOCUMENTATION] or /gnu/src/gnv/bash/documentation
	ARTICLE (.MS, .PS, .TXT)	White paper on bash . 11 pages.
	BASH (.1, .PS, .TXT)	MAN page. Source unknown. The .TXT file contains some unprintable text. 37 pages.
	BASH_REFERENCE_MANUAL.TXT	Reference manual describing the features and functionality of bash . This manual documents bash Version 2. This kit contains bash Version 1.14. This manual documents features not present in the provided software. For example, two such features are (1) arrays and (2) several invocation options (for example, bash -r ). Approximately 100 pages.
	BUILTINS (.1, PS, .TXT)	MAN page that documents the bash built-in commands. 11 pages.
	FAQ.	Contains a set of frequently-asked questions concerning bash . 12 pages.
	FEATURES (.DVI, .INFO, .PS, .TEXI)	A 1994 document describing bash features and functionality.
	READLINE (.3, .PS, .TXT)	MAN page documenting the readline() API. Useful for understanding bash command-line processing.
GNU:[SRC.GNV.BASH.CWRU] or /gnu/src/gnv/bash/cwru
	POSIX.NOTES	Discussion of the bash POSIX mode. One page.
GNU:[SRC.GNV.BASH.LIB.READLINE.DOC] or /gnu/src/gnv/bash/lib/readline/doc
	HISTORY.PS	Documents the history function (command-line recall) of readline. For both users and programmers. 18 pages.
	HISTORY.INFO	Technical guide to the history library. 12 pages.
	HSTECH.TEXINFO	Programmer's guide to the history library.
	HSUSER.TEXINFO	User's guide to the history library.
GNU:[SRC.GNV.BASH.LIB.TERMCAP.GROT] or /gnu/src/gnv/bash/lib/termcap/grot
	TERMCAP.INFO*	This series of files provides programmer's information about the termcap library. 100 pages.
GNU:[SRC.GNV.FINDUTILS.4_1] or /gnu/src/gnv/findutils/4_1
	README.	Technical usage notes for the find utility. One page.
	INSTALL.	Build and installation instructions applicable primarily to GNU on UNIX systems. Four pages.
	NEWS.	New features in recent versions of the find utility. Four pages.
	COPYING.	GNU General Public License regulations. Six pages.
GNU:[SRC.GNV.FINDUTILS.4_1.DOC] or /gnu/src/gnv/findutils/4_1/doc
	FIND.INFO-1	User's guide for find utility. 25 pages.
	FIND.INFO-2	Continuation of the user's guide. 18 pages.
	FIND.TEXI	Source file for the user's guide.
	PERM.TEXI	Discussion of UNIX file permissions. Six pages.
GNU:[SRC.GNV.GREP.GREP-2_4_2] or /gnu/src/gnv/grep/grep-2_4_2
	NEWS.	New features in recent versions of grep. Three pages.
	README.	Readme file for grep. One page.
	AUTHORS.	Acknowledgements. One page.
	THANKS.	Acknowledgements. One page.
	COPYING.	GNU General Public License regulations. Six pages.
	INSTALL.	Build and installation instructions for the GNU version of grep. Four pages.
GNU:[SRC.GNV.GREP.GREP-2_4_2.DOC] or /gnu/src/gnv/grep/grep-2_4_2/doc
	GREP (.1, .INFO, .TEXI)	User's guide for grep. 13 pages.
GNU:[SRC.GNV.SED.SED-3_02] or /gnu/src/gnv/sed/sed-3_02
	COPYING.	GNU General Public License regulations. Six pages.
	INSTALL.	Build and installation instructions for the GNU version of sed. Four pages.
	NEWS.	New featuers introduced in recent versions of sed. One page.
	README.	Readme file for sed. One page.
GNU:[SRC.GNV.SED.SED-3_02.DOC] or /gnu/src/gnv/sed/sed-3_02/doc
	SED (.1, .INFO, .TEXI)	User's guide for sed. 10 pages.
GNU:[SRC.GNV.MAKE.MAKE] or /gnu/src/gnv/make/make
	README.VMS	Release notes for the OpenVMS version of make. One page.
GNU:[SRC.GNV.LESS.LESS-358] or /gnu/src/gnv/less/less-358
	LESS.HLP	OpenVMS help file for the less utility. Four pages.
	LESS.MAN	MAN page text file for the less utility. 30 pages.
GNU:[SRC.GNV.TAR] or /gnu/src/gnv/tar
	AAAREADME.TXT	Build instructions and release for OpenVMS tar . Three pages.
GNU:[SRC.GNV.VITPU.DOC] or /gnu/src/gnv/vitpu/doc
	HOW-VI-WORKS.	Information on the internals of the vi text editor. Notes from developers. Three pages.
	README.	Readme file for vi . Four pages.
	TUTOR (.MEM, .RNO, .RNT, .RNX)	User's guide for novice vi text editor users. Six pages.
	VI (.HLP, .HLB, .MEM, .RNO, .RNT)	Help file and guide to using the OpenVMS VITPU utility that emulates the vi text editor. 27 pages.
GNU:[SRC.GNV.GZIP] or /gnu/src/gnv/gzip
	GZIP (.1, .DOC, .INFO, .TEXI)	User's guide for gzip. Six pages.
GNU:[SRC.GNV.ZIP.MAN] or /gnu/src/gnv/zip/man
	ZIP.1	User's guide for zip in source format.
GNU:[SRC.GNV.ZIP] or /gnu/src/gnv/zip
	ZIP.HLP	Help file (OpenVMS) for zip .
GNU:[SRC.GNV.UNZIP] or /gnu/src/gnv/unzip
	UNZIP.HLP	Help file (OpenVMS) for unzip .
	UNZIP.TXT	User's guide for unzip .
	README.	Readme file for unzip .
GNU:[SRC.GNV.UNZIP.MAN] or /gnu/src/gnv/unzip/man
	UNZIP.1	User's guide for unzip.
GNU:[LIB-LIBGDBM] or /gnu/lib-libgdbm
	README.TXT	Describes GNU C libgdbm library components provided for OpenVMS Alpha and Integrity server systems. Explains how to build libgbdm , and lists the files provided, restrictions, and changes made for OpenVMS. Three pages.
GNU:[LIB-LIBHASH] or /gnu/lib-libhash
	README.TXT	Describes GNU C libhash library components provided for OpenVMS Alpha and Integrity server systems. Explains how to build libhash , and lists the files provided, restrictions, and changes made for OpenVMS. Two pages.
GNU:[LIB-LIBREGEX] or /gnu/lib-libregex
	README.TXT	Describes GNU C libregex library components provided for OpenVMS Alpha and Integrity server systems. Explains how to build libregex , and lists the files provided, restrictions, and changes made for OpenVMS. Two pages.

Table 6 External Sources of Information

Description	location
GNU Project Website	http://www.gnu.org
GNV OpenVMS Website	http://gnv.sourceforge.net
	http://h71000.www7.hp.com/opensource/gnv.html