AC_PATH_X checks for Xt, not for X itself

[Ben Pfaff]

Debian bug 327655 complains that AC_PATH_X in Autoconf checks for
the presence of Xt development headers and libraries, whereas the
stated purpose of the macro is to check for X headers and
libraries.  In Debian, Xt was recently broken out from the main X
development package, so this check has become a bit of an issue:
some packages now need to build-depend on libxt-dev even though
they don't use it.

For the full history of this bug, you can view the Debian bug
report:
        http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=327655

The following patch fixes the problem.  It does have the
backward-compatibility implication that any program that expected
AC_PATH_X to check for Xt will now only know that X itself is
installed.

--- tmp/autoconf-2.59a/lib/autoconf/libs.m4     2005-09-14 21:50:55.000000000 
-0700
+++ autoconf-2.59a/lib/autoconf/libs.m4 2005-09-14 21:47:42.000000000 -0700
@@ -345,7 +345,7 @@
   else
 dnl If we are called with less than 3 arguments, use the defaults
     m4_ifval([$3], [_AC_PATH_X($@)],
-                   [_AC_PATH_X([Xt],[X11/Intrinsic.h],[XtMalloc (0)])])
+                   [_AC_PATH_X([X11],[X11/Xlib.h],[XrmInitialize ()])])
   fi
   eval "$ac_cv_have_x"
 fi # $with_x != no


-- 
"You know, they probably have special dorms for people like us."
--American Pie