Hrvoje Niksic <hniksic(a)srce.hr&gt; writes in xemacs-beta(a)xemacs.org: Of course. I'm building the Sumos and I use a bare-ass naked featureless bytecompile engine to do it. It's been that way for several years now. You are not allowed to call X functions during bytecompilation (nor any other feature specific call). uname -a: SunOS miho 5.6 Generic_105181-05 sun4u sparc ./configure '--with-mule' '--debug=no' '--error-checking=none' '--verbose=no' '--extra-verbose=no' '--compiler=gcc' '--mail-locking=file' '--cflags=-O' '--without-x11' '--prefix=/project/xemacs/home/steve/devel/dummy' '--without-shlib' '--without-canna' '--without-database' XEmacs 21.1.4 "Arches" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /project/xemacs/home/steve/devel/xemacs-21.1 What installation prefix should install use? /project/xemacs/home/steve/devel/dummy What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -O Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? none Runtime library search path: /usr/ccs/lib:/usr/local/lib Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. movemail will use "dot-locking" for locking mail spool files.