INN commit: trunk (doc/FAQ m4/pam-const.m4)

INN Commit rra at isc.org
Wed Dec 9 21:54:25 UTC 2020


    Date: Wednesday, December 9, 2020 @ 13:54:25
  Author: iulius
Revision: 10449

Update new name of macOS

Modified:
  trunk/doc/FAQ
  trunk/m4/pam-const.m4

-----------------+
 doc/FAQ         |    8 ++++----
 m4/pam-const.m4 |    8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)

Modified: doc/FAQ
===================================================================
--- doc/FAQ	2020-12-09 21:53:27 UTC (rev 10448)
+++ doc/FAQ	2020-12-09 21:54:25 UTC (rev 10449)
@@ -75,7 +75,7 @@
     5.2.  Using raw devices on Solaris destroys the partition table
     5.3.  Will INN run on Windows?
     5.4.  Why aren't INN's files where the documentation says they are?
-    5.5.  Running INN on Mac OS X
+    5.5.  Running INN on macOS
 
 6.  How Do I...
     6.1.  Set up a server with no external feeds, just local groups
@@ -1018,7 +1018,7 @@
 
 ------------------------------
 
-Subject: 5.5. Running INN on Mac OS X
+Subject: 5.5. Running INN on macOS
 
 Richard Tobin provided the following advice in news.software.nntp on
 2013-06-29 based on experience with running INN on Snow Leopard:
@@ -1047,8 +1047,8 @@
     function related to "vprocmgr".  Running from launchd shouldn't have
     this problem, and it appears to be fixed in Mountain Lion.
 
-The Perl flags come from the Perl configuration, so this problem may be
-fixed with newer builds of Mac OS X.
+The Perl flags come from the Perl configuration; this problem is fixed
+with current builds of macOS.
 
 ------------------------------
 

Modified: m4/pam-const.m4
===================================================================
--- m4/pam-const.m4	2020-12-09 21:53:27 UTC (rev 10448)
+++ m4/pam-const.m4	2020-12-09 21:54:25 UTC (rev 10449)
@@ -3,10 +3,10 @@
 dnl
 dnl Linux marks several PAM arguments const, including the argument to
 dnl pam_get_item and some arguments to conversation functions, which Solaris
-dnl doesn't.  Mac OS X marks the first argument to pam_strerror const, and
-dnl other platforms don't.  This test tries to determine which style is in use
-dnl to select whether to declare variables const and how to prototype
-dnl functions in order to avoid compiler warnings.
+dnl doesn't.  Mac OS X, OS X and macOS mark the first argument to pam_strerror
+dnl const, and other platforms don't.  This test tries to determine which
+dnl style is in use to select whether to declare variables const and how
+dnl to prototype functions in order to avoid compiler warnings.
 dnl
 dnl Since this is just for compiler warnings, it's not horribly important if
 dnl we guess wrong.  This test is ugly, but it seems to work.



More information about the inn-committers mailing list