Olivier Galibert <galibert(a)pobox.com> writes in xemacs-beta(a)xemacs.org:
What I plan to do after I'm finished whipping our DSP cards into
submission:
- compute a md5 (or sum, or whatever) of the Installation file at
configure time
- slap it into config.h and Makefile
This won't necessarily work. The Installation file need not necessarily
change as the temacs image changes, especially for developers. I first
got the core dumps after doing a `cvs update' which even with rerunning
configure won't change the contents of the Installation file.
How sensitive is the .dmp file to the environment? For example, if I
build and pdump an XEmacs that has staticly linked libraries, then
relink a temacs with shared libraries, will that still work?
- rename the xemacs.dmp file to xemacs-[md5].dmp (or
<whatever>-[md5].<whatever>, I'm not religious about that)
O.K.
- add a flag to [tx]emacs to force it to ignore .dmp (aka, forced
dump)
O.K.
This way:
- we have filesystem timestamps for the normal builds
- we can have -mule, -nomule, -optimized, etc... versions without conflict
Good.
> 0. I would like to see this made a default as soon as possible.
There is a bug in the filling code in mule mode I have been unable
to
trace (for my level of lisp expertise, the kinsoku processing is
simply unreadable).
My face customizations in .emacs are coming out wonky, but I haven't
checked a non-pdumped 21.2 recently.
I know of no other bug, but I'm not yet using it
for my day-to-day work.
O.K. Jareth owns the kinsoku code and you should check with him on
this when he returns from vacation, hopefully some time this week.