Re: xemacs 21.4.10 core dump during build
Ville Skyttä <scop(a)xemacs.org> writes:
On Sat, 2002-11-02 at 21:12, Simon Josefsson wrote:
> This is release-21-4 from CVS, built from a clean directory ("cvsco").
> Ideas?
[...]
> Linking with `-z nocombreloc'.
> - Consider configuring with --pdump.
Since you're on Linux, try --pdump, and possibly --with-system-malloc?
I think Stephen's announcement addendum has some info about this, too.
Dumping works with --pdump, thanks. Would it make sense to enable
--pdump in configure when it is required to build XEmacs? I.e., write
an autoconf test to detect the nocomreloc problem. (Or simply switch
to pdump for linux, unless there are known bugs in pdump.)
However, it doesn't complete the build:
Loading /home/jas/src/xemacs-21.4/lisp/loadhist.elc...
Loading /home/jas/src/xemacs-21.4/lisp/loaddefs.elc...
Loading site-load...
Finding pointers to doc strings...
Finding pointers to doc strings...done
Dumping under the name xemacs
Testing for Lisp shadows ...
make[1]: Leaving directory `/home/jas/src/xemacs-21.4/src'
Building finder database ...
Opening input file: No such file or directory,
/usr/local/lib/xemacs/mule-packages/lisp/edict/auto-autoloads.el
xemacs exiting
.
make: *** [lisp/finder-inf.el] Error 255
jas＠latte:~/src/xemacs-21.4$ src/xemacs
jas＠latte:~/src/xemacs-21.4$
Should XEmacs be looking in the package directory during build? The
file happened to be a stale symlink, but building XEmacs shouldn't
fail because of this IMHO.