Xemacs on Sun-Fire-280R

I've been attempting to build xemacs-21.1.14 on our Sun cluster, which includes a Sun-Fire-280R (Ultra-III) machine. All systems in the cluster are running Solaris 8. I find that the xemacs built by: ---------------------------------- ---------------------------------- segfaults almost immediately on the Ultra-III system, but runs OK on the others (all Ultra-II). This is true whether the build was performed on the Ultra-II or the Ultra-III platform. The details of the build are as in the following 'configure' output: ---------------------------------- XEmacs 21.1.14 "Cuyahoga Valley" configured for `sparc-sun-solaris2.8'. Where should the build process find the source code? /export/home/xemacs-21.1.14 What installation prefix should install use? /opt/gnu What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? cc -v -xO4 Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/dt/include /opt/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /opt/X11R6/lib Runtime library search path: /usr/ccs/lib:/usr/dt/lib:/opt/X11R6/lib:/opt/SUNWdt/lib Compiling in support for XAUTH. Compiling in support for XPM images. -------------------------------------------------------------------- WARNING: Compiling without PNG image support. WARNING: You should strongly consider installing the PNG libraries. WARNING: Otherwise certain images and glyphs may not display. WARNING: (a copy may be found in ftp://ftp.xemacs.org/pub/xemacs/aux) -------------------------------------------------------------------- Compiling in support for (builtin) GIF image handling. Compiling in native sound support. Compiling in support for DBM. Compiling in support for LDAP. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for ToolTalk. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. ---------------------------------- and I've tried with less optimisation, and also using 'gcc'. The error messages produced are as follows (the Xemacs window does not appear): ---------------------------------- Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode Warning: Conversion arguments for widget 'menubar' contain an unsupported address mode 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(a)xemacs.org&#39;. *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 /export/home/xemacs-21.1.14/src/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: # bind (frame-being-created) make-frame(nil #<x-device on "mraox46.ra.phy.cam.ac.uk:0.0" 0x982>) frame-initialize() # bind (debugger debug-on-error command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Segmentation Fault ---------------------------------- Can you offer any advice, please, or an indication of what's missing here? Apologies for not including any further tracebacks or core dumps, which did not appear to be available. Many thanks, David Titterington, Department of Physics, University of Cambridge, Cambridge, UK. djt(a)mrao.cam.ac.uk