# ./configure -without-gcc --with-gnu-make --cflags '-fast -std' --site-include\ s=/usr/local/include --with-site-lisp Built the kit from patches using DEC C and gnu make. No problems, but one oddity... The initial sizing of purespace was VERY large. the build re-dumped with increasingly small purespace sizes unit it fit, but I don't recall every seeing this before. Purespace usage: 134856 of 1689000 (8% -- 1517k wasted). Purespace usage: 1052480 of 1689000 (62% -- 621k wasted). Purespace usage: 1052480 of 1052480 (100%). Several minor errors were detected in dgif_lib.c. cc: Warning: dgif_lib.c, line 113: In this statement, the referenced type of th\ e pointer value "Buf" is "unsigned char", which is not compatible with "const c\ har". if (strncmp(GIF_STAMP, Buf, GIF_VERSION_POS) != 0) { --------^ cc: Warning: dgif_lib.c, line 252: In this statement, the referenced type of th\ e pointer value "(GifPixelType ...)0" is "unsigned char", which is not compatib\ le with "char". sp->RasterBits = (GifPixelType *)NULL; --------^ cc: Warning: dgif_lib.c, line 747: In this statement, the referenced type of th\ e pointer value "(GifPixelType ...)malloc(...)" is "unsigned char", which is no\ t compatible with "char". sp->RasterBits ----------------^ cc: Warning: dgif_lib.c, line 750: In this statement, the referenced type of th\ e pointer value "sp->RasterBits" is "char", which is not compatible with "unsig\ ned char". DGifGetLine(GifFile, sp->RasterBits, ImageSize); ----------------^ cc: Warning: dgif_lib.c, line 802: In this statement, the referenced type of th\ e pointer value "(GifByteType ...)malloc(...)" is "unsigned char", which is not\ compatible with "char". ep->Bytes = (GifByteType *)malloc(size); ----^ emacs.c had one more: cc -c -fast -std -Demacs -I. -DHAVE_CONFIG_H -std -I/usr/local/include -I/usr/\ dt/include emacs.c cc: Warning: emacs.c, line 2520: In this statement, the referenced type of the \ pointer value "newpath" is "unsigned char", which is not compatible with "const\ char". len = strlen (newpath); --------^ cmdloop.c had: cc: Warning: cmdloop.c, line 507: Non-void function "Fcommand_loop_1" does not \ contain a return statement. DEFUN ("command-loop-1", Fcommand_loop_1, 0, 0, 0, /* ^ That was it. Here is the config. Full build attached. XEmacs 21.0 "Erzgeberg" configured for `alphaev56-dec-osf4.0d'. Where should the build process find the source code? /home/oberman/utils/x$ What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/decosf4-0.h' and `m/alpha.h' What compiler should XEmacs be built with? cc -fast -std Should XEmacs use the GNU version of malloc? no (The GNU allocators don't work with this system configuration). 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 Where do we find X Windows libraries? /usr/dt/lib Additional header files: /usr/local/include Runtime library search path: /usr/dt/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for TIFF image handling. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in EXPERIMENTAL support for Drag'n'Drop ( CDE ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "flock" for locking mail spool files. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634