[xsrc/xorg]: xsrc/external/mit/libXrandr/dist initial import of libXrandr-1.5.2

[mrg <mrg%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/xsrc/rev/fc11183c3d1d
branches:  xorg
changeset: 10232:fc11183c3d1d
user:      mrg <mrg%NetBSD.org@localhost>
date:      Mon Mar 18 02:30:12 2019 +0000

description:
initial import of libXrandr-1.5.2

diffstat:

 external/mit/libXrandr/dist/ChangeLog       |    85 +-
 external/mit/libXrandr/dist/INSTALL         |   119 +-
 external/mit/libXrandr/dist/Makefile.am     |     2 +
 external/mit/libXrandr/dist/Makefile.in     |    47 +-
 external/mit/libXrandr/dist/README.md       |    21 +
 external/mit/libXrandr/dist/aclocal.m4      |  5220 +++++++++++++----------
 external/mit/libXrandr/dist/compile         |     2 +-
 external/mit/libXrandr/dist/config.guess    |   854 +--
 external/mit/libXrandr/dist/config.h.in     |     3 +-
 external/mit/libXrandr/dist/config.sub      |   334 +-
 external/mit/libXrandr/dist/configure       |  2228 ++++++----
 external/mit/libXrandr/dist/configure.ac    |     4 +-
 external/mit/libXrandr/dist/depcomp         |     2 +-
 external/mit/libXrandr/dist/install-sh      |   354 +-
 external/mit/libXrandr/dist/ltmain.sh       |  5838 ++++++++++++++++----------
 external/mit/libXrandr/dist/man/Makefile.in |    23 +-
 external/mit/libXrandr/dist/missing         |     2 +-
 external/mit/libXrandr/dist/src/Makefile.in |    25 +-
 external/mit/libXrandr/dist/src/XrrCrtc.c   |     4 +
 19 files changed, 8860 insertions(+), 6307 deletions(-)

diffs (truncated from 26618 to 300 lines):

diff -r dab0a1758450 -r fc11183c3d1d external/mit/libXrandr/dist/ChangeLog
--- a/external/mit/libXrandr/dist/ChangeLog     Mon Mar 18 02:30:08 2019 +0000
+++ b/external/mit/libXrandr/dist/ChangeLog     Mon Mar 18 02:30:12 2019 +0000
@@ -1,3 +1,78 @@
+commit 55dcda4518eda8ae03ef25ea29d3c994ad71eb0a
+Author: Alan Coopersmith <alan.coopersmith%oracle.com@localhost>
+Date:   Sat Mar 16 13:54:20 2019 -0700
+
+    libXrandr 1.5.2
+    
+    Signed-off-by: Alan Coopersmith <alan.coopersmith%oracle.com@localhost>
+
+commit 2a03e8d069fce635981aad248e1cab14ed93e176
+Author: Alan Coopersmith <alan.coopersmith%oracle.com@localhost>
+Date:   Sat Mar 16 13:53:42 2019 -0700
+
+    Add description of libXrandr to README.md
+    
+    Signed-off-by: Alan Coopersmith <alan.coopersmith%oracle.com@localhost>
+
+commit 583d4f114d36e4df87ba3ed1201acae4aefb68dc
+Author: Alan Coopersmith <alan.coopersmith%oracle.com@localhost>
+Date:   Fri Dec 7 19:48:28 2018 -0800
+
+    Update configure.ac bug URL for gitlab migration
+    
+    Signed-off-by: Alan Coopersmith <alan.coopersmith%oracle.com@localhost>
+
+commit 08fab8367ea5357314d1c54edac04bc6a38da074
+Author: Alan Coopersmith <alan.coopersmith%oracle.com@localhost>
+Date:   Mon Nov 19 22:35:01 2018 -0800
+
+    Update README for gitlab migration
+    
+    Signed-off-by: Alan Coopersmith <alan.coopersmith%oracle.com@localhost>
+
+commit 87227e5fc79750d3eccc3c3482a3c5b3f2af2e90
+Author: Tobias Stoeckmann <tobias%stoeckmann.org@localhost>
+Date:   Sat Jan 28 15:37:57 2017 +0100
+
+    Fix memory leak on error paths
+    
+    Introduced in commit a0df3e1c7728205e5c7650b2e6dce684139254a6 "Avoid out
+    of boundary accesses on illegal responses"
+    
+    Signed-off-by: Julien Cristau <jcristau%debian.org@localhost>
+
+commit 5fb14f7a2c6da81c8e6bb325b354141233ab7d0a
+Author: Mihail Konev <k.mvc%ya.ru@localhost>
+Date:   Thu Jan 26 13:52:49 2017 +1000
+
+    autogen: add default patch prefix
+    
+    Signed-off-by: Mihail Konev <k.mvc%ya.ru@localhost>
+
+commit e0303d9c61d55081ffe4365a24107d851f457948
+Author: Emil Velikov <emil.l.velikov%gmail.com@localhost>
+Date:   Mon Mar 9 12:00:52 2015 +0000
+
+    autogen.sh: use quoted string variables
+    
+    Place quotes around the $srcdir, $ORIGDIR and $0 variables to prevent
+    fall-outs, when they contain space.
+    
+    Signed-off-by: Emil Velikov <emil.l.velikov%gmail.com@localhost>
+    Reviewed-by: Peter Hutterer <peter.hutterer%who-t.net@localhost>
+    Signed-off-by: Peter Hutterer <peter.hutterer%who-t.net@localhost>
+
+commit f26e07fa0fdb7f5cb5c82a3bb0ab5494fe3faa29
+Author: Peter Hutterer <peter.hutterer%who-t.net@localhost>
+Date:   Tue Jan 24 10:32:07 2017 +1000
+
+    autogen.sh: use exec instead of waiting for configure to finish
+    
+    Syncs the invocation of configure with the one from the server.
+    
+    Signed-off-by: Peter Hutterer <peter.hutterer%who-t.net@localhost>
+    Reviewed-by: Emil Velikov <emil.velikov%collabora.com@localhost>
+
 commit 54ac1eb5d14636002b018607227c6d52cca0b754
 Author: Matthieu Herrb <matthieu.herrb%laas.fr@localhost>
 Date:   Tue Oct 4 21:23:23 2016 +0200
@@ -871,7 +946,7 @@
     
     Conflicts:
     
-       src/Xrandr.c
+            src/Xrandr.c
 
 commit 00f2e30d0b8296668776d62a4c47f96bf95faa08
 Author: Julien Cristau <jcristau%debian.org@localhost>
@@ -1050,9 +1125,9 @@
     Fix read sizes for 64-bit machines.
     
     Be consistent in variable usage:
-       nbytes = network byte length.
-       rbytes = memory byte length.
-       nbytesRead = actual network bytes read.
+            nbytes = network byte length.
+            rbytes = memory byte length.
+            nbytesRead = actual network bytes read.
     Malloc rbytes data to pass to _XRead*, but use nbytes as the
     amount of data to read (yes, this is insane, welcome to Xlib).
     Some of this patch is semi-gratuitous, but the goal is to be consistent
@@ -1111,7 +1186,7 @@
     
     Conflicts:
     
-       configure.ac
+            configure.ac
 
 commit 0dba1be7969aa56f934d93889cbd589b3dafd3d4
 Author: Keith Packard <keithp%neko.keithp.com@localhost>
diff -r dab0a1758450 -r fc11183c3d1d external/mit/libXrandr/dist/INSTALL
--- a/external/mit/libXrandr/dist/INSTALL       Mon Mar 18 02:30:08 2019 +0000
+++ b/external/mit/libXrandr/dist/INSTALL       Mon Mar 18 02:30:12 2019 +0000
@@ -1,11 +1,13 @@
 Installation Instructions
 *************************
 
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
-2006, 2007, 2008 Free Software Foundation, Inc.
+Copyright (C) 1994-1996, 1999-2002, 2004-2011 Free Software Foundation,
+Inc.
 
-   This file is free documentation; the Free Software Foundation gives
-unlimited permission to copy, distribute and modify it.
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.
 
 Basic Installation
 ==================
@@ -13,7 +15,11 @@
    Briefly, the shell commands `./configure; make; make install' should
 configure, build, and install this package.  The following
 more-detailed instructions are generic; see the `README' file for
-instructions specific to this package.
+instructions specific to this package.  Some packages provide this
+`INSTALL' file but do not implement all of the features documented
+below.  The lack of an optional feature in a given package is not
+necessarily a bug.  More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
 
    The `configure' shell script attempts to guess correct values for
 various system-dependent variables used during compilation.  It uses
@@ -42,7 +48,7 @@
 you want to change it or regenerate `configure' using a newer version
 of `autoconf'.
 
-The simplest way to compile this package is:
+   The simplest way to compile this package is:
 
   1. `cd' to the directory containing the package's source code and type
      `./configure' to configure the package for your system.
@@ -53,12 +59,22 @@
   2. Type `make' to compile the package.
 
   3. Optionally, type `make check' to run any self-tests that come with
-     the package.
+     the package, generally using the just-built uninstalled binaries.
 
   4. Type `make install' to install the programs and any data files and
-     documentation.
+     documentation.  When installing into a prefix owned by root, it is
+     recommended that the package be configured and built as a regular
+     user, and only the `make install' phase executed with root
+     privileges.
 
-  5. You can remove the program binaries and object files from the
+  5. Optionally, type `make installcheck' to repeat any self-tests, but
+     this time using the binaries in their final installed location.
+     This target does not install anything.  Running this target as a
+     regular user, particularly if the prior `make install' required
+     root privileges, verifies that the installation completed
+     correctly.
+
+  6. You can remove the program binaries and object files from the
      source code directory by typing `make clean'.  To also remove the
      files that `configure' created (so you can compile the package for
      a different kind of computer), type `make distclean'.  There is
@@ -67,8 +83,15 @@
      all sorts of other programs in order to regenerate files that came
      with the distribution.
 
-  6. Often, you can also type `make uninstall' to remove the installed
-     files again.
+  7. Often, you can also type `make uninstall' to remove the installed
+     files again.  In practice, not all packages have tested that
+     uninstallation works correctly, even though it is required by the
+     GNU Coding Standards.
+
+  8. Some packages, particularly those that use Automake, provide `make
+     distcheck', which can by used by developers to test that all other
+     targets like `make install' and `make uninstall' work correctly.
+     This target is generally not run by end users.
 
 Compilers and Options
 =====================
@@ -93,7 +116,8 @@
 own directory.  To do this, you can use GNU `make'.  `cd' to the
 directory where you want the object files and executables to go and run
 the `configure' script.  `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
+source code in the directory that `configure' is in and in `..'.  This
+is known as a "VPATH" build.
 
    With a non-GNU `make', it is safer to compile the package for one
 architecture at a time in the source code directory.  After you have
@@ -120,7 +144,8 @@
    By default, `make install' installs the package's commands under
 `/usr/local/bin', include files under `/usr/local/include', etc.  You
 can specify an installation prefix other than `/usr/local' by giving
-`configure' the option `--prefix=PREFIX'.
+`configure' the option `--prefix=PREFIX', where PREFIX must be an
+absolute file name.
 
    You can specify separate installation prefixes for
 architecture-specific files and architecture-independent files.  If you
@@ -131,15 +156,46 @@
    In addition, if you use an unusual directory layout you can give
 options like `--bindir=DIR' to specify different values for particular
 kinds of files.  Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
+you can set and what kinds of files go in them.  In general, the
+default for these options is expressed in terms of `${prefix}', so that
+specifying just `--prefix' will affect all of the other directory
+specifications that were not explicitly provided.
+
+   The most portable way to affect installation locations is to pass the
+correct locations to `configure'; however, many packages provide one or
+both of the following shortcuts of passing variable assignments to the
+`make install' command line to change installation locations without
+having to reconfigure or recompile.
+
+   The first method involves providing an override variable for each
+affected directory.  For example, `make install
+prefix=/alternate/directory' will choose an alternate location for all
+directory configuration variables that were expressed in terms of
+`${prefix}'.  Any directories that were specified during `configure',
+but not in terms of `${prefix}', must each be overridden at install
+time for the entire installation to be relocated.  The approach of
+makefile variable overrides for each directory variable is required by
+the GNU Coding Standards, and ideally causes no recompilation.
+However, some platforms have known limitations with the semantics of
+shared libraries that end up requiring recompilation when using this
+method, particularly noticeable in packages that use GNU Libtool.
+
+   The second method involves providing the `DESTDIR' variable.  For
+example, `make install DESTDIR=/alternate/directory' will prepend
+`/alternate/directory' before all installation names.  The approach of
+`DESTDIR' overrides is not required by the GNU Coding Standards, and
+does not work on platforms that have drive letters.  On the other hand,
+it does better at avoiding recompilation issues, and works well even
+when some directory options were not specified in terms of `${prefix}'
+at `configure' time.
+
+Optional Features
+=================
 
    If the package supports it, you can cause programs to be installed
 with an extra prefix or suffix on their names by giving `configure' the
 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
 
-Optional Features
-=================
-
    Some packages pay attention to `--enable-FEATURE' options to
 `configure', where FEATURE indicates an optional part of the package.
 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
@@ -152,6 +208,13 @@
 you can use the `configure' options `--x-includes=DIR' and
 `--x-libraries=DIR' to specify their locations.
 
+   Some packages offer the ability to configure how verbose the
+execution of `make' will be.  For these packages, running `./configure
+--enable-silent-rules' sets the default to minimal output, which can be
+overridden with `make V=1'; while running `./configure
+--disable-silent-rules' sets the default to verbose, which can be
+overridden with `make V=0'.
+
 Particular systems
 ==================
 
@@ -159,10 +222,15 @@
 CC is not installed, it is recommended to use the following options in
 order to use an ANSI C compiler:
 
-     ./configure CC="cc -Ae"
+     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
 
 and if that doesn't work, install pre-built binaries of GCC for HP-UX.
 
+   HP-UX `make' updates targets which have the same time stamps as
+their prerequisites, which makes it generally unusable when shipped
+generated files such as `configure' are involved.  Use GNU `make'
+instead.
+
    On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot