Re: emacs porting problems

[Kevin Rodgers]

Wendy Palm wrote:
> i'm in the process of porting emacs-21.3 to a new cray architecture
> and i'm having some problems i don't understand.
>
> if there's another email alias i should be using, my apologies and
> please direct me to it.
>
> i've spent a lot of time on this port, and am quite excited to have
> gotten this far (and a lot of customers have been begging for it), so
> i hope you can help me out.
>
> the machine is a cray X1, and i've put in the info in etc/MACHINES,
> created a src/s/unicosmp.h and src/m/cray.h file, and made some minor
> #ifdef additions where they were needed.
>
> i get all the way to a "emacs" being created and then it tries to run it-
> ...
>         ln temacs emacs
>         ./emacs -q -batch -f list-load-path-shadows
> Loading loadup.el (source)...
> Using load-path (/opt/open/36/share/emacs/21.3/site-lisp 
/opt/open/36/share/emacs/site-lisp /opt/open/36/share/emacs/21.3/leim 
/opt/open/36/share/emacs/21.3/lisp)
> Loading byte-run...
> Loading subr...
> Loading version.el (source)...
> Loading widget...
> Loading custom...
> Loading emacs-lisp/backquote...
> Loading map-ynp...
> Loading env...
> Loading cus-start (source)...
> Note, built-in variable `delete-exited-processes' not bound
> Note, built-in variable `x-bitmap-file-path' not bound
> Note, built-in variable `x-stretch-cursor' not bound
> Loading international/mule...
> Loading international/mule-conf.el (source)...
> *** Termination code 11 (bu21) (ignored)
>         (export PARALLEL; PARALLEL=0; cd leim; make all  \
>           CC='cc' CFLAGS='-Gn' CPPFLAGS='' \
>           LDFLAGS='' MAKE='make')
>
> so, the problem is two-fold -
> how do i get the variables bound properly?

delete-exited-processes is defined in src/process.c, but only if the
subprocesses C preprocessor symbol is defined.  src/config.h says that
it should be #define'd by your s/SYSTEM.h file.

x-bitmap-file-path is defined in src/xfns.c, but only if the
HAVE_X_WINDOWS C preprocesor symbol is defined.  src/config.h should
#define it, unless you specified --with-x==no or --without-x to the
configure script.

x-stretch-cursor is defined in src/xterm.c, again only if HAVE_X_WINDOWS
is #define'd.

> what does the mule error mean?

Sorry, I can't help you there.

--
Kevin Rodgers