getprogname: fix port to IRIXdiff --git a/doc/ctime.texi b/doc/ctime.texideleted file mode 100644index 1354c6c..0000000--- a/doc/ctime.texi+++ /dev/null@@ -1,30 +0,0 @@-@node ctime-@section ctime-@findex ctime--@c Copyright (C) 2005, 2009-2017 Free Software Foundation, Inc.--@c Permission is granted to copy, distribute and/or modify this document-@c under the terms of the GNU Free Documentation License, Version 1.3 or-@c any later version published by the Free Software Foundation; with no-@c Invariant Sections, no Front-Cover Texts, and no Back-Cover-@c Texts. A copy of the license is included in the ``GNU Free-@c Documentation License'' file as part of this distribution.--The @code{ctime} function need not be reentrant, and consequently is-not required to be thread safe. Implementations of @code{ctime}-typically write the time stamp into static buffer. If two threads-call @code{ctime} at roughly the same time, you might end up with the-wrong date in one of the threads, or some undefined string. There is-a re-entrant interface @code{ctime_r}, that take a pre-allocated-buffer and length of the buffer, and return @code{NULL} on errors.-The input buffer should be at least 26 bytes in size. The output-string is locale-independent. However, years can have more than 4-digits if @code{time_t} is sufficiently wide, so the length of the-required output buffer is not easy to determine. Increasing the-buffer size when @code{ctime_r} return @code{NULL} is not necessarily-sufficient. The @code{NULL} return value could mean some other error-condition, which will not go away by increasing the buffer size.--A more flexible function is @code{strftime}. However, note that it is-locale dependent.diff --git a/doc/inet_ntoa.texi b/doc/inet_ntoa.texideleted file mode 100644index 9db025f..0000000--- a/doc/inet_ntoa.texi+++ /dev/null@@ -1,22 +0,0 @@-@node inet_ntoa-@section inet_ntoa-@findex inet_ntoa--@c Copyright (C) 2005, 2009-2017 Free Software Foundation, Inc.--@c Permission is granted to copy, distribute and/or modify this document-@c under the terms of the GNU Free Documentation License, Version 1.3 or-@c any later version published by the Free Software Foundation; with no-@c Invariant Sections, no Front-Cover Texts, and no Back-Cover-@c Texts. A copy of the license is included in the ``GNU Free-@c Documentation License'' file as part of this distribution.--The @code{inet_ntoa} function need not be reentrant, and consequently-is not required to be thread safe. Implementations of-@code{inet_ntoa} typically write the time stamp into static buffer.-If two threads call @code{inet_ntoa} at roughly the same time, you-might end up with the wrong date in one of the threads, or some-undefined string. Further, @code{inet_ntoa} is specific for-IPv4 addresses.--A protocol independent function is @code{inet_ntop}.

-HP-UX @command{make} updates targets which have the same time stamps as+HP-UX @command{make} updates targets which have the same timestamps astheir prerequisites, which makes it generally unusable when shippedgenerated files such as @command{configure} are involved. Use GNU@command{make} instead.diff --git a/doc/parse-datetime.texi b/doc/parse-datetime.texiindex 2b168a4..9568a4a 100644--- a/doc/parse-datetime.texi+++ b/doc/parse-datetime.texi@@ -311,7 +311,7 @@ unambiguous numeric time zone corrections like @samp{-0500}, asdescribed in the previous section.

If neither a time zone item nor a time zone correction is supplied,-time stamps are interpreted using the rules of the default time zone+timestamps are interpreted using the rules of the default time zone(@pxref{Specifying time zone rules}).

@@ -478,12 +478,12 @@ year.@node Seconds since the Epoch@section Seconds since the Epoch

-If you precede a number with @samp{@@}, it represents an internal time-stamp as a count of seconds. The number can contain an internal+If you precede a number with @samp{@@}, it represents an internal+timestamp as a count of seconds. The number can contain an internaldecimal point (either @samp{.} or @samp{,}); any excess precision notsupported by the internal representation is truncated toward minusinfinity. Such a number cannot be combined with any other date-item, as it specifies a complete time stamp.+item, as it specifies a complete timestamp.

@cindex beginning of time, for POSIX@cindex epoch, for POSIXdiff --git a/doc/posix-functions/ctime.texi b/doc/posix-functions/ctime.texiindex 6bff20c..f5a7c27 100644--- a/doc/posix-functions/ctime.texi+++ b/doc/posix-functions/ctime.texi@@ -17,7 +17,7 @@ This function may overflow its internal buffer if an invalid year is passed.@itemThe @code{ctime} function need not be reentrant, and consequently isnot required to be thread safe. Implementations of @code{ctime}-typically write the time stamp into static buffer. If two threads+typically write the timestamp into static buffer. If two threadscall @code{ctime} at roughly the same time, you might end up with thewrong date in one of the threads, or some undefined string. There isa re-entrant interface @code{ctime_r}.diff --git a/doc/posix-functions/inet_ntoa.texi b/doc/posix-functions/inet_ntoa.texiindex a21f319..56b497d 100644--- a/doc/posix-functions/inet_ntoa.texi+++ b/doc/posix-functions/inet_ntoa.texi@@ -18,7 +18,7 @@ mingw, MSVC 9.@itemThe @code{inet_ntoa} function need not be reentrant, and consequentlyis not required to be thread safe. Implementations of-@code{inet_ntoa} typically write the time stamp into static buffer.+@code{inet_ntoa} typically write the timestamp into static buffer.If two threads call @code{inet_ntoa} at roughly the same time, youmight end up with the wrong date in one of the threads, or someundefined string.diff --git a/lib/fdutimensat.c b/lib/fdutimensat.cindex 1475bb0..ff68490 100644--- a/lib/fdutimensat.c+++ b/lib/fdutimensat.c@@ -27,14 +27,14 @@#include <fcntl.h>#include <sys/stat.h>

-/* Set the access and modification time stamps of FD (a.k.a. FILE) to be+/* Set the access and modification timestamps of FD (a.k.a. FILE) to beTIMESPEC[0] and TIMESPEC[1], respectively; relative to directory DIR.FD must be either negative -- in which case it is ignored --or a file descriptor that is open on FILE.If FD is nonnegative, then FILE can be NULL, which meansuse just futimes (or equivalent) instead of utimes (or equivalent),and fail if on an old system without futimes (or equivalent).- If TIMESPEC is null, set the time stamps to the current time.+ If TIMESPEC is null, set the timestamps to the current time.ATFLAG is passed to utimensat if FD is negative or futimens wasunsupported, which can allow operation on FILE as a symlink.Return 0 on success, -1 (setting errno) on failure. */diff --git a/lib/futimens.c b/lib/futimens.cindex d370568..213e9b7 100644--- a/lib/futimens.c+++ b/lib/futimens.c@@ -22,10 +22,10 @@

#include "utimens.h"

-/* Set the access and modification time stamps of FD to be+/* Set the access and modification timestamps of FD to beTIMESPEC[0] and TIMESPEC[1], respectively.Fail with ENOSYS on systems without futimes (or equivalent).- If TIMESPEC is null, set the time stamps to the current time.+ If TIMESPEC is null, set the timestamps to the current time.Return 0 on success, -1 (setting errno) on failure. */intfutimens (int fd, struct timespec const times[2])diff --git a/lib/mktime.c b/lib/mktime.cindex cd52835..2efd44a 100644--- a/lib/mktime.c+++ b/lib/mktime.c@@ -153,7 +153,7 @@ isdst_differ (int a, int b)

/* Return an integer value measuring (YEAR1-YDAY1 HOUR1:MIN1:SEC1) -(YEAR0-YDAY0 HOUR0:MIN0:SEC0) in seconds, assuming that the clocks- were not adjusted between the time stamps.+ were not adjusted between the timestamps.

The YEAR values uses the same numbering as TP->tm_year. Valuesneed not be in the usual range. However, YEAR1 must not overflowdiff --git a/lib/parse-datetime.h b/lib/parse-datetime.hindex a777aac..fa6a9a3 100644--- a/lib/parse-datetime.h+++ b/lib/parse-datetime.h@@ -1,4 +1,4 @@-/* Parse a string into an internal time stamp.+/* Parse a string into an internal timestamp.

@@ -24,7 +24,7 @@Modified by Paul Eggert <***@twinsun.com> in August 1999 to dothe right thing about local DST. Also modified by Paul Eggert<***@cs.ucla.edu> in February 2004 to support- nanosecond-resolution time stamps, and in October 2004 to support+ nanosecond-resolution timestamps, and in October 2004 to supportTZ strings in dates. */

- For each time stamp T, this code assumes that either:+ For each timestamp T, this code assumes that either:

* T.tv_nsec is in the range 0..999999999; or* T.tv_sec corresponds to a valid leap second on a host that supports@@ -56,7 +56,7 @@ make_timespec (time_t s, long int ns)* T.tv_sec is the minimum time_t value and T.tv_nsec is -1; orT.tv_sec is the maximum time_t value and T.tv_nsec is 2000000000.This allows for special struct timespec values that are less or- greater than all possible valid time stamps.+ greater than all possible valid timestamps.

In all these cases, it is safe to subtract two tv_nsec values andconvert the result to integer without worrying about overflow ondiff --git a/lib/utimecmp.c b/lib/utimecmp.cindex 1d7745f..cd773ae 100644--- a/lib/utimecmp.c+++ b/lib/utimecmp.c@@ -1,4 +1,4 @@-/* utimecmp.c -- compare file time stamps+/* utimecmp.c -- compare file timestamps

-/* Describe a file system and its time stamp resolution in nanoseconds. */+/* Describe a file system and its timestamp resolution in nanoseconds. */struct fs_res{/* Device number of file system. */dev_t dev;

- /* An upper bound on the time stamp resolution of this file system,+ /* An upper bound on the timestamp resolution of this file system,ignoring any resolution that cannot be set via utimens. It isrepresented by an integer count of nanoseconds. It must beeither 2 billion, or a power of 10 that is no greater than a@@ -108,9 +108,9 @@ dev_info_compare (void const *x, void const *y)If OPTIONS & UTIMECMP_TRUNCATE_SOURCE, do the comparison after SRC isconverted to the destination's timestamp resolution as filtered throughutimens. In this case, return -2 if the exact answer cannot be- determined; this can happen only if the time stamps are very close and+ determined; this can happen only if the timestamps are very close andthere is some trouble accessing the file system (e.g., the user does not- have permission to futz with the destination's time stamps). */+ have permission to futz with the destination's timestamps). */

- /* Determine the actual time stamp resolution for the+ /* Determine the actual timestamp resolution for thedestination file system (after truncation due to- SYSCALL_RESOLUTION) by setting the access time stamp of the+ SYSCALL_RESOLUTION) by setting the access timestamp of thedestination to the existing access time, except withtrailing nonzero digits. */

-/* Set the access and modification time stamps of FD (a.k.a. FILE) to be+/* Set the access and modification timestamps of FD (a.k.a. FILE) to beTIMESPEC[0] and TIMESPEC[1], respectively.FD must be either negative -- in which case it is ignored --or a file descriptor that is open on FILE.If FD is nonnegative, then FILE can be NULL, which meansuse just futimes (or equivalent) instead of utimes (or equivalent),and fail if on an old system without futimes (or equivalent).- If TIMESPEC is null, set the time stamps to the current time.+ If TIMESPEC is null, set the timestamps to the current time.Return 0 on success, -1 (setting errno) on failure. */

-/* Set the access and modification time stamps of FILE to be+/* Set the access and modification timestamps of FILE to beTIMESPEC[0] and TIMESPEC[1], respectively, without dereferencingsymlinks. Fail with ENOSYS if the platform does not supportchanging symlink timestamps, but FILE was a symlink. */diff --git a/lib/utimensat.c b/lib/utimensat.cindex 7c5ee89..7605747 100644--- a/lib/utimensat.c+++ b/lib/utimensat.c@@ -133,11 +133,11 @@ rpl_utimensat (int fd, char const *file, struct timespec const times[2],

#endif /* !HAVE_UTIMENSAT */

-/* Set the access and modification time stamps of FILE to be+/* Set the access and modification timestamps of FILE to beTIMESPEC[0] and TIMESPEC[1], respectively; relative to directoryFD. If flag is AT_SYMLINK_NOFOLLOW, change the times of a symlink,or fail with ENOSYS if not possible. If TIMESPEC is null, set the- time stamps to the current time. If possible, do it without+ timestamps to the current time. If possible, do it withoutchanging the working directory. Otherwise, resort to usingsave_cwd/fchdir, then utimens/restore_cwd. If either the save_cwdor the restore_cwd fails, then give a diagnostic and exit nonzero.diff --git a/lib/xtime.h b/lib/xtime.hindex 810a3c7..6cea17c 100644--- a/lib/xtime.h+++ b/lib/xtime.h@@ -1,4 +1,4 @@-/* xtime -- extended-resolution integer time stamps+/* xtime -- extended-resolution integer timestamps

-/* xtime_t is a signed type used for time stamps. It is an integer+/* xtime_t is a signed type used for timestamps. It is an integertype that is a count of nanoseconds -- except for obsolescent hostswithout sufficiently-wide integers, where it is a count ofseconds. */diff --git a/modules/utimecmp b/modules/utimecmpindex 398411e..c7eee89 100644--- a/modules/utimecmp+++ b/modules/utimecmp@@ -1,5 +1,5 @@Description:-compare file time stamps+compare file timestamps

/* These two tests fail on 64-bit Solaris up through at least- Solaris 10, which is off by one day for time stamps before+ Solaris 10, which is off by one day for timestamps before0001-01-01 00:00:00 UTC. */{ "000001010000.00", 13, 1,- INT64_C (62167219200)},/* Sat Jan 1 00:00:00 0 */

Whenever making a global change like this (for which regression isprobable), I like to add something to help ensure consistency. Wealready have a "syntax-check" rule to prohibit things like "can not",so it's easy to add there: