4:58 p.m.
XEmacs without pdump would allow to add
"../xemacs-packages/lisp/vc/vc-hooks.elc"
"../lisp/wid-edit.elc"
"../xemacs-packages/lisp/xemacs-base/comint.elc"
to `site-packages' file and dump them during build. With pdump
dumping prints:
Undumpable object type : extent-info
On some platforms (including one described below) `configure.in'
comment says that glibc 2.3.1 seems to hose unexec, so enabling pdump
is required for building. Perhaps it should check for glibc version
since my one is earlier than 2.3.1.
uname -a: Linux rhysling 2.2.19-7.1.asp.exst #1 Sun Mar 30 23:14:10 MSD 2003 i686 unknown
../configure '--prefix=/home/gin' '--cflags=-g -O99 -Wall -Wno-switch
-Wpointer-arith -Winline -Wmissing-prototypes -Wshadow' '--with-gpm=no'
'--with-sound=native' '--with-pop' '--mail-locking=lockf'
'--with-clash-detection' '--debug' '--error-checking=all'
'--with-mule=yes' '--with-database=no' '--with-ldap=yes'
'--with-hesiod=no' '--with-menubars=lucid'
'--with-scrollbars=lucid' '--with-dialogs=lucid' '--with-xim=xlib'
'--with-canna=no' '--with-wnn=no' '--with-wnn6=no'
'--with-msw=no' '--with-xfs=yes'
XEmacs 21.4.12 "Portable Code" configured for `i686-pc-linux'.
Compilation / Installation:
Source code location: /home/gin/share/xemacs-21.4
Installation prefix: /home/gin
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -g -O99 -Wall -Wno-switch -Wpointer-arith
-Winline -Wmissing-prototypes -Wshadow
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11/include
- X Windows libraries location: /usr/X11/lib
- Handling WM_COMMAND properly.
Using Lucid menubars.
Using Lucid scrollbars.
Using Motif dialog boxes.
Using Motif native widgets.
TTY:
Compiling in support for ncurses.
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Sound:
Compiling in support for sound (native).
Databases:
Compiling in support for LDAP.
Compiling in support for PostgreSQL.
- Using PostgreSQL header file: pgsql/libpq-fe.h
- Using PostgreSQL V7 bindings.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
- Using XFontSet to provide bilingual menubar.
Mail:
Compiling in support for POP mail retrieval.
Compiling in support for "lockf" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new portable dumper.
Compiling in support for extra debugging code.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
10:55 a.m.
>>>> "Ilya" == Ilya N Golubev
<gin(a)mo.msk.ru> writes:
Ilya> Perhaps it should check for glibc version since my one is
Ilya> earlier than 2.3.1.
Why? unexec is a broken idea. We want to encourage the use of the
portable dumper, and it has been very satisfactory for almost all
users, not to mention decreasing the number of bug reports.
If for whatever reason, you want to use unexec, be our guest. I hope
you insurance is paid up! :-) --pdump=no is available and will be
available for the foreseeable future.
--
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:01 p.m.
New subject: Undumpable object type : buffer
Some configurations of xemacs (`--pdump' ones) do not allow dumped
lisp files (listed in `site-packages') to use buffer data type.
Despite of this cc-mode before 5.30 was dumpable. Since 5.30 (5.141
mast 10-Sep-02) `cc-vars.el' uses temporay buffers for computing
initial variable values. This makes it and rest of cc-mode depending
on it undumpable in those configurations.
Is using temporary buffers really necessary? Is there something that
may not be done using string operations only?
Already wrote on Mon, 12 May 2003 16:57:16 (GMT) to
<xemacs-beta(a)xemacs.org> about very limited data type set allowed for
dumping. What about extending it?
12:08 a.m.
New subject: Undumpable object type : buffer
On Fri, Sep 26, 2003 at 11:01:29PM +0400, Ilya N. Golubev wrote:
Already wrote on Mon, 12 May 2003 16:57:16 (GMT) to
<xemacs-beta(a)xemacs.org> about very limited data type set allowed for
dumping. What about extending it?
Be our guest, but you're not going to enjoy the ride. Buffer has a
lot of other object types linked to it (if you dump object x, you must
be able to dump every object x has a reference to), and in particular
I suspect you don't want to go anywhere near console, frame or device.
They are linked to system thingies, and more importantly they are
recreated at startup.
I'd suspect extent-info links to the underlying buffer too.
OG.
4:52 p.m.
New subject: Undumpable object type : buffer
"Ilya N. Golubev" <gin(a)mo.msk.ru> wrote:
/.../ Since 5.30 (5.141 mast 10-Sep-02) `cc-vars.el' uses
temporay
buffers for computing initial variable values. This makes it and
rest of cc-mode depending on it undumpable in those configurations.
Is using temporary buffers really necessary? Is there something that
may not be done using string operations only?
The tests are done to check some properties of syntax classes in
buffers. To use strings instead it would e.g. be necessary to be able
to call forward-sexp on a string, and to set the syntax-table text
property on strings. Afaik that isn't supported.
An alternative could perhaps be to replace the tests with their
results in the XEmacs packaging of CC Mode. Afterall, the result
always should be the same provided the package is only used with
XEmacs >= 21.4. That's however not an option in my upstream source
code since it's unified across all emacsen.
7302
days inactive
7440
days old
4 comments
4 participants
participants (4)
-
Ilya N. Golubev -
Martin Stjernholm -
Olivier Galibert -
Stephen J. Turnbull