🚀 go-pugleaf

上野です。
> > ./configure sparc-sun-sunos4.1.4shr
> > 
> > で通りませんか？
> 
> おかげさまで./configure sparc-sun-sunos4.1.4shrはとおりました。makeも終ったの
> ですが、起動するとcoreをはいて落ちてしまいました。時間が有る時にもう少し詳し
> く見てみます。有難うございました。

お手上げなのでもう一度お願いします。

SUN OS 4.1.4 でのxemacs-21.1.10のconfigureとmakeは終ったのですが、
以下のようになります。何を調べれば良いのでしょうか？

% xemacs

Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.

If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes@xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.

If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type

  gdb /usr/local/bin/xemacs core
then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB.  A similar procedure should work for all of
these.  Ask your system administrator if you need more help.)

Lisp backtrace follows:

  # (unwind-protect ...)
  make-device(x nil)
  # bind (display)
  make-x-device(nil)
  init-x-win()
  # bind (debugger debug-on-error command-line-args-left)
  command-line()
  # (unwind-protect ...)
  normal-top-level()
  # (condition-case ... . error)
  # (catch top-level ...)
Segmentation fault (core dumped)