fix a pile of lintian warnings

[debian/sudo] / INSTALL

diff --git a/INSTALL b/INSTALL
index 6597087f2d7807cb0e9efbe63aa29a6a0680ab83..a2c9cb46c4004cad237e5a5e438267123cc3a28b 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -99,9 +99,6 @@ Directory and file names:
        Find the sources in DIR [configure dir or ..]
 
 Special features/options:
-  --with-CC=PATH
-       Specifies path to C compiler you wish to use.
-
   --with-incpath=DIR
        Adds the specified directory (or directories) to CPPFLAGS
        so configure and the compiler will look there for include
@@ -630,6 +627,9 @@ The following options are also configurable at runtime:
   --enable-warnings
        Enable compiler warnings when building sudo with gcc.
 
+  --enable-werror
+       Enable the -Werror compiler option when building sudo with gcc.
+
   --enable-admin-flag
        Enable the creation of an Ubuntu-style admin flag file
        the first time sudo is run.
@@ -712,14 +712,15 @@ Solaris 2.x:
     CD.  You can also get them from various places on the net,
     including http://www.sunfreeware.com/
     NOTE: sudo will *not* build with the sun C compiler in BSD
-         compatibility mode (/usr/ucb/cc).  Sudo is designed to
-         compile with the standard C compiler (or gcc) and will
-         not build correctly with /usr/ucb/cc.  You can use the
-         `--with-CC' option to point `configure' to the non-ucb
-         compiler if it is not the first cc in your path.  Some
-         sites link /usr/ucb/cc to gcc; configure will not notice
-         this and still refuse to use /usr/ucb/cc, so make sure gcc
-         is also in your path if your site is setup this way.
+          compatibility mode (/usr/ucb/cc).  Sudo is designed to
+          compile with the standard C compiler (or gcc) and will
+          not build correctly with /usr/ucb/cc.  You can set the
+          CC environment variable to the non-ucb compiler when
+          running `configure' if it is not the first cc in your
+          path.  Some sites link /usr/ucb/cc to gcc; configure will
+          not notice this and still refuse to use /usr/ucb/cc, so
+          make sure gcc is also in your path if your site is setup
+          this way.
     Also: Older versions of Solaris come with a broken syslogd.
          If you have having problems with sudo logging you should
          make sure you have the latest syslogd patch installed.