10:41 a.m.
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>
* 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>
12:09 p.m.
On Sat, 05 Mar 2005 21:41:59 +1100, Malcolm Purvis <malcolmp(a)xemacs.org> wrote:
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?
Yes, I think that would be a _very_ good idea. I try to keep the FAQs
in sync (although they aren't at the moment).
Thanks,
Vin
--
Whoever you are, no matter how lonely,
the world offers itself to your imagination,
calls to you like the wild geese, harsh and exciting--
over and over announcing your place
in the family of things. Mary Oliver
5:22 p.m.
>>>> "Vin" == Vin Shelton
<ethersoft(a)gmail.com> writes:
Vin> On Sat, 05 Mar 2005 21:41:59 +1100, Malcolm Purvis
Vin> <malcolmp(a)xemacs.org> wrote:
> 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?
>
Vin> Yes, I think that would be a _very_ good idea. I try to keep
Vin> the FAQs in sync (although they aren't at the moment).
They were in synch up until Ben's last big comm it. I'm really
tempted to revert to that version, move the thing to general-docs, and
if Ben wants his changes in, he can check it for 21.4 compatibility,
and reapply.
What do you think?
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
4:56 a.m.
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Stephen> They were in synch up until Ben's last big comm it. I'm really
Stephen> tempted to revert to that version, move the thing to general-docs,
Stephen> and if Ben wants his changes in, he can check it for 21.4
Stephen> compatibility, and reapply.
I think that the FAQ should be in the core because we want it to be helpful to
people with really minimal setups (ie without packages). I don't think that
the 'general-docs' package is an obvious place to look for a FAQ.
I now see the point of having one version for all releases and I'll rewrite this
patch accordingly.
Malcolm
--
Malcolm Purvis <malcolmp(a)xemacs.org>
12:32 p.m.
>>>> "Malcolm" == Malcolm Purvis
<malcolmp(a)xemacs.org> writes:
Malcolm> I think that the FAQ should be in the core because we
Malcolm> want it to be helpful to people with really minimal
Malcolm> setups (ie without packages). I don't think that the
Malcolm> 'general-docs' package is an obvious place to look for a
Malcolm> FAQ.
People without packages are far beyond the help of a FAQ.
As for where people will look for the FAQ, placement in the
general-docs package won't change that: in the first few lines of the
Info directory, or on the web site. The reason the FAQ isn't already
in the general-docs package is that I haven't set up the mechanism for
distributing packages in source tarballs yet.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
5:36 a.m.
People without packages are far beyond the help of a FAQ.
??????????
This is *exactly* what the FAQ should address. *nothing* (related to XEmacs
at least) should be too far gone for the FAQ.
*PLEASE* let's put the FAQ in as obvious a place as possible, and put
pointers in the top-level README, etc. files to where the FAQ is.
As for where people will look for the FAQ, placement in the
general-docs package won't change that: in the first few
lines of the Info directory,
Not if there is no Info directory -- very common (always the case under
native Windows) when XEmacs hasn't been installed.
or on the web site.
Not if the net is down. Also, every extra step you put in the way of
figuring something out increases by 50% the chance that the new user will
give up entirely on installing the software.
ben
11:19 a.m.
>>>> "Ben" == Ben Wing <ben(a)666.com>
writes:
Ben> *PLEASE* let's put the FAQ in as obvious a place as possible,
Ben> and put pointers in the top-level README, etc. files to where
Ben> the FAQ is.
Good, you do it. I no longer have anything to do with the FAQ.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
8:21 a.m.
They were in synch up until Ben's last big comm it. I'm
really tempted to revert to that version, move the thing to
general-docs, and if Ben wants his changes in, he can check
it for 21.4 compatibility, and reapply.
BTW I try hard to make sure that every FAQ change I produce is correct for
both 21.4 and 21.5.
7246
days inactive
7248
days old
8 comments
4 participants
participants (4)
-
Ben Wing -
Malcolm Purvis -
Stephen J. Turnbull -
Vin Shelton