<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0"> </HEAD> <BODY> As described in the INSTALL file, "Briefly, the shell commands `./configure; <PRE> make; make install' should configure, build, and install this package". In Makefile.am, the AM_MAINTAINER_MODE macro disables by default the maintainer build rules. If Makefile.am is changed, the make program will not reconfigure the component. Otherwise the package would be reconfigure with different or missing Autotools and could break, making it difficult for anyone to debug. When the component is built using build.sh or tinderbox, autogen.sh is used which passes the --enable-maintainer-mode option to ./configure. This allows the maintainer to make changes to the configuration and get an automatic rebuild when necessary. By shipping autogen.sh we are introducing another build entry point which isn't documented and is confusing. The behavior will also be different as it enables the maintainer build rules. </PRE> <TT>---</TT> <TT> Makefile.am |    2 +-</TT> <TT> 1 files changed, 1 insertions(+), 1 deletions(-)</TT> <TT>diff --git a/Makefile.am b/Makefile.am</TT> <TT>index a5e0730..3aa1fb4 100644</TT> <TT>--- a/Makefile.am</TT> <TT>+++ b/Makefile.am</TT> <TT>@@ -49,7 +49,7 @@ pkgconfigdir = $(libdir)/pkgconfig</TT> <TT> pkgconfig_DATA = xorg-server.pc</TT> <TT> endif</TT> <TT> </TT> <TT>-EXTRA_DIST = xorg-server.pc.in xorg-server.m4 ChangeLog autogen.sh</TT> <TT>+EXTRA_DIST = xorg-server.pc.in xorg-server.m4 ChangeLog</TT> <TT> </TT> <TT> DISTCHECK_CONFIGURE_FLAGS=\</TT> <TT> --with-xkb-path=$(XKB_BASE_DIRECTORY) \</TT> <TT>-- </TT> <TT>1.6.0.4</TT> </BODY> </HTML>