[PATCH] Autoconf FAQ update.

This is the autoconf 2.5 related changes to the FAQ and will make the FAQ specific to 21.5. Should I recast this to describe 21.4 and 21.5 options in the same document? Malcolm man/ChangeLog addition: 2005-03-05 Malcolm Purvis <malcolmp(a)xemacs.org&gt; * xemacs-faq.texi: Change configure arguments to the new autoconf 2.5 style. xemacs-autoconf-2.5 source patch: Diff command: cvs -q diff -u Files affected: man/xemacs-faq.texi Index: man/xemacs-faq.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/xemacs-faq.texi,v retrieving revision 1.84 diff -u -r1.84 xemacs-faq.texi --- man/xemacs-faq.texi 2005/02/04 02:51:21 1.84 +++ man/xemacs-faq.texi 2005/03/05 10:28:26 ＠＠ -1102,8 +1102,8 ＠＠ sparc-sun-sunos4.1.4 (gcc) ＠end example -Some systems have a dual mode 32-bit/64-bit compiler. On most of -these, XEmacs requires the ＠samp{--pdump} configure option to build +Some systems have a dual mode 32-bit/64-bit compiler. On most of these, +XEmacs requires the ＠samp{--enable-pdump} configure option to build correctly with the 64-bit version of the compiler. ＠example ＠＠ -3262,12 +3262,12 ＠＠ ＠code{cd $prefix/lib/xemacs ; tar zxvf <tarballname>} -If you have the packages somewhere nonstandard and don't want to -bother with ＠samp{$prefix} (for example, you're a developer and are -compiling the packages yourself, and want your own private copy of -everything), you can also directly specify this using ＠file{configure}. -To do this under 21.5 and above use the ＠samp{--package-prefix} parameter -to specify the directory under which you untarred the above tarballs. +If you have the packages somewhere nonstandard and don't want to bother +with ＠samp{$prefix} (for example, you're a developer and are compiling +the packages yourself, and want your own private copy of everything), +you can also directly specify this using ＠file{configure}. To do this +under 21.5 and above use the ＠samp{--with-package-prefix} parameter to +specify the directory under which you untarred the above tarballs. Under 21.4 and previous you need to use ＠samp{--package-path}, something like this: ＠＠ -3504,11 +3504,10 ＠＠ under ＠file{/usr/local/lib/xemacs}. You can specify where exactly XEmacs looks for packages by using the -＠samp{--package-prefix} or ＠samp{--package-path} parameters to -＠file{configure} (or the equivalent settings in ＠file{config.inc}, -under Windows), or setting the ＠samp{EMACSPACKAGEPATH} environment -variable (which has the same format as ＠samp{--package-path}). -(a)xref{Q2.1.1}. +＠samp{--with-package-prefix} or ＠samp{--with-package-path} parameters to +＠file{configure} (or the equivalent settings in ＠file{config.inc}, under +Windows), or setting the ＠samp{EMACSPACKAGEPATH} environment variable +(which has the same format as ＠samp{--with-package-path}). ＠xref{Q2.1.1}. See ＠file{configure.usage} for more info about the format of these ＠file{configure} parameters. ＠＠ -3547,14 +3546,14 ＠＠ using the following flags to ＠file{configure}: ＠example ---site-libraries=WHATEVER ---site-includes=WHATEVER +--with-site-libraries=WHATEVER +--with-site-includes=WHATEVER ＠end example If you have multiple paths to specify, use the following syntax: ＠example ---site-libraries='/path/one /path/two /path/etc' +--with-site-libraries='/path/one /path/two /path/etc' ＠end example ＠node Q2.2.2, Q2.3.1, Q2.2.1, Installation ＠＠ -3751,7 +3750,7 ＠＠ ＠item Specify the target location of the extra libs on the command line to ＠file{configure}, e.g. -(a)samp{./configure --site-prefixes=/build/libs i586-pc-mingw32}. +(a)samp{./configure --with-site-prefixes=/build/libs i586-pc-mingw32}. ＠end itemize ＠node Q2.3.7, Q2.3.8, Q2.3.6, Installation ＠＠ -3964,7 +3963,7 ＠＠ the top-level source directory) to read what it says about your platform. -If you compiled XEmacs using ＠samp{--use-union-type} (or the option +If you compiled XEmacs using ＠samp{--enable-union-type} (or the option ＠samp{USE_UNION_TYPE} in ＠file{config.inc} under Windows), try recompiling again without it. The union type has been known to trigger compiler errors in a number of cases. ＠＠ -3982,14 +3981,14 ＠＠ strongly recompiling your XEmacs with debugging symbols and with no optimization (e.g. with GCC use the compiler flags ＠samp{-g -O0} -- that's an "oh" followed by a zero), and with the configure options -＠samp{--debug=yes} and ＠samp{--error-checking=all}. This will make -your XEmacs run somewhat slower, but you are a lot more likely to -catch the problem earlier (closer to its source). It makes it a lot -easier to determine what's going on with a debugger. The way to -control the compiler flags is with the configuration option -＠samp{--cflags}. If you have a recent version of 21.5, you should use -＠samp{--without-optimization} in preference to directly setting -＠samp{--cflags}. +＠samp{--enable-debug=yes} and ＠samp{--enable-error-checking=all}. This +will make your XEmacs run somewhat slower, but you are a lot more likely +to catch the problem earlier (closer to its source). It makes it a lot +easier to determine what's going on with a debugger. The way to control +the compiler flags is with the configuration option +＠samp{--with-cflags}. If you have a recent version of 21.5, you should +use ＠samp{--without-optimization} in preference to directly setting +＠samp{--with-cflags}. ＠item If it's not a true crash (＠emph{i.e.}, XEmacs is hung, or a zombie ＠＠ -4145,9 +4144,9 ＠＠ If you're using a debugger to get a C stack backtrace and you're seeing stack traces with some of the innermost frames mangled, it may be due to dynamic linking. (This happens especially under Linux.) Consider -reconfiguring with ＠samp{--dynamic=no}. Also, sometimes (again under -Linux), stack backtraces of core dumps will have the frame where the -fatal signal occurred mangled; if you can obtain a stack trace while +reconfiguring with ＠samp{--with-dynamic=no}. Also, sometimes (again +under Linux), stack backtraces of core dumps will have the frame where +the fatal signal occurred mangled; if you can obtain a stack trace while running the XEmacs process under a debugger, the stack trace should be clean. ＠＠ -4292,9 +4291,9 ＠＠ complex command run from a make suite, it may be easier to attach to the process once it's running. -Under Microsoft Windows (and perhaps other operating systems), there -is another useful trick you can do if you have configured with -debugging support (configure option ＠samp{--debug} or setting +Under Microsoft Windows (and perhaps other operating systems), there is +another useful trick you can do if you have configured with debugging +support (configure option ＠samp{--with-debug} or setting ＠samp{DEBUG_XEMACS} in ＠file{nt/config.inc}). Set the environment variable ＠samp{XEMACSDEBUG} (as described above) to ＠samp{(setq debug-on-error t)}. Then, when an error occurs noninteractively, ＠＠ -6439,15 +6438,15 ＠＠ ＠uref{http://radscan.com/nas.html}. -To build XEmacs with it, use the ＠file{configure} flag ＠samp{--with-sound=nas}. +To build XEmacs with it, use the ＠file{configure} flag ＠samp{--enable--sound=nas}. ＠dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system. ＠uref{http://www.tux.org/~ricdude/EsounD.html}. -To build XEmacs with it, use the ＠file{configure} flag ＠samp{--with-sound=esd}. +To build XEmacs with it, use the ＠file{configure} flag ＠samp{--enable-sound=esd}. -You can specify support for both with a flag like ＠samp{--with-sound=nas,esd}. +You can specify support for both with a flag like ＠samp{--enable-sound=nas,esd}. ＠node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems ＠unnumberedsubsec Q5.3.4: Sunsite sounds don't play. ＠＠ -6837,7 +6836,7 ＠＠ defined by ＠code{/bin/mail}. There are various different protocols in general use, which you need to -specify using the ＠samp{--mail-locking} option to ＠file{configure}: +specify using the ＠samp{--with-mail-locking} option to ＠file{configure}: ＠table ＠samp ＠item lockf ＠＠ -7759,9 +7758,9 ＠＠ bignum ＠ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}. To configure with GNU MP, add -＠samp{--use-number-lib=gmp} +＠samp{--enable-bignum=gmp} to your invocation of ＠file{configure}. For BSD MP, use -＠samp{--use-number-lib=mp}. +＠samp{--enable-bignum=mp}. If you would like to help with bignum support, especially on BSD MP, please subscribe to the ＠uref{http://www.xemacs.org/Lists/#xemacs-beta, -- Malcolm Purvis <malcolmp(a)xemacs.org&gt;