kkm> ./configure --with-xpm --with-file-coding --with-jpeg --with-png --with-xface kkm> Build went smoothly. XEmacs does not run under X, and when I kill it, the kkm> backtrace tops at (make-device 'x nil). What's wrong? kkm> Oh, I do not have xemacs-base. See below. kkm> With -nw, it reports in the warnings buffer: kkm> Initialization error while loading nil kkm> WTA: stringp, nil kkm> With -q, this error goes away. I do not have: ~/.em* ~/.xem* /usr/lib/xem* kkm> /usr/local/lib/xem* kkm> What could get loaded? Martin> ?? kkm> I cannot install packages. The XEmacs package finding logic will always be kkm> black magic to me. Wherever I put packages, XEmacs does not notice them, kkm> as per load-path. Where should I put them? Under Windows, the path kkm> ../../packages (or maybe /xemacs/packages) works perfectly, not under Unix. kkm> Help! "packages" for a directory name is wrong; "xemacs-packages" is right. This is documented in README.packages and Texinfo. Martin> I continue to claim our packages are a user install nightmare. These two are unrelated. (I feel like a broken record here, repeating this over and over.) Kirill, if renaming the directory doesn't work, you really need to state what you mean by "wherever". There's pretty extensive documentation in Texinfo on how the path startup logic works under "Startup paths". Also, you can start with "--debug-paths" and mail the output to the list, so I can look at it. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla