CVS update by crestani MODIFIED: xemacs/src ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: crestani
Date: 05/03/11 09:42:50
Modified: xemacs/src ChangeLog alloc.c
Log:
Fix KKCC backtrace C++ build
2005-03-11 Marcus Crestani <crestani(a)informatik.uni-tuebingen.de>
* alloc.c (kkcc_backtrace): Fix C++ build: do typecasts correctly.
Revision Changes Path
1.807 +4 -0 XEmacs/xemacs/src/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v
retrieving revision 1.806
retrieving revision 1.807
diff -u -r1.806 -r1.807
--- ChangeLog 2005/03/10 09:19:14 1.806
+++ ChangeLog 2005/03/11 08:42:30 1.807
＠＠ -1,3 +1,7 ＠＠
+2005-03-11 Marcus Crestani <crestani(a)informatik.uni-tuebingen.de>
+
+ * alloc.c (kkcc_backtrace): Fix C++ build: do typecasts correctly.
+
2005-03-09 Marcus Crestani <crestani(a)informatik.uni-tuebingen.de>
* database.c (berkdb_map): Add typecasts.
1.108 +5 -5 XEmacs/xemacs/src/alloc.c
Index: alloc.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/alloc.c,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -r1.107 -r1.108
--- alloc.c 2005/03/10 09:12:37 1.107
+++ alloc.c 2005/03/11 08:42:36 1.108
＠＠ -3343,18 +3343,18 ＠＠
stderr_out ("KKCC mark stack backtrace :\n");
for (i = kkcc_bt_depth - 1; i >= 0; i--)
{
+ Lisp_Object obj = wrap_pointer_1 (kkcc_bt[i].obj);
stderr_out (" [%d]", i);
- if ((((struct lrecord_header *) kkcc_bt[i].obj)->type
- >= lrecord_type_free)
- || (!LRECORDP (kkcc_bt[i].obj))
- || (!XRECORD_LHEADER_IMPLEMENTATION (kkcc_bt[i].obj)))
+ if ((XRECORD_LHEADER (obj)->type >= lrecord_type_free)
+ || (!LRECORDP (obj))
+ || (!XRECORD_LHEADER_IMPLEMENTATION (obj)))
{
stderr_out (" non Lisp Object");
}
else
{
stderr_out (" %s",
- XRECORD_LHEADER_IMPLEMENTATION (kkcc_bt[i].obj)->name);
+ XRECORD_LHEADER_IMPLEMENTATION (obj)->name);
}
stderr_out (" (addr: 0x%x, desc: 0x%x, ",
(int) kkcc_bt[i].obj,
- 1 participants
- 0 comments
CVS update by scop MODIFIED: packages/xemacs-packages/mh-e ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: scop
Date: 05/03/11 08:14:22
Modified: packages/xemacs-packages/mh-e ChangeLog mh-xemacs-icons.el
Log:
Fix toolbar initialization <1110320901.18201.461.camel(a)bobcat.mine.nu>
Revision Changes Path
1.42 +4 -0 XEmacs/packages/xemacs-packages/mh-e/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/mh-e/ChangeLog,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- ChangeLog 2004/10/04 12:07:47 1.41
+++ ChangeLog 2005/03/11 07:14:20 1.42
＠＠ -1,3 +1,7 ＠＠
+2003-07-16 Stephen J. Turnbull <stephen(a)xemacs.org>
+
+ * mh-xemacs-icons.el: Fix toolbar initialization.
+
2004-09-29 Steve Youngs <steve(a)youngs.au.com>
* Makefile (REQUIRES): Add ecrypto.
1.2 +2 -0 XEmacs/packages/xemacs-packages/mh-e/mh-xemacs-icons.el
Index: mh-xemacs-icons.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/mh-e/mh-xemacs-icons.el,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mh-xemacs-icons.el 2003/04/29 06:11:03 1.1
+++ mh-xemacs-icons.el 2005/03/11 07:14:20 1.2
＠＠ -42,6 +42,8 ＠＠
;; Avoid compiler warning
(eval-and-compile
(require 'mh-utils)
+ ;; See http://list-archive.xemacs.org/xemacs-beta/200307/msg00138.html
+ (require 'toolbar)
(defvar mh-xemacs-toolbar-folder-toolbar nil)
(defvar mh-xemacs-toolbar-letter-toolbar nil))
- 1 participants
- 0 comments
CVS update by viteno MODIFIED: xemacs ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: viteno
Date: 05/03/10 23:51:34
Modified: xemacs version.sh
Log:
Update xemacs_extra_name.
Revision Changes Path
1.1092 +1 -1 XEmacs/xemacs/version.sh
Index: version.sh
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/version.sh,v
retrieving revision 1.1091
retrieving revision 1.1092
diff -u -r1.1091 -r1.1092
--- version.sh 2005/03/09 22:51:11 1.1091
+++ version.sh 2005/03/10 22:51:32 1.1092
＠＠ -8,5 +8,5 ＠＠
infodock_major_version=4
infodock_minor_version=0
infodock_build_version=8
-xemacs_extra_name="(+CVS-20050309)"
+xemacs_extra_name="(+CVS-20050310)"
xemacs_release_date="2005-02-18"
- 1 participants
- 0 comments
CVS update by malcolmp MODIFIED: xemacs ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: malcolmp
Date: 05/03/10 12:49:01
Modified: xemacs ChangeLog INSTALL PROBLEMS
Log:
Autoconf 2.5 documentation updates.
Revision Changes Path
1.441 +6 -0 XEmacs/xemacs/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/ChangeLog,v
retrieving revision 1.440
retrieving revision 1.441
diff -u -r1.440 -r1.441
--- ChangeLog 2005/03/02 17:55:25 1.440
+++ ChangeLog 2005/03/10 11:49:00 1.441
＠＠ -1,3 +1,9 ＠＠
+2005-03-06 Malcolm Purvis <malcolmp(a)xemacs.org>
+
+ * INSTALL:
+ * PROBLEMS: Change configure arguments to the new autoconf 2.5
+ style configure.
+
2005-03-01 Aidan Kehoe <kehoea(a)parhasard.net>
* configure: Regenerated.
1.43 +94 -86 XEmacs/xemacs/INSTALL
Index: INSTALL
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/INSTALL,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- INSTALL 2004/12/07 12:52:31 1.42
+++ INSTALL 2005/03/10 11:49:00 1.43
＠＠ -36,7 +36,7 ＠＠
Verify that your users have a high enough stack limit. On some systems
such as OpenBSD and OSF/Tru64 the default is 2MB which is too low. On
-MacOS/X (Darwin), it's 512kB. See 'PROBLEMS' for details.
+MacOS/X (Darwin) before 10.3, it's 512kB. See 'PROBLEMS' for details.
Building XEmacs requires about 100 Mb of disk space (including the
XEmacs sources). Once installed, XEmacs occupies between 20 and 100
＠＠ -93,19 +93,19 ＠＠
each library does is available in the file
<ftp://ftp.xemacs.org/pub/xemacs/aux/00README.txt>.
-Use the `--site-includes' and `--site-libraries' options when building
-XEmacs to allow configure to find the external software packages. For
-your convenience these can be set together by using the
-`--with-site-prefix' option. This will set these variables as needed
+Use the `--with-site-includes' and `--with-site-libraries' options when
+building XEmacs to allow configure to find the external software
+packages. For your convenience these can be set together by using the
+`--with-site-prefixes' option. This will set these variables as needed
assuming your libraries are organised as a typical /usr tree.
If you link dynamically with external libraries, usually denoted by
-".so" (Unix), ".dll" (Windows), or ".dylib" (MacOS) file extensions,
-on some systems you may also need to add the library directories to
-the `--site-runtime-libraries' option. It is typically necessary only
+".so" (Unix), ".dll" (Windows), or ".dylib" (MacOS) file extensions, on
+some systems you may also need to add the library directories to the
+`--with-site-runtime-libraries' option. It is typically necessary only
if you link with dynamic libraries that are installed in non-standard
-directories, or if you expect some of the libraries used to build
-XEmacs to be in a different directory at run time than at build time.
+directories, or if you expect some of the libraries used to build XEmacs
+to be in a different directory at run time than at build time.
NOTE: This option has unusual semantics. ONLY libraries found in the
directories specified in this option will be used at runtime. This
＠＠ -113,13 +113,13 ＠＠
this option (perhaps excluding a very small number of standard system
library paths).
-Directories specified with `--site-libraries' are NOT automatically
-added. The rationale is that most users will not need this option,
-and this allows the builder to specify exactly the needed directories.
-Specifying unnecessary directories leads to obscure problems
-(typically startup delays) if those directories are mounted over a
-network, and the automounter configuration changes. Not all systems
-need this option; it's best to avoid using it if you can.
+Directories specified with `--with-site-libraries' are NOT automatically
+added. The rationale is that most users will not need this option, and
+this allows the builder to specify exactly the needed directories.
+Specifying unnecessary directories leads to obscure problems (typically
+startup delays) if those directories are mounted over a network, and the
+automounter configuration changes. Not all systems need this option;
+it's best to avoid using it if you can.
Dynamic linking has pros and cons. Dynamically linking 3rd party
libraries to XEmacs decreases the size of the binary, and means you
＠＠ -155,14 +155,14 ＠＠
Specifying Location of Headers and Libraries
--------------------------------------------
-The `--site-includes=DIR' and `--site-libraries=DIR' options allow you
-to specify additional places the compiler should look for include
-files and object libraries. You may specify multiple DIR's by
+The `--with-site-includes=DIR' and `--with-site-libraries=DIR' options
+allow you to specify additional places the compiler should look for
+include files and object libraries. You may specify multiple DIR's by
enclosing the list in quotes. All the external libraries you want to
use with XEmacs (e.g. xpm, wnn, ...) described later should have their
include and library directories defined using these options.
-The `--site-runtime-libraries=DIR' option specifies directories to
+The `--with-site-runtime-libraries=DIR' option specifies directories to
search for shared libraries at run time. If you use this option, you
must specify ALL of the directories containing shared libraries at run
time, including system directories. Please read the information about
＠＠ -177,31 +177,42 ＠＠
Configuring the Build Process
-----------------------------
-The `--with-gcc=PROGRAM' option specifies that the build process
-should compile XEmacs using GCC. The `--compiler' option allows you
-to specify some other compiler to be used to compile XEmacs. If
-neither option is specified, the environment variable CC is used
-instead. Otherwise the compiler will then default to 'cc'.
-
-The `--xemacs-compiler=PROGRAM' option specifies the compiler control
-program for the xemacs binary only. Other C code will be compiled
-according to the `--with-gcc' and `--compiler' options above. This is
-useful if you wish to compile XEmacs with a C++ compiler, because the
-utilities in ./lib-src cannot be compiled as C++. This option is
-primarily intended for use by the maintainers.
-
-The `--cflags=FLAGS' option specifies all of the CFLAGS the build process
-should use when compiling XEmacs, except for flags controlling warning
-generation. Otherwise the value of the environment variable CFLAGS is
-consulted. If that is also undefined, CFLAGS defaults to "-g -O" for
-gcc and "-g" for all other compilers.
+The `--with-gcc=PROGRAM' option specifies that the build process should
+compile XEmacs using GCC. The `--with-compiler' option allows you to
+specify some other compiler to be used to compile XEmacs. If neither
+option is specified, the environment variable CC is used instead.
+Otherwise the compiler will then default to 'cc'.
+
+The `--with-xemacs-compiler=PROGRAM' option specifies the compiler
+control program for the xemacs binary only. Other C code will be
+compiled according to the `--with-gcc' and `--with-compiler' options
+above. This is useful if you wish to compile XEmacs with a C++
+compiler, because the utilities in ./lib-src cannot be compiled as C++.
+This option is primarily intended for use by the maintainers.
+
+The `--with-cflags=FLAGS' option specifies all of the CFLAGS the build
+process should use when compiling XEmacs, except for flags controlling
+warning generation. Otherwise the value of the environment variable
+CFLAGS is consulted. If that is also undefined, CFLAGS defaults to "-g
+-O" for gcc and "-g" for all other compilers.
-The `--cflags_warning=FLAGS' option specifies the warnings to be
+The `--with-cflags-warning=FLAGS' option specifies the warnings to be
generated. There is normally no reason to use this flag, as XEmacs
turns on as many warnings as possible, and is still expected to build
with no, or at most a few warnings.
-The `--dynamic' option specifies that configure should try to link
+The `--with-cflags-optimization=FLAGS' option specifies the
+optimizations to be used. There is normally no reason to use this flag,
+as XEmacs will already set the maximum safe
+optimization flags appropriate for the compiler being invoked.
+
+The `--with-cflags-debugging=FLAGS' option specifies debugging
+information to be generated. There is normally no reason to use this
+flag, as XEmacs will include debugging information whenever possible
+(i.e. unless optimization is turned on and the compiler does not permit
+debugging and optimization simultaneously).
+
+The `--with-dynamic' option specifies that configure should try to link
emacs dynamically rather than statically.
You can build XEmacs for several different machine types from a single
＠＠ -257,28 +268,27 ＠＠
The `--without-xmu' option can be used if your vendor doesn't ship
the Xmu library.
-The `--with-menubars=TYPE' option allows you to specify which X
+The `--enable-menubars=TYPE' option allows you to specify which X
toolkit you wish to use for the menubar. The valid options are
`lucid', `motif' and `no'. The default is `lucid' which is a
Motif-lookalike menubar. We highly recommend its usage over the real
Motif menubar. (In fact, the Motif menubar is currently broken.) If
`no' is specified then support for menubars will not be compiled in.
-The `--with-scrollbars=TYPE' option allows you to specify which X
+The `--enable-scrollbars=TYPE' option allows you to specify which X
toolkit you wish to use for the scrollbars. The valid options are
`lucid', `motif', `athena', `athena3d', and `no'. The default is
-`lucid' which is a Motif-lookalike scrollbar. If `no' is specified
-then support for scrollbars will not be compiled in.
+`lucid' which is a Motif-lookalike scrollbar. If `no' is specified then
+support for scrollbars will not be compiled in.
-The `--with-dialogs=TYPE' option allows you to specify which X toolkit
+The `--enable-dialogs=TYPE' option allows you to specify which X toolkit
you wish to use for the dialog boxes. The valid options are `athena',
`athena3d', `motif, and `no. The `lucid' option is accepted and will
result in the `athena' toolkit being used. If the Motif toolkit can be
found the default is `motif'. Otherwise, the default is `athena'. If
-`no' is specified then support for dialog boxes will not be compiled
-in.
+`no' is specified then support for dialog boxes will not be compiled in.
-The `--with-toolbars' option allows you to enable or disable toolbar
+The `--enable-toolbars' option allows you to enable or disable toolbar
support. The default is `yes' if support for a windowing system is
included.
＠＠ -290,11 +300,11 ＠＠
X-Faces. `configure' will attempt to detect if you have the compface
library and define `--with-xface' for you.
-The `--with-database' option specifies that XEmacs should be built
+The `--enable-database' option specifies that XEmacs should be built
with simple database support. The valid options are `no' or a
comma-separated list of one or more of `dbm', `gnudbm' or `berkdb'.
`configure' will attempt to detect the necessary libraries and header
-files and define `--with-database' for you.
+files and define `--enable-database' for you.
The `--with-postgresql' option specifies that XEmacs should be built
with PostgreSQL support, linking with libpq. `configure' will attempt
＠＠ -309,23 +319,23 ＠＠
The `--with-socks' option specifies that XEmacs should be built with
SOCKS support. This requires the libsocks library.
-The `--external-widget' option specifies that XEmacs should be built
-with support for being used as a widget by other X11 applications.
+The `--enable-external-widget' option specifies that XEmacs should be
+built with support for being used as a widget by other X11 applications.
This functionality should be considered beta.
-The `--with-sound=TYPE' option specifies that XEmacs should be built
-with sound support. Native (`--with-sound=native') sound support is
+The `--enable-sound=TYPE' option specifies that XEmacs should be built
+with sound support. Native (`--enable-sound=native') sound support is
currently available only on Sun SparcStations, SGI's, HP9000s, and
systems (such as Linux) with soundcard.h. Network Audio Support (NAS)
-(`--with-sound=nas' or `--with-sound=both') is an extension to X that
-you may or may not have for your system. For NAS, you will probably
-need to provide the paths to the nas include and library directories
-to configure. If `--with-sound' is not specified, `configure' will
-attempt to determine if your configuration supports native sound and
-define --with-sound for you. If your native sound library is not in a
-standard location you can specify it with the `--native-sound-lib=LIB'
-flag. For Linux, `/dev/audio' is required for SunAudio files and
-`/dev/dsp' is required for raw data and WAVE format files.
+(`--enable-sound=nas') is an extension to X that you may or may not have
+for your system. For NAS, you will probably need to provide the paths
+to the nas include and library directories to configure. If
+`--enable-sound' is not specified, `configure' will attempt to determine
+if your configuration supports native sound and define --enable-sound
+for you. If your native sound library is not in a standard location you
+can specify it with the `--with-native-sound-lib=LIB' flag. For Linux,
+`/dev/audio' is required for SunAudio files and `/dev/dsp' is required
+for raw data and WAVE format files.
The `--with-tooltalk' option specifies that XEmacs should be built
with ToolTalk support for interconnecting with other applications.
＠＠ -351,7 +361,7 ＠＠
Internationalization Options
----------------------------
-The `--with-mule' option enables MUlti-Lingual Emacs (Mule) support,
+The `--enable-mule' option enables MUlti-Lingual Emacs (Mule) support,
needed to support non-Latin-1 (including Asian) languages. Mule
support is required for Asian language and Unicode (multibyte and wide
character) support. With the advent of the Euro and European
＠＠ -409,14 +419,14 ＠＠
Options for Developers and Special Requirements
-----------------------------------------------
-The `--rel-alloc' option can be used to either enable or disable use
-of the relocating allocator. Turning on --rel-alloc will allow XEmacs
-to return unused memory to the operating system, thereby reducing its
-memory footprint. However, it may make XEmacs runs more slowly,
+The `--with-rel-alloc' option can be used to either enable or disable
+use of the relocating allocator. Turning on --with-rel-alloc will allow
+XEmacs to return unused memory to the operating system, thereby reducing
+its memory footprint. However, it may make XEmacs runs more slowly,
especially if your system's `mmap' implementation is missing or
-inefficient. Generally, it's best to go with the default
-configuration for your system. You can tweak this based on how you
-use XEmacs, and the memory and cpu resources available on your system.
+inefficient. Generally, it's best to go with the default configuration
+for your system. You can tweak this based on how you use XEmacs, and
+the memory and cpu resources available on your system.
The `--with-system-malloc' option can be used to either enable or
disable use of the system malloc. Generally, it's best to go with the
＠＠ -427,18 +437,16 ＠＠
debugging version of malloc. Debug Malloc is not included with XEmacs
and is intended for use only by the developers. It may be obtained
from <URL:http://www.letters.com/dmalloc/>.
+
+The `--enable-debug' and `--enable-error-checking' options are primarily
+useful to the developers. `--enable-debug' incorporates code for
+performing various tests, but does not impose a speed penalty.
+`--enable-error-checking' adds additional tests to many of the commonly
+used macros, and imposes a speed penalty. Using either or both of these
+options can make bug reports more useful to the developers.
-The `--debug' and `--error-checking' options are primarily useful to
-the developers. `--debug' incorporates code for performing various
-tests, but does not impose a speed penalty. `--error-checking' adds
-additional tests to many of the commonly used macros, and imposes a
-speed penalty. Using either or both of these options can make bug
-reports more useful to the developers.
-
-The `--verbose' and `--extra-verbose' options are useful only to the
-developers. `--verbose' causes the results of all configure tests to
-be displayed. `--extra-verbose' displays additional information,
-useful for debugging `configure'.
+The `--verbose' option is useful only to the developers. It displays
+additional information, useful for debugging `configure'.
MAIL LOCKING
============
＠＠ -450,9 +458,9 ＠＠
utilities on your system, or you WILL lose mail.
Presently, XEmacs supports lockf, flock, and dot locking. Specify the
-locking method via the --mail-locking=METHOD option to configure.
-Valid values for METHOD are --mail-locking are `lockf', `flock', and
-`dot'.
+locking method via the --with-mail-locking=METHOD option to configure.
+Valid values for METHOD are --with-mail-locking are `lockf', `flock',
+and `dot'.
RUNNING CONFIGURE
=================
1.70 +35 -30 XEmacs/xemacs/PROBLEMS
Index: PROBLEMS
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/PROBLEMS,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -r1.69 -r1.70
--- PROBLEMS 2005/01/31 20:01:49 1.69
+++ PROBLEMS 2005/03/10 11:49:00 1.70
＠＠ -47,7 +47,7 ＠＠
*** How do I configure to get the buffer tabs/progress bars?
These features depend on support for "native widgets". Use the
---with-widgets option to configure. Configuration of widgets is
+--enable-widgets option to configure. Configuration of widgets is
automatic for "modern" toolkits (MS Windows, GTK, and Motif), but if
you are using Xt and the Athena widgets, you will probably want to
specify a "3d" widget set. See configure --usage, and don't forget to
＠＠ -278,7 +278,7 ＠＠
Larry Auton <lda(a)control.att.com> writes:
Beware of not specifying
- --with-dialogs=athena
+ --enable-dialogs=athena
if it builds with the motif dialogs [boom!] you're a dead man.
＠＠ -301,7 +301,7 ＠＠
defined in string.h - basically anything the compiler knows how to
inline.)
-*** On AIX 4.3, you must specify --with-dialogs=athena with configure
+*** On AIX 4.3, you must specify --enable-dialogs=athena with configure
*** The libXt shipped with AIX 4.3 up to 4.3.2 is broken. This causes
xemacs -nw to fail in various ways. The official APAR is this:
＠＠ -369,7 +369,7 ＠＠
are caused by using GNU ld. There are several workarounds available:
In XEmacs 21.2 or later, configure using the new portable dumper
-(--pdump).
+(--enable-pdump).
Alternatively, you can link using the Sun version of ld, which is
normally held in /usr/ccs/bin. This can be done by one of:
＠＠ -536,9 +536,9 ＠＠
passes the result to something that things foo_struct is a bit bigger,
trashing memory....
-Here's typical crash backtrace. With --pdump, this occurs usually at
-startup under X windows and xemacs -nw at least starts, while without
---pdump a similar crash is observed during build.
+Here's typical crash backtrace. With --enable-pdump, this occurs
+usually at startup under X windows and xemacs -nw at least starts, while
+without --pdump a similar crash is observed during build.
#0 0x0fa460b8 in kill () at regcomp.c:637
637 regcomp.c: No such file or directory.
＠＠ -559,7 +559,7 ＠＠
The MIPSpro Compiler (at least version 7.2.1) can't seem to handle the
union type properly, and fails to compile src/glyphs.c. To avoid this
-problem, always build ---use-union-type=no (but that's the default, so
+problem, always build --enable-union-type=no (but that's the default, so
you should only see this problem if you're an XEmacs maintainer).
*** Linking with -rpath on IRIX.
＠＠ -569,9 +569,9 ＠＠
1. The ld in IRIX 5.3 ignores all but the last -rpath
spec, so the patched configure spits out a warning
- if --x-libraries or --site-runtime-libraries are
+ if --x-libraries or --with-site-runtime-libraries are
specified under irix 5.x, and it only adds -rpath
- entries for the --site-runtime-libraries. This bug was
+ entries for the --with-site-runtime-libraries. This bug was
fixed sometime between 5.3 and 6.2.
2. IRIX gcc 2.7.2 doesn't accept -rpath directly, so
＠＠ -580,8 +580,8 ＠＠
${CC-cc} $CFLAGS $LDFLAGS ...
rather than quoting $LDFLAGS with prefix-args, like
src/Makefile does. So if you specify --x-libraries
- or --site-runtime-libraries, you must use --use-gcc=no,
- or configure will fail.
+ or --with-site-runtime-libraries, you must use
+ --with--gcc=no, or configure will fail.
*** On Irix 6.3, the SGI ld quits with segmentation fault when linking temacs
＠＠ -686,16 +686,18 ＠＠
configuration for COFF with:
/path_to_xemacs_source/configure --with-gcc=no \
- --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
- --with-xpm --with-xface --with-sound=nas
+ --with-site-includes=/usr/local/include \
+ --with-site-libraries=/usr/local/lib \
+ --with-xpm --with-xface --enable-sound=nas
This version now supports ELF builds. I highly recommend this to
reduce the in-core footprint of XEmacs. This is now how I compile
all my test releases. Build it like this:
/path_to_XEmacs_source/configure --with-gcc=no \
- --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
- --with-xpm --with-xface --with-sound=nas --dynamic
+ --with-site-includes=/usr/local/include
+ --with-site-libraries=/usr/local/lib \
+ --with-xpm --with-xface --enable-sound=nas --with-dynamic
The compiler known as icc [ supplied with the OpenServer 5 Development
System ] generates a working binary, but it takes forever to generate
＠＠ -706,8 +708,10 ＠＠
The way I handle the build procedure is:
/path_to_XEmacs_source/configure --with-gcc=no \
- --site-includes=/usr/local/include --site-libraries=/usr/local/lib \
- --with-xpm --with-xface --with-sound=nas --dynamic --compiler="icc"
+ --with-site-includes=/usr/local/include \
+ --with-site-libraries=/usr/local/lib \
+ --with-xpm --with-xface --enable-sound=nas --with-dynamic \
+ --with-compiler="icc"
NOTE I have the xpm, xface, and audio libraries and includes in
/usr/local/lib, /usr/local/include. If you don't have these,
＠＠ -1361,8 +1365,8 ＠＠
undefined symbols.
The only known case in which this happens is if you are using gcc, you
-configured with --error-checking=all and --with-modules, and you
-compiled with no optimization. If you encounter this problem in any
+configured with --enable-error-checking=all and --enable-modules, and
+you compiled with no optimization. If you encounter this problem in any
other situation, please inform xemacs-beta(a)xemacs.org.
This problem stems from a gcc bug. With no optimization, functions
＠＠ -1601,18 +1605,19 ＠＠
make-frame(nil #<x-device on ":0.0" 0x2558>)
-somewhere near the top. The problem is due to an improvement in GNU
-ld that sorts the ELF reloc sections in the executable, giving
-dramatic speedups in startup for large executables. It also confuses
-the traditional unexec code in XEmacs, leading to the core dump. The
-solution is to use the --pdump or --ldflags='-z nocombreloc' options
-to configure. Recent 21.4 and 12.5 autodetect this in configure.
+somewhere near the top. The problem is due to an improvement in GNU ld
+that sorts the ELF reloc sections in the executable, giving dramatic
+speedups in startup for large executables. It also confuses the
+traditional unexec code in XEmacs, leading to the core dump. The
+solution is to use the --enable-pdump or --with-ldflags='-z nocombreloc'
+options to configure. Recent 21.4 and 12.5 autodetect this in
+configure.
Red Hat and SuSE (at least) distributed a prerelease version of ld
(versions around 2.11.90.x.y) where autodetection is impossible. The
recommended procedure is to upgrade to binutils >= 2.12 and rerun
-configure. Otherwise you must apply the flags by hand. --pdump is
-recommended.
+configure. Otherwise you must apply the flags by hand. --enable-pdump
+is recommended.
*** I want XEmacs to use the Alt key, not the XXX key, for Meta commands
＠＠ -1774,8 +1779,8 ＠＠
SGI ships a really old Xpm library in /usr/lib which does not work at
all well with XEmacs. The solution is to install your own copy of the
-latest version of Xpm somewhere and then use the --site-includes and
---site-libraries flags to tell configure where to find it.
+latest version of Xpm somewhere and then use the --with-site-includes
+and --with-site-libraries flags to tell configure where to find it.
*** Trouble using ptys on IRIX, or running out of ptys.
- 1 participants
- 0 comments
CVS update by malcolmp MODIFIED: xemacs/man/internals ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: malcolmp
Date: 05/03/10 12:44:24
Modified: xemacs/man/internals internals.texi
Log:
Autoconf 2.5 documentation updates.
Revision Changes Path
1.292 +7 -0 XEmacs/xemacs/man/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/ChangeLog,v
retrieving revision 1.291
retrieving revision 1.292
diff -u -r1.291 -r1.292
--- ChangeLog 2005/03/09 05:36:28 1.291
+++ ChangeLog 2005/03/10 11:44:17 1.292
＠＠ -1,3 +1,10 ＠＠
+2005-03-05 Malcolm Purvis <malcolmp(a)xemacs.org>
+
+ * beta.texi : Change configure arguments to the new autoconf 2.5
+ style configure.
+ * internals/internals.texi (The Build Configuration System): Fill
+ out the details.
+
2005-01-19 Aidan Kehoe <kehoea(a)parhasard.net>
* lispref/mule.texi (CCL Example): Detail an implementation of the
1.3 +42 -35 XEmacs/xemacs/man/beta.texi
Index: beta.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/beta.texi,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- beta.texi 2005/02/03 06:14:40 1.2
+++ beta.texi 2005/03/10 11:44:17 1.3
＠＠ -377,10 +377,9 ＠＠
It's a good idea to use
＠example
---extra-verbose
---debug
---memory-usage-stats
---error-checking=all
+--enable-debug
+--enable-memory-usage-stats
+--enable-error-checking=all
＠end example
These turn on extra debugging info and checks. The last one in particular
＠＠ -392,10 +391,10 ＠＠
You should also strongly consider
＠example
---with-mule
---use-pkcc
---pdump
---with-clash-detection
+--enable-mule
+--enable-kkcc
+--enable-pdump
+--enable-clash-detection
--with-wmcommand
--with-xfs
＠end example
＠＠ -406,8 +405,8 ＠＠
If you have gcc, consider using
＠example
---compiler=gcc
---xemacs-compiler=g++
+--with-compiler=gcc
+--with-xemacs-compiler=g++
＠end example
This will compile XEmacs using g++, which will turn on a lot of additional
＠＠ -418,7 +417,7 ＠＠
line like
＠example
---package-path=~/.xemacs::/xemacs/site-packages:/xemacs/xemacs-packages:/xemacs/mule-packages
+--with-package-path=~/.xemacs::/xemacs/site-packages:/xemacs/xemacs-packages:/xemacs/mule-packages
＠end example
＠item
＠＠ -435,12 +434,12 ＠＠
populate your build directory.
＠item
-Use --site-prefixes (or --site-includes and --site-libraries) if you have
-some packages that XEmacs can compile with that are located in an unusual
-place. For example:
+Use --with-site-prefixes (or --with-site-includes and
+---with-site-libraries) if you have some packages that XEmacs can
+compile with that are located in an unusual place. For example:
＠example
---site-prefixes=/usr/local/pgsql:/usr/local/BerkeleyDB.4.1
+--with-site-prefixes=/usr/local/pgsql:/usr/local/BerkeleyDB.4.1
＠end example
＠item
＠＠ -455,33 +454,41 ＠＠
the command ＠kbd{M-x describe-installation RET}).
＠example
-uname -a: Linux eicq 2.4.20 #1 Wed Dec 18 02:14:29 EST 2002 i586 unknown
+uname -a: Darwin laptop.local 7.7.0 Darwin Kernel Version 7.7.0: Sun Nov 7 16:06:51 PST 2004; root:xnu/xnu-517.9.5.obj~1/RELEASE_PPC Power Macintosh powerpc
-./configure '--extra-verbose' '--site-prefixes=/usr/local/pgsql:/usr/local/BerkeleyDB.4.1' '--dynamic=yes' '--with-gtk=no' '--with-gnome=no' '--with-toolbars' '--with-wmcommand' '--with-athena=next' '--with-menubars=lucid' '--with-scrollbars=athena' '--with-dialogs=athena' '--with-widgets=athena' '--with-gif' '--with-sound=native,noesd' '--with-site-lisp=no' '--with-site-modules' '--pdump' '--with-mule' '--with-xfs' '--debug' '--error-checking=all' '--memory-usage-stats' '--use-kkcc' '--with-clash-detection'
+./configure '--with-site-prefixes=/sw' '--without-ldap' '--with-dynamic=yes' '--with-gtk=no' '--with-gnome=no' '--enable-toolbars' '--with-wmcommand' '--with-athena=3d' '--enable-menubars=lucid' '--enable-scrollbars=athena' '--enable-dialogs=athena' '--enable-widgets=athena' '--with-gif' '--enable-sound=native,noesd' '--with-site-lisp=no' '--with-site-modules' '--enable-pdump' '--enable-mule' '--with-xfs' '--enable-debug' '--enable-error-checking=all' '--enable-memory-usage-stats' '--enable-kkcc' '--enable-clash-detection'
-XEmacs 21.5-b10 "burdock" (+CVS-20030131) configured for `i586-pc-linux'.
+XEmacs 21.5-b19 "chives" (+CVS-20050226) configured for `powerpc-apple-darwin7.7.0'.
+ WARNING: --------------------------------------------------------------
+ WARNING: This was produced from a new autoconf-2.5 based configuration.
+ WARNING: If this configuration seems buggy then copy etc/configure-2.13
+ WARNING: to configure and try again. Also please report the bug.
+ WARNING: --------------------------------------------------------------
-Compilation / Installation:
+Compilation Environment and Installation Defaults:
Source code location: /usr/local/src/xemacs
Installation prefix: /usr/local
- Additional prefixes: /usr/local/pgsql /usr/local/BerkeleyDB.4.1
- Operating system description file: `s/linux.h'
- Machine description file: `m/intel386.h'
- Compiler: gcc -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wundef -Wstrict-prototypes -Wshadow -Wmissing-declarations -O1 -ggdb3 -Wall -Wchar-subscripts -Wunused -Wundef -Wshadow -Wsign-compare -Wmissing-declarations -march=k6
+ Additional prefixes: /sw
+ Operating system description file: `s/darwin.h'
+ Machine description file: `m/powerpc.h'
+ Compiler version: gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1671)
+ - GCC specs file: /usr/libexec/gcc/darwin/ppc/3.3/specs
+ - Compiler command: gcc -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wpointer-arith -Wunused-parameter -g
+ libc version:
Relocating allocator for buffers: no
- GNU version of malloc: yes
- - Using Doug Lea's new malloc from the GNU C Library.
+ GNU version of malloc: no
+ - The GNU allocators don't work with this system configuration.
Window System:
Compiling in support for the X window system:
- - X Windows headers location: /usr/X11/include
- - X Windows libraries location: /usr/X11/lib
+ - X Windows headers location: /usr/X11R6/include
+ - X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- - Athena headers location: X11/neXtaw
- - Athena library to link: neXtaw
+ - Athena headers location: X11/Xaw3d
+ - Athena library to link: Xaw3d
Using Lucid menubars.
Using Athena scrollbars.
Using Athena dialog boxes.
＠＠ -489,7 +496,6 ＠＠
TTY:
Compiling in support for ncurses.
- Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
＠＠ -500,12 +506,12 ＠＠
Compiling in support for X-Face message headers.
Sound:
- Compiling in support for sound (native).
Databases:
Compiling in support for Berkeley database.
+ Compiling in support for GNU DBM.
Compiling in support for PostgreSQL.
- - Using PostgreSQL header file: libpq-fe.h
+ - Using PostgreSQL header file: postgresql/libpq-fe.h
- Using PostgreSQL V7 bindings.
Internationalization:
＠＠ -515,7 +521,7 ＠＠
- Using XFontSet to provide bilingual menubar.
Mail:
- Compiling in support for "dot-locking" mail spool file locking method.
+ Compiling in support for "file" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
＠＠ -523,10 +529,11 ＠＠
Using the new GC algorithms.
Using the new portable dumper.
Compiling in support for extra debugging code.
- WARNING: WARNING: Compiling in support for runtime error checking.
+ Compiling in support for runtime error checking.
+ WARNING: ---------------------------------------------------------
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
- WARNING:
+ WARNING: ---------------------------------------------------------
＠end example
＠end enumerate
1.62 +134 -92 XEmacs/xemacs/man/internals/internals.texi
Index: internals.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/internals/internals.texi,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -r1.61 -r1.62
--- internals.texi 2005/03/09 05:36:35 1.61
+++ internals.texi 2005/03/10 11:44:22 1.62
＠＠ -4159,12 +4159,11 ＠＠
＠cindex build configuration
＠cindex configuration, build
-＠strong{Please write this node!} ＠c ####
+XEmacs makes extensive use of the external features provided by the
+system it is running on. Determining which features are present and
+where they are located is the responsibility of the build configuration
+system.
-This node should describe XEmacs-specific techniques and idioms in the
-configuration system. A particular example is the set of ＠samp{XE_}
-macros in ＠file{configure.in} and ＠file{configure.ac}.
-
＠menu
* The version.sh Script::
* Adding Configurable Features::
＠＠ -4270,12 +4269,18 ＠＠
＠cindex adding configurable features
＠cindex configurable features, adding
＠cindex features, adding configurable
-
-Adding a configurable feature requires at least adding an option to the
-＠file{configure} script and a macro definition to ＠file{src/config.h.in}
-(＠pxref{The configure Script}), and often changes to Makefile precursors
-(＠pxref{The Makefile Precursors}).
+Adding a configurable feature requires at the very least adding an
+option to the ＠file{configure} script and a macro definition to
+(a)file{src/config.h.in} (＠pxref{The configure Script}), and often changes
+to Makefile precursors (＠pxref{The Makefile Precursors}).
+
+Be prepared for the feature to be absent (even if you think that is
+always present for a particular OS release) and work with
+＠code{--with-site-prefixes} to handle libraries and headers that are in
+unusual locations. There is no end to the strange ways in which systems
+can be configured and XEmacs is expected to cope with anything thrown at
+it.
＠node The configure Script, The Makefile Precursors, Adding Configurable Features, The Build Configuration System
＠＠ -4286,26 +4291,37 ＠＠
At the heart of the XEmacs build configuration system is the
＠file{configure} script. This beast is maintained using the Autoconf
system, which is a truly terrifying monstrosity based on a fundamentally
-flawed programming model (extensive use of macros), with an
-implementation about which I've never heard a nice word (GNU ＠file{m4}),
-used to string together a large set of ＠emph{ad hoc} tests, to implement
-a configuration language with conventions that are unimportant in simple
-cases and counterintuitive when things get complicated. If that doesn't
-scare you off, Welcome! I think you're ready to become a configure
-hacker! (But be prepared for things to go downhill from here.)
+flawed programming model (extensive use of macros), with an unpleasant
+implementation (GNU ＠file{m4}), used to string together a large set of
+＠emph{ad hoc} tests, to implement a configuration language with
+conventions that are unimportant in simple cases and counterintuitive
+when things get complicated. If that doesn't scare you off, Welcome! I
+think you're ready to become a configure hacker! (But be prepared for
+things to go downhill from here.)
+
+Unless you plan to develop autoconf macros, much of this complexity can
+be removed by following the following rule:
+
+＠quotation
+Always quote (ie surround with ＠samp{[]}) every argument to every
+macro. This includes macros that appear in the argument list of other
+macros.
+＠end quotation
+
+If this rule is followed and the macro produces incorrect results then
+the macro is buggy.
＠file{configure} is, of course, is written in POSIX shell language, and
-autogenerated from a precursor (see? the first step was a doozy!)
-Currently that precursor is called ＠file{configure.ac}, but in the
-previous generation it was called ＠file{configure.in}. As of February
-2005, ＠file{configure.ac} is used in the development mainline, but
-because the semantics of many predefined macros changed drastically
-between ＠file{autoconf} 2.13 and ＠file{autoconf} 2.50 (why not ``3.0''?
-you got me), the XEmacs Project chose to stick with the devil it knew
-for the stable line of XEmacs 21.4 releases.
+autogenerated from a precursor. As of March 2005 on the mainline the
+precursor is called ＠file{configure.ac} and it is built using
+＠code{autoconf} 2.59. Prior to that, and with XEmacs 21.4 and earlier
+it was called ＠file{configure.in} and build using ＠code{autoconf} 2.13.
+＠code{autoconf} 2.5X is not completely backward compatible with
+＠code{autoconf} 2.13 so the XEmacs Project chose to stick with the devil
+it knew for the stable line of XEmacs 21.4 releases.
-One reason for worrying about the semantic changes is the fact that
-XEmacs uses a lot of homebrew code, including ＠file{m4} macros, to
+One reason for worrying about the level of compatibility is the fact
+that XEmacs uses a lot of homebrew code, including ＠file{m4} macros, to
implement special features in its ＠file{configure} script. Here are
some of the important features:
＠＠ -4326,85 +4342,116 ＠＠
＠c #### ＠var{}-ize the formal parameters of these functions?
＠table ＠code
＠item USAGE_ERROR(string)
-prints a usage error and dies
+Prints a usage error and dies.
＠item PRINT_VAR(var var ...)
-prints values of shell variables
+Prints the name and value of the list of shell variables.
-＠item XE_ADD_OBJS(foo.o ...)
-＠strong{#### Please document me!}
+＠item XE_ADD_OBJS(foo.o)
+Appends the argument to the variable ＠code{extra_objs}. This variable
+goes to make up part of the link command line. If the command line
+argument ＠code{--verbose} is supplied a message is printed out.
＠item XE_APPEND(value, varname)
-＠strong{#### Please document me!}
+Append the value (separated by a space) to the shell variable
+＠var{varname}. ＠var{varname} should not be prefixed with a ＠samp{$}.
+If the command line argument ＠code{--verbose} is supplied a message is
+printed out.
＠item XE_PREPEND(value, varname)
-＠strong{#### Please document me!}
+Prepend the value (separated by a space) to the shell variable
+＠var{varname}. ＠var{varname} should not be prefixed with a ＠samp{$}.
+If the command line argument ＠code{--verbose} is supplied a message is
+printed out.
＠item XE_DIE(message)
-used for situations that can't lead to a successful build, such as
+Used for situations that can't lead to a successful build, such as
missing include files or conflicts between requested features.
＠item XE_CHECK_FEATURE_DEPENDENCY(feature1, feature2)
-＠strong{#### Please document me!}
+＠code{--with-＠var{feature1}} requires that ＠code{--with-＠var{feature2}}
+be also set and will die if the latter is not specified.
＠item XE_STRIP_4TH_COMPONENT(var)
-＠strong{#### Please document me!}
+Converts the four part system name (eg ＠code{i986-pc-linux-gnu}) in
+＠var{var} to a three part names (eg ＠code{i986-pc-linux}).
＠item CANONICALIZE_PATH(varname)
-＠strong{#### Please document me!}
+Strips automount brokenness from the path in ＠var{varname}.
＠item XE_PROTECT_LINKER_FLAGS(shell_var)
-＠strong{#### Please document me!}
+Wrap the command line arguments in ＠var{shell_var} with suitable
+incantations to ensure that the compiler front end passes them to the
+linker. Currently the magic is added only for gcc.
＠item COLON_TO_SPACE(path)
-Allow use of either ＠samp{:} or spaces for lists of directories.
+Converts a colon separated list of paths into a space separated list of paths.
＠item XE_ADD_RUNPATH_DIR(directory)
-＠strong{#### Please document me!}
+Internal function used by ＠code{XE_COMPUTE_RUNPATH}.
＠item XE_COMPUTE_RUNPATH()
-＠strong{#### Please document me!}
+Calculate the appropriate dynamic library run path for XEmacs and the
+value to the shell variable ＠code{ld_switch_run}.
＠item XE_SPACE(var, words)
-＠strong{#### Please document me!}
+Append to ＠code{var} a space separated list of ＠code{words}.
＠item XE_SHLIB_STUFF
-See ＠file{aclocal.m4}.
+Generate the appropriate shared library support black magic. This is
+implemented in the file ＠file{aclocal.m4}.
＠end table
＠heading XEmacs keyword option support
A ＠dfn{keyword} option is one that accepts one of a number of
-pre-defined values (if support for sets of values is needed, see
+pre-defined values (if support for sets of values is needed, x1see
``complex options'' below). For example,
＠samp{--with-mail-locking=flock}.
-Keyword options use expanded forms of ＠samp{AC_ARG_[WITH|ENABLE]} called
-＠samp{XE_KEYWORD_ARG_[WITH|ENABLE]}, both taking 5 parameters. The
-first 4 parameters of these macros are the same as original macros with
-the exception that all four parameters are ＠strong{required}. The
-＠var{action-if-true} code is run after the argument list has been
-parsed.
+Keyword options are defined with expanded forms of
+＠samp{AC_ARG_[WITH|ENABLE]} called ＠samp{XE_KEYWORD_ARG_[WITH|ENABLE]},
+both taking 5 parameters. The first 4 parameters of these macros are
+the same as original macros with the exception that all four parameters
+are ＠strong{required}. The ＠var{action-if-true} code is run after the
+argument list has been parsed.
The 5th parameter is a list of supported keywords. The whole list must
-be quoted but the individual keywords should not.
+be quoted but the individual keywords should not. Here is how the
+＠samp{mail-locking} flag is defined:
+
+＠example
+XE_KEYWORD_ARG_WITH([mail-locking],
+ AC_HELP_STRING([--with-mail-locking],[Specify the locking to be
+ used by movemail to prevent concurrent updates
+ of mail spool files. Valid types are `lockf',
+ `flock', `dot', `locking' or `mmdf'.]),
+ [],
+ [],
+ [lockf,flock,file,locking,mmdf,pop])
+＠end example
+(Note that the help string will be reformatted by ＠file{autoconf} so
+that all whitespace is first compressed to a single space, then folded
+to appear in the right-hand column as above. Thus the help string may
+appear differently when ＠code{./configure --help} is invoked.)
+
If the option value is a not a valid keyword then an error message is
generated, otherwise the value is left untouched.
This support is implemented via the following ＠file{GNU m4} macros.
-Macros labelled ＠dfn{internal} are not expected to be used by
+Macros labeled ＠dfn{internal} are not expected to be used by
＠file{configure.ac} programmers; they are part of the implementation of
higher-level features.
＠table ＠code
＠item XE_KEYWORD_ARG_WITH(package, help-string, action-if-true, action-if-false, [keyword1, keyword2, ....])
-Expanded version of ＠samp{AC_ARG_WITH} for keyword options. All the
+Expanded version of ＠code{AC_ARG_WITH} for keyword options. All the
parameters are required. The last argument is a comma-separated list of
supported keywords, ＠file{m4}-quoted with ＠samp{[]}.
＠item XE_KEYWORD_ARG_ENABLE(feature, help-string, action-if-true, action-if-false, [keyword1, keyword2, ....])
-Expanded version of ＠samp{AC_ARG_ENABLE} for keyword options. All the
+Expanded version of ＠code{AC_ARG_ENABLE} for keyword options. All the
parameters are required. The last argument is a comma-separated list of
supported keywords, ＠file{m4}-quoted with ＠samp{[]}.
＠＠ -4413,26 +4460,25 ＠＠
found then an error is generated.
＠item XE_KEYWORD(keyword)
-Internal macro to declare an option value.
+Internal macro to convert the keyword list into the various forms needed
+by ＠code{XE_PARSE_KEYWORD_OPTION}.
＠end table
＠heading XEmacs complex option support
A ＠dfn{complex option} is one that takes a number of related values, as
-a set. For example, we might use "--with-xft=all,nomenubars" for
-compatibility with XFontSet i18n of menubars. (The example is
-contrived, Xft looks much better than XFS.) Processing such an option
-requires a number of auxiliary variables.
-
-Complex options use expanded forms of ＠samp{AC_ARG_[WITH|ENABLE]} called
-＠samp{XE_COMPLEX_ARG_[WITH|ENABLE]}, both taking 5 parameters. The
-first 4 parameters of these macros are the same as original macros with
-the exception that all four parameters are ＠strong{required}. The
-＠var{action-if-true} code is run after the argument list has been
-parsed.
+a set. For example, we might use ＠code{--with-sound=native,nas} to play
+sounds using the native libraries and via NAS.
+
+Complex options are defined with expanded forms of
+＠samp{AC_ARG_[WITH|ENABLE]} called ＠samp{XE_COMPLEX_ARG_[WITH|ENABLE]},
+both taking 5 parameters. The first 4 parameters of these macros are
+the same as original macros with the exception that all four parameters
+are ＠strong{required}. The ＠var{action-if-true} code is run after the
+argument list has been parsed.
-The 5th parameter is a list of ＠samp{XE_COMPLEX_OPTION} macro calls that
+The 5th parameter is a list of ＠code{XE_COMPLEX_OPTION} macro calls that
define the valid components and their default values. The list must be
quoted but the individual macro calls should not. Here is how the
＠samp{sound} flag is defined:
＠＠ -4454,23 +4500,18 ＠＠
XE_COMPLEX_OPTION([esd],[no])])
＠end example
-(Note that the help string will be reformatted by ＠file{autoconf} so
-that all whitespace is first compressed to a single space, then folded
-to appear in the right-hand column as above. Thus the help string may
-appear differently when ＠code{./configure --help} is invoked.)
-
＠c #### verify for INSTALL and xemacs Texinfo.
-Each component is interpreted as a separate feature to be enabled or
+Each option is interpreted as a separate feature to be enabled or
disabled. As usual, the distinction between ``with'' and ``enable'' is
that ``with'' features require specific support from the system, usually
one or more optional libraries, and ``enable'' features are supported
entirely by code in XEmacs, but the user might want to switch it off for
some reason. Option values are stored in the variables
-＠samp{with_＠var{package}_＠var{component}} or
-＠samp{enable_＠var{feature}_＠var{component}} (＠i{e.g.}
-＠samp{with_xft_menubars}).
+＠code{with_＠var{package}_＠var{component}} or
+＠code{enable_＠var{feature}_＠var{component}} (＠i{e.g.}
+＠code{enable_sound_native}).
-The user of ＠file{configure} specifies the configuration by providing a
+The user of ＠code{configure} specifies the configuration by providing a
list of components. The special components ＠samp{all} and ＠samp{none}
may occur first in the list, setting the defaults for all components to
＠samp{yes} or ＠samp{no} respectively.
＠＠ -4482,7 +4523,7 ＠＠
value can also be the null string ＠samp{""}, usually meaning that
＠file{configure} will attempt to find support for the feature on the
system, and will enable the configuration if it is available. Sometimes
-the null string means that ＠file{configure}'s default is
+the null string means that ＠code{configure}'s default is
system-dependent. (This usage is not consistent, and depends on the
implementation of the feature detector rather than the argument parser.)
Users cannot specify the null string for an individual component from
＠＠ -4494,7 +4535,7 ＠＠
library which may or may not be supported by multiple components of
XEmacs, as exemplified by Xft. This latter usage may be more common
during development of a feature. Perhaps specialized APIs should be
-provided, see comment on ＠samp{XE_COMPLEX_OPTION_HELP_STRING} below.
+provided, see comment on ＠code{XE_COMPLEX_OPTION_HELP_STRING} below.
＠table ＠code
＠item XE_COMPLEX_OPTION(option, yesno)
＠＠ -4513,11 +4554,11 ＠＠
the API may be enhanced to deal with this in the future.
＠item XE_COMPLEX_ARG_WITH(PACKAGE, HELP-STRING, ACTION-IF-TRUE, ACTION-IF-FALSE, [XE_COMPLEX_OPTION(a,yes), ....])
-Extended version of ＠samp{AC_ARG_WITH} for complex options. All the
+Extended version of ＠code{AC_ARG_WITH} for complex options. All the
parameters are required.
＠item XE_COMPLEX_ARG_ENABLE(FEATURE, HELP-STRING, ACTION-IF-TRUE, ACTION-IF-FALSE, [XE_COMPLEX_OPTION(a,yes), ....])
-Expanded version of ＠samp{AC_ARG_ENABLE} for complex options. All the
+Expanded version of ＠code{AC_ARG_ENABLE} for complex options. All the
parameters are required.
＠item XE_EXPAND_COMPLEX_OPTION(prefix, component, yesno)
＠＠ -4548,21 +4589,22 ＠＠
＠cindex Makefile precursors
＠cindex precursors, Makefile
-＠strong{Please write this node!} ＠c ####
-
-As in other programs using a ＠file{configure} program, XEmacs's
-Makefiles are not written, they are generated. The ＠file{configure}
-program uses Makefile precursors, or templates, to generate the actual
-Makefiles. In fact, it is a multistage process. The developer changes
-the file ＠file{Makefile.in.in}, then ＠file{configure} first generates an
+As with other ＠code{autoconf} based programs, XEmacs's Makefiles are not
+written, they are generated. The ＠code{configure} program uses Makefile
+precursors, or templates, to generate the actual Makefiles. Unlike
+other programs this is a multistage process. The developer changes the
+file ＠file{Makefile.in.in}, then ＠code{configure} first generates an
intermediate file ＠file{Makefile.in}, and finally produces a portable
-Makefile called ＠file{Makefile}, and a Makefile optimized for ＠file{GNU
+Makefile called ＠file{Makefile}, and a Makefile optimized for ＠code{GNU
make} called ＠file{GNUmakefile}.
-
-This node describes XEmacs-specific techniques and idioms used in the
-(a)file{Makefile.in.in} files.
+(a)file{Makefile.in.in} is run through the C preprocessor as part of this
+process. This means that common files can be included and conditional
+construction of the Makefile can occur. When ＠file{GNUmakefile} is
+being produced ＠code{USE_GNU_MAKE} is defined.
+Comments in ＠file{Makefile.in.in} must start with ＠samp{##} to avoid
+confusing the preprocessor.
＠node Rules When Writing New C Code, Regression Testing XEmacs, The Build Configuration System, Top
＠chapter Rules When Writing New C Code
- 1 participants
- 0 comments
CVS update by crestani MODIFIED: xemacs/src ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: crestani
Date: 05/03/10 10:19:18
Modified: xemacs/src ChangeLog database.c
Log:
Add missing typecasts.
2005-03-09 Marcus Crestani <crestani(a)informatik.uni-tuebingen.de>
* database.c (berkdb_map): Add typecasts.
Revision Changes Path
1.806 +4 -0 XEmacs/xemacs/src/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v
retrieving revision 1.805
retrieving revision 1.806
diff -u -r1.805 -r1.806
--- ChangeLog 2005/03/10 09:12:36 1.805
+++ ChangeLog 2005/03/10 09:19:14 1.806
＠＠ -1,3 +1,7 ＠＠
+2005-03-09 Marcus Crestani <crestani(a)informatik.uni-tuebingen.de>
+
+ * database.c (berkdb_map): Add typecasts.
+
2005-03-01 Marcus Crestani <crestani(a)informatik.uni-tuebingen.de>
* alloc.c: Add functionality for backtracing the KKCC mark
1.34 +2 -2 XEmacs/xemacs/src/database.c
Index: database.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/database.c,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- database.c 2005/01/21 20:07:06 1.33
+++ database.c 2005/03/10 09:19:16 1.34
＠＠ -510,9 +510,9 ＠＠
status == 0;
status = dbp->seq (dbp, &keydatum, &valdatum, R_NEXT))
{
- key = make_ext_string (keydatum.data, keydatum.size,
+ key = make_ext_string ((const Extbyte *) keydatum.data, keydatum.size,
db->coding_system);
- val = make_ext_string (valdatum.data, valdatum.size,
+ val = make_ext_string ((const Extbyte *) valdatum.data, valdatum.size,
db->coding_system);
call2 (func, key, val);
}
- 1 participants
- 0 comments
CVS update by crestani MODIFIED: xemacs/src, profile.c ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: crestani
Date: 05/03/10 10:12:41
Modified: xemacs/src ChangeLog alloc.c data.c elhash.c lisp.h
profile.c
Log:
KKCC backtrace.
2005-03-01 Marcus Crestani <crestani(a)informatik.uni-tuebingen.de>
* alloc.c: Add functionality for backtracing the KKCC mark
algorithm.
* alloc.c (kkcc_backtrace): New.
* alloc.c (kkcc_bt_push): New.
* alloc.c (kkcc_gc_stack_push):
* alloc.c (kkcc_gc_stack_push_lisp_object):
* alloc.c (mark_object_maybe_checking_free):
* alloc.c (mark_struct_contents):
* alloc.c (kkcc_marking):
* alloc.c (mark_object):
* data.c (finish_marking_weak_lists):
* data.c (continue_marking_ephemerons):
* data.c (finish_marking_ephemerons):
* elhash.c (MARK_OBJ):
* lisp.h:
* profile.c (mark_profiling_info_maphash): Add level (current
depth of mark tree) and pos (position within description) as
additional arguments to KKCC mark functions.
Revision Changes Path
1.805 +21 -0 XEmacs/xemacs/src/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v
retrieving revision 1.804
retrieving revision 1.805
diff -u -r1.804 -r1.805
--- ChangeLog 2005/03/10 09:05:44 1.804
+++ ChangeLog 2005/03/10 09:12:36 1.805
＠＠ -1,3 +1,24 ＠＠
+2005-03-01 Marcus Crestani <crestani(a)informatik.uni-tuebingen.de>
+
+ * alloc.c: Add functionality for backtracing the KKCC mark
+ algorithm.
+ * alloc.c (kkcc_backtrace): New.
+ * alloc.c (kkcc_bt_push): New.
+ * alloc.c (kkcc_gc_stack_push):
+ * alloc.c (kkcc_gc_stack_push_lisp_object):
+ * alloc.c (mark_object_maybe_checking_free):
+ * alloc.c (mark_struct_contents):
+ * alloc.c (kkcc_marking):
+ * alloc.c (mark_object):
+ * data.c (finish_marking_weak_lists):
+ * data.c (continue_marking_ephemerons):
+ * data.c (finish_marking_ephemerons):
+ * elhash.c (MARK_OBJ):
+ * lisp.h:
+ * profile.c (mark_profiling_info_maphash): Add level (current
+ depth of mark tree) and pos (position within description) as
+ additional arguments to KKCC mark functions.
+
2004-10-25 Mike Alexander <mta(a)arbortext.com>
* Makefile.in.in (obj_src): Fix a typo in the PDUMP section
1.107 +158 -17 XEmacs/xemacs/src/alloc.c
Index: alloc.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/alloc.c,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -r1.106 -r1.107
--- alloc.c 2005/02/03 16:14:04 1.106
+++ alloc.c 2005/03/10 09:12:37 1.107
＠＠ -3091,6 +3091,10 ＠＠
default:
stderr_out ("Unsupported count type : %d (line = %d, code = %ld)\n",
idesc[line].type, line, (long) code);
+#ifdef USE_KKCC
+ if (gc_in_progress)
+ kkcc_backtrace ();
+#endif
#ifdef PDUMP
if (in_pdump)
pdump_backtrace ();
＠＠ -3307,6 +3311,10 ＠＠
{
void *data;
const struct memory_description *desc;
+#ifdef DEBUG_XEMACS
+ int level;
+ int pos;
+#endif
} kkcc_gc_stack_entry;
static kkcc_gc_stack_entry *kkcc_gc_stack_ptr;
＠＠ -3314,6 +3322,72 ＠＠
static kkcc_gc_stack_entry *kkcc_gc_stack_last_entry;
static int kkcc_gc_stack_size;
+#ifdef DEBUG_XEMACS
+#define KKCC_BT_STACK_SIZE 4096
+
+static struct
+{
+ void *obj;
+ const struct memory_description *desc;
+ int pos;
+} kkcc_bt[KKCC_BT_STACK_SIZE];
+
+static int kkcc_bt_depth = 0;
+
+#define KKCC_BT_INIT() kkcc_bt_depth = 0;
+
+void
+kkcc_backtrace (void)
+{
+ int i;
+ stderr_out ("KKCC mark stack backtrace :\n");
+ for (i = kkcc_bt_depth - 1; i >= 0; i--)
+ {
+ stderr_out (" [%d]", i);
+ if ((((struct lrecord_header *) kkcc_bt[i].obj)->type
+ >= lrecord_type_free)
+ || (!LRECORDP (kkcc_bt[i].obj))
+ || (!XRECORD_LHEADER_IMPLEMENTATION (kkcc_bt[i].obj)))
+ {
+ stderr_out (" non Lisp Object");
+ }
+ else
+ {
+ stderr_out (" %s",
+ XRECORD_LHEADER_IMPLEMENTATION (kkcc_bt[i].obj)->name);
+ }
+ stderr_out (" (addr: 0x%x, desc: 0x%x, ",
+ (int) kkcc_bt[i].obj,
+ (int) kkcc_bt[i].desc);
+ if (kkcc_bt[i].pos >= 0)
+ stderr_out ("pos: %d)\n", kkcc_bt[i].pos);
+ else
+ stderr_out ("root set)\n");
+ }
+}
+
+static void
+kkcc_bt_push (void *obj, const struct memory_description *desc,
+ int level, int pos)
+{
+ kkcc_bt_depth = level;
+ kkcc_bt[kkcc_bt_depth].obj = obj;
+ kkcc_bt[kkcc_bt_depth].desc = desc;
+ kkcc_bt[kkcc_bt_depth].pos = pos;
+ kkcc_bt_depth++;
+ if (kkcc_bt_depth > KKCC_BT_STACK_SIZE)
+ {
+ stderr_out ("KKCC backtrace overflow, adjust KKCC_BT_STACK_SIZE.\n");
+ stderr_out ("Maybe it is a loop?\n");
+ ABORT ();
+ }
+}
+
+#else /* not DEBUG_XEMACS */
+#define KKCC_BT_INIT()
+#define kkcc_bt_push(obj, desc, level, pos)
+#endif /* not DEBUG_XEMACS */
+
static void
kkcc_gc_stack_init (void)
{
＠＠ -3359,15 +3433,32 ＠＠
#define KKCC_GC_STACK_EMPTY (kkcc_gc_stack_top < kkcc_gc_stack_ptr)
static void
-kkcc_gc_stack_push (void *data, const struct memory_description *desc)
+#ifdef DEBUG_XEMACS
+kkcc_gc_stack_push_1 (void *data, const struct memory_description *desc,
+ int level, int pos)
+#else
+kkcc_gc_stack_push_1 (void *data, const struct memory_description *desc)
+#endif
{
if (KKCC_GC_STACK_FULL)
kkcc_gc_stack_realloc();
kkcc_gc_stack_top++;
kkcc_gc_stack_top->data = data;
kkcc_gc_stack_top->desc = desc;
+#ifdef DEBUG_XEMACS
+ kkcc_gc_stack_top->level = level;
+ kkcc_gc_stack_top->pos = pos;
+#endif
}
+#ifdef DEBUG_XEMACS
+#define kkcc_gc_stack_push(data, desc, level, pos) \
+ kkcc_gc_stack_push_1 (data, desc, level, pos)
+#else
+#define kkcc_gc_stack_push(data, desc, level, pos) \
+ kkcc_gc_stack_push_1 (data, desc)
+#endif
+
static kkcc_gc_stack_entry *
kkcc_gc_stack_pop (void)
{
＠＠ -3378,7 +3469,11 ＠＠
}
void
-kkcc_gc_stack_push_lisp_object (Lisp_Object obj)
+#ifdef DEBUG_XEMACS
+kkcc_gc_stack_push_lisp_object_1 (Lisp_Object obj, int level, int pos)
+#else
+kkcc_gc_stack_push_lisp_object_1 (Lisp_Object obj)
+#endif
{
if (XTYPE (obj) == Lisp_Type_Record)
{
＠＠ -3389,11 +3484,19 ＠＠
if (! MARKED_RECORD_HEADER_P (lheader))
{
MARK_RECORD_HEADER (lheader);
- kkcc_gc_stack_push((void*) lheader, desc);
+ kkcc_gc_stack_push((void*) lheader, desc, level, pos);
}
}
}
+#ifdef DEBUG_XEMACS
+#define kkcc_gc_stack_push_lisp_object(obj, level, pos) \
+ kkcc_gc_stack_push_lisp_object_1 (obj, level, pos)
+#else
+#define kkcc_gc_stack_push_lisp_object(obj, level, pos) \
+ kkcc_gc_stack_push_lisp_object_1 (obj)
+#endif
+
#ifdef ERROR_CHECK_GC
#define KKCC_DO_CHECK_FREE(obj, allow_free) \
do \
＠＠ -3409,24 +3512,44 ＠＠
#endif
#ifdef ERROR_CHECK_GC
+#ifdef DEBUG_XEMACS
+static void
+mark_object_maybe_checking_free_1 (Lisp_Object obj, int allow_free,
+ int level, int pos)
+#else
static void
-mark_object_maybe_checking_free (Lisp_Object obj, int allow_free)
+mark_object_maybe_checking_free_1 (Lisp_Object obj, int allow_free)
+#endif
{
KKCC_DO_CHECK_FREE (obj, allow_free);
- kkcc_gc_stack_push_lisp_object (obj);
+ kkcc_gc_stack_push_lisp_object (obj, level, pos);
}
+
+#ifdef DEBUG_XEMACS
+#define mark_object_maybe_checking_free(obj, allow_free, level, pos) \
+ mark_object_maybe_checking_free_1 (obj, allow_free, level, pos)
#else
-#define mark_object_maybe_checking_free(obj, allow_free) \
- kkcc_gc_stack_push_lisp_object (obj)
-#endif /* ERROR_CHECK_GC */
+#define mark_object_maybe_checking_free(obj, allow_free, level, pos) \
+ mark_object_maybe_checking_free_1 (obj, allow_free)
+#endif
+#else /* not ERROR_CHECK_GC */
+#define mark_object_maybe_checking_free(obj, allow_free, level, pos) \
+ kkcc_gc_stack_push_lisp_object (obj, level, pos)
+#endif /* not ERROR_CHECK_GC */
/* This function loops all elements of a struct pointer and calls
mark_with_description with each element. */
static void
-mark_struct_contents (const void *data,
+#ifdef DEBUG_XEMACS
+mark_struct_contents_1 (const void *data,
+ const struct sized_memory_description *sdesc,
+ int count, int level, int pos)
+#else
+mark_struct_contents_1 (const void *data,
const struct sized_memory_description *sdesc,
int count)
+#endif
{
int i;
Bytecount elsize;
＠＠ -3434,10 +3557,18 ＠＠
for (i = 0; i < count; i++)
{
- kkcc_gc_stack_push (((char *) data) + elsize * i, sdesc->description);
+ kkcc_gc_stack_push (((char *) data) + elsize * i, sdesc->description,
+ level, pos);
}
}
+#ifdef DEBUG_XEMACS
+#define mark_struct_contents(data, sdesc, count, level, pos) \
+ mark_struct_contents_1 (data, sdesc, count, level, pos)
+#else
+#define mark_struct_contents(data, sdesc, count, level, pos) \
+ mark_struct_contents_1 (data, sdesc, count)
+#endif
/* This function implements the KKCC mark algorithm.
Instead of calling mark_object, all the alive Lisp_Objects are pushed
＠＠ -3450,12 +3581,21 ＠＠
void *data = 0;
const struct memory_description *desc = 0;
int pos;
+#ifdef DEBUG_XEMACS
+ int level = 0;
+ KKCC_BT_INIT ();
+#endif
while ((stack_entry = kkcc_gc_stack_pop ()) != 0)
{
data = stack_entry->data;
desc = stack_entry->desc;
+#ifdef DEBUG_XEMACS
+ level = stack_entry->level + 1;
+#endif
+ kkcc_bt_push (data, desc, stack_entry->level, stack_entry->pos);
+
for (pos = 0; desc[pos].type != XD_END; pos++)
{
const struct memory_description *desc1 = &desc[pos];
＠＠ -3493,8 +3633,8 ＠＠
if (EQ (*stored_obj, Qnull_pointer))
break;
mark_object_maybe_checking_free
- (*stored_obj, (desc1->flags) & XD_FLAG_FREE_LISP_OBJECT);
-
+ (*stored_obj, (desc1->flags) & XD_FLAG_FREE_LISP_OBJECT,
+ level, pos);
break;
}
case XD_LISP_OBJECT_ARRAY:
＠＠ -3510,9 +3650,9 ＠＠
if (EQ (*stored_obj, Qnull_pointer))
break;
-
mark_object_maybe_checking_free
- (*stored_obj, (desc1->flags) & XD_FLAG_FREE_LISP_OBJECT);
+ (*stored_obj, (desc1->flags) & XD_FLAG_FREE_LISP_OBJECT,
+ level, pos);
}
break;
}
＠＠ -3524,7 +3664,7 ＠＠
lispdesc_indirect_description (data, desc1->data2.descr);
const char *dobj = * (const char **) rdata;
if (dobj)
- mark_struct_contents (dobj, sdesc, count);
+ mark_struct_contents (dobj, sdesc, count, level, pos);
break;
}
case XD_BLOCK_ARRAY:
＠＠ -3534,7 +3674,7 ＠＠
const struct sized_memory_description *sdesc =
lispdesc_indirect_description (data, desc1->data2.descr);
- mark_struct_contents (rdata, sdesc, count);
+ mark_struct_contents (rdata, sdesc, count, level, pos);
break;
}
case XD_UNION:
＠＠ -3546,6 +3686,7 ＠＠
default:
stderr_out ("Unsupported description type : %d\n", desc1->type);
+ kkcc_backtrace ();
ABORT ();
}
}
＠＠ -4735,7 +4876,7 ＠＠
#ifdef USE_KKCC
/* initialize kkcc stack */
kkcc_gc_stack_init();
-#define mark_object kkcc_gc_stack_push_lisp_object
+#define mark_object(obj) kkcc_gc_stack_push_lisp_object (obj, 0, -1)
#endif /* USE_KKCC */
{ /* staticpro() */
1.63 +4 -4 XEmacs/xemacs/src/data.c
Index: data.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/data.c,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- data.c 2005/02/03 16:14:04 1.62
+++ data.c 2005/03/10 09:12:38 1.63
＠＠ -2739,7 +2739,7 ＠＠
if (need_to_mark_elem && ! marked_p (elem))
{
#ifdef USE_KKCC
- kkcc_gc_stack_push_lisp_object (elem);
+ kkcc_gc_stack_push_lisp_object (elem, 0, -1);
#else /* NOT USE_KKCC */
mark_object (elem);
#endif /* NOT USE_KKCC */
＠＠ -2767,7 +2767,7 ＠＠
if (!NILP (rest2) && ! marked_p (rest2))
{
#ifdef USE_KKCC
- kkcc_gc_stack_push_lisp_object (rest2);
+ kkcc_gc_stack_push_lisp_object (rest2, 0, -1);
#else /* NOT USE_KKCC */
mark_object (rest2);
#endif /* NOT USE_KKCC */
＠＠ -3148,7 +3148,7 ＠＠
{
#ifdef USE_KKCC
kkcc_gc_stack_push_lisp_object
- (XCAR (XEPHEMERON (rest)->cons_chain));
+ (XCAR (XEPHEMERON (rest)->cons_chain), 0, -1);
#else /* NOT USE_KKCC */
mark_object (XCAR (XEPHEMERON (rest)->cons_chain));
#endif /* NOT USE_KKCC */
＠＠ -3198,7 +3198,7 ＠＠
MARK_CONS (XCONS (XEPHEMERON (rest)->cons_chain));
#ifdef USE_KKCC
kkcc_gc_stack_push_lisp_object
- (XCAR (XEPHEMERON (rest)->cons_chain));
+ (XCAR (XEPHEMERON (rest)->cons_chain), 0, -1);
#else /* NOT USE_KKCC */
mark_object (XCAR (XEPHEMERON (rest)->cons_chain));
#endif /* NOT USE_KKCC */
1.41 +7 -7 XEmacs/xemacs/src/elhash.c
Index: elhash.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/elhash.c,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- elhash.c 2005/02/03 16:14:05 1.40
+++ elhash.c 2005/03/10 09:12:38 1.41
＠＠ -1460,13 +1460,13 ＠＠
/* garbage collecting weak hash tables */
/************************************************************************/
#ifdef USE_KKCC
-#define MARK_OBJ(obj) do { \
- Lisp_Object mo_obj = (obj); \
- if (!marked_p (mo_obj)) \
- { \
- kkcc_gc_stack_push_lisp_object (mo_obj); \
- did_mark = 1; \
- } \
+#define MARK_OBJ(obj) do { \
+ Lisp_Object mo_obj = (obj); \
+ if (!marked_p (mo_obj)) \
+ { \
+ kkcc_gc_stack_push_lisp_object (mo_obj, 0, -1); \
+ did_mark = 1; \
+ } \
} while (0)
#else /* NO USE_KKCC */
1.125 +11 -1 XEmacs/xemacs/src/lisp.h
Index: lisp.h
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/lisp.h,v
retrieving revision 1.124
retrieving revision 1.125
diff -u -r1.124 -r1.125
--- lisp.h 2005/02/03 16:30:37 1.124
+++ lisp.h 2005/03/10 09:12:38 1.125
＠＠ -3585,7 +3585,17 ＠＠
int object_dead_p (Lisp_Object);
void mark_object (Lisp_Object obj);
#ifdef USE_KKCC
-void kkcc_gc_stack_push_lisp_object (Lisp_Object obj);
+#ifdef DEBUG_XEMACS
+void kkcc_gc_stack_push_lisp_object_1 (Lisp_Object obj, int level, int pos);
+#define kkcc_gc_stack_push_lisp_object(obj, level, pos) \
+ kkcc_gc_stack_push_lisp_object_1 (obj, level, pos)
+void kkcc_backtrace (void);
+#else
+void kkcc_gc_stack_push_lisp_object_1 (Lisp_Object obj);
+#define kkcc_gc_stack_push_lisp_object(obj, level, pos) \
+ kkcc_gc_stack_push_lisp_object_1 (obj)
+#define kkcc_backtrace()
+#endif
#endif /* USE_KKCC */
int marked_p (Lisp_Object obj);
extern int funcall_allocation_flag;
1.25 +1 -1 XEmacs/xemacs/src/profile.c
Index: profile.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/profile.c,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- profile.c 2005/02/03 16:14:08 1.24
+++ profile.c 2005/03/10 09:12:38 1.25
＠＠ -609,7 +609,7 ＠＠
void *UNUSED (void_closure))
{
#ifdef USE_KKCC
- kkcc_gc_stack_push_lisp_object (VOID_TO_LISP (void_key));
+ kkcc_gc_stack_push_lisp_object (VOID_TO_LISP (void_key), 0, -1);
#else /* NOT USE_KKCC */
mark_object (VOID_TO_LISP (void_key));
#endif /* NOT USE_KKCC */
- 1 participants
- 0 comments
CVS update by michaels (Fix Makefile problem with PDUMP build) MODIFIED: xemacs/src ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: michaels
Date: 05/03/10 10:06:04
Modified: xemacs/src ChangeLog Makefile.in.in
Log:
Subject: Fix Makefile problem with PDUMP build
2004-10-25 Mike Alexander <mta(a)arbortext.com>
* Makefile.in.in (obj_src): Fix a typo in the PDUMP section
Revision Changes Path
1.804 +4 -0 XEmacs/xemacs/src/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v
retrieving revision 1.803
retrieving revision 1.804
diff -u -r1.803 -r1.804
--- ChangeLog 2005/03/09 19:47:40 1.803
+++ ChangeLog 2005/03/10 09:05:44 1.804
＠＠ -1,3 +1,7 ＠＠
+2004-10-25 Mike Alexander <mta(a)arbortext.com>
+
+ * Makefile.in.in (obj_src): Fix a typo in the PDUMP section
+
2005-03-02 Marcus Crestani <crestani(a)informatik.uni-tuebingen.de>
* redisplay.h (struct rune): make type field an int, to fix
1.115 +1 -1 XEmacs/xemacs/src/Makefile.in.in
Index: Makefile.in.in
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/Makefile.in.in,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -r1.114 -r1.115
--- Makefile.in.in 2005/01/26 03:40:15 1.114
+++ Makefile.in.in 2005/03/10 09:05:52 1.115
＠＠ -613,7 +613,7 ＠＠
fi ; \
fi ; \
fi
- if ! test -f dump-size; then \
+ if test ! -f dump-size; then \
$(LIB_SRC)/insert-data-in-exec -s $(DUMP_TARGET).dmp > dump-size ; \
$(RM) dump-data.o $(DUMP_TARGET) $(DUMP_TARGET).dmp $(RAW_EXE);\
$(MAKE) $(RECURSIVE_MAKE_ARGS) $＠; \
- 1 participants
- 0 comments
CVS update by viteno MODIFIED: xemacs ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: viteno
Date: 05/03/09 23:51:12
Modified: xemacs version.sh
Log:
Update xemacs_extra_name.
Revision Changes Path
1.1091 +1 -1 XEmacs/xemacs/version.sh
Index: version.sh
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/version.sh,v
retrieving revision 1.1090
retrieving revision 1.1091
diff -u -r1.1090 -r1.1091
--- version.sh 2005/03/08 22:51:29 1.1090
+++ version.sh 2005/03/09 22:51:11 1.1091
＠＠ -8,5 +8,5 ＠＠
infodock_major_version=4
infodock_minor_version=0
infodock_build_version=8
-xemacs_extra_name="(+CVS-20050308)"
+xemacs_extra_name="(+CVS-20050309)"
xemacs_release_date="2005-02-18"
- 1 participants
- 0 comments
CVS update by viteno MODIFIED: xemacsweb/Develop ...
19 years, 9 months
CVS Monitor
CVS Monitor
User: viteno
Date: 05/03/09 22:24:57
Modified: xemacsweb/Develop ChangeLog packages.content
Log:
Announce new package re-builder.
Revision Changes Path
1.98 +4 -0 XEmacs/xemacsweb/Develop/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/ChangeLog,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -r1.97 -r1.98
--- ChangeLog 2005/02/28 12:48:49 1.97
+++ ChangeLog 2005/03/09 21:24:56 1.98
＠＠ -1,3 +1,7 ＠＠
+2005-03-09 Norbert Koch <viteno(a)xemacs.org>
+
+ * packages.content: Announce new package re-builder.
+
2005-02-28 Stephen J. Turnbull <stephen(a)xemacs.org>
* jobs.content: Add Aidan Kehoe and Steve Youngs to reviewers.
1.33 +2 -1 XEmacs/xemacsweb/Develop/packages.content
Index: packages.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/packages.content,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- packages.content 2005/02/17 08:34:59 1.32
+++ packages.content 2005/03/09 21:24:56 1.33
＠＠ -50,7 +50,7 ＠＠
</p>
<!-- Produced by:
- cvs/xemacs-builds/adrian/website/package-info2table.pl /usr/users/nk/cvs/packages
+ cvs/xemacs-builds/adrian/website/package-info2table.pl cvs/xprm
Id: package-info2table.pl,v 1.4 2003/10/13 23:24:08 adrian Exp -->
<table align="center" border="3" cellspacing="1" cellpadding="1" width="90%">
<caption>XEmacs packages</caption>
＠＠ -129,6 +129,7 ＠＠
<tr><td>psgml</td><td>psgml</td><td><a name="psgml" href="http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/p... HTML/SGML editing.</td></tr>
<tr><td>psgml-dtds</td><td>psgml-dtds</td><td><a name="psgml-dtds" href="http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/p... collection of DTDs for psgml.</td></tr>
<tr><td>python-modes</td><td>python-modes</td><td><a name="python-modes" href="http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/p... support.</td></tr>
+ <tr><td>re-builder</td><td>re-builder</td><td><a name="re-builder" href="http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/r... development tool for regular expressions.</td></tr>
<tr><td>reftex</td><td>reftex</td><td><a name="reftex" href="http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/r... support for LaTeX cross-references, citations..</td></tr>
<tr><td>riece</td><td>riece</td><td><a name="riece" href="http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/r... (Internet Relay Chat) client for Emacs.</td></tr>
<tr><td>rmail</td><td>rmail</td><td><a name="rmail" href="http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/r... obsolete Emacs mailer.</td></tr>
- 1 participants
- 0 comments