+File: xemacs-faq.info, Node: Installation, Next: Customization, Prev: Introduction, Up: Top
+
+2 Installation and Trouble Shooting
+***********************************
+
+ This is part 2 of the XEmacs Frequently Asked Questions list. This
+section is devoted to Installation, Maintenance and Trouble Shooting.
+
+* Menu:
+
+Installation:
+* Q2.0.1:: Running XEmacs without installing.
+* Q2.0.2:: XEmacs is too big.
+* Q2.0.3:: Compiling XEmacs with Netaudio.
+* Q2.0.4:: Problems with Linux and ncurses.
+* Q2.0.5:: Do I need X11 to run XEmacs?
+* Q2.0.6:: I'm having strange crashes. What do I do?
+* Q2.0.7:: Libraries in non-standard locations.
+* Q2.0.8:: can't resolve symbol _h_errno
+* Q2.0.9:: Where do I find external libraries?
+* Q2.0.10:: After I run configure I find a coredump, is something wrong?
+* Q2.0.11:: XEmacs can't resolve host names.
+* Q2.0.12:: Why can't I strip XEmacs?
+* Q2.0.13:: I don't need no steenkin' packages. Do I? (NEW)
+* Q2.0.14:: I don't want to install a million .els one at a time! (NEW)
+
+Trouble Shooting:
+* Q2.1.1:: XEmacs just crashed on me!
+* Q2.1.2:: Cryptic Minibuffer messages.
+* Q2.1.3:: Translation Table Syntax messages at Startup.
+* Q2.1.4:: Startup warnings about deducing proper fonts?
+* Q2.1.5:: XEmacs cannot connect to my X Terminal.
+* Q2.1.6:: XEmacs just locked up my Linux X server.
+* Q2.1.7:: HP Alt key as Meta.
+* Q2.1.8:: got (wrong-type-argument color-instance-p nil)!
+* Q2.1.9:: XEmacs causes my OpenWindows 3.0 server to crash.
+* Q2.1.10:: Warnings from incorrect key modifiers.
+* Q2.1.11:: Can't instantiate image error... in toolbar
+* Q2.1.12:: Regular Expression Problems on DEC OSF1.
+* Q2.1.13:: HP/UX 10.10 and `create_process' failure
+* Q2.1.14:: C-g doesn't work for me. Is it broken?
+* Q2.1.15:: How to debug an XEmacs problem with a debugger.
+* Q2.1.16:: XEmacs crashes in `strcat' on HP/UX 10.
+* Q2.1.17:: `Marker does not point anywhere'.
+* Q2.1.18:: [This question intentionally left blank]
+* Q2.1.19:: XEmacs does not follow the local timezone.
+* Q2.1.20:: `Symbol's function definition is void: hkey-help-show.'
+* Q2.1.21:: [This question intentionally left blank]
+* Q2.1.22:: XEmacs seems to take a really long time to do some things.
+* Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
+* Q2.1.24:: XEmacs won't start without network. (NEW)
+* Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
+
+\1f
+File: xemacs-faq.info, Node: Q2.0.1, Next: Q2.0.2, Prev: Installation, Up: Installation
+
+2.0: Installation
+=================
+
+Q2.0.1: Running XEmacs without installing
+-----------------------------------------
+
+ How can I just try XEmacs without installing it?
+
+ XEmacs will run in place without requiring installation and copying
+of the Lisp directories, and without having to specify a special
+build-time flag. It's the copying of the Lisp directories that
+requires so much space. XEmacs is largely written in Lisp.
+
+ A good method is to make a shell alias for xemacs:
+
+ alias xemacs=/i/xemacs-20.2/src/xemacs
+
+ (You will obviously use whatever directory you downloaded the source
+tree to instead of `/i/xemacs-20.2').
+
+ This will let you run XEmacs without massive copying.
+
+\1f
+File: xemacs-faq.info, Node: Q2.0.2, Next: Q2.0.3, Prev: Q2.0.1, Up: Installation
+
+Q2.0.2: XEmacs is too big
+-------------------------
+
+ The space required by the installation directories can be reduced
+dramatically if desired. Gzip all the .el files. Remove all the
+packages you'll never want to use. Remove the TexInfo manuals. Remove
+the Info (and use just hardcopy versions of the manual). Remove most
+of the stuff in etc. Remove or gzip all the source code. Gzip or
+remove the C source code. Configure it so that copies are not made of
+the support lisp.
+
+ These are all Emacs Lisp source code and bytecompiled object code.
+You may safely gzip everything named *.el here. You may remove any
+package you don't use. _Nothing bad will happen if you delete a package
+that you do not use_. You must be sure you do not use it though, so be
+conservative at first.
+
+ Possible candidates for deletion include w3, games, hyperbole, mh-e,
+hm-html-menus, vm, viper, oobr, gnus, etc. Ask yourself, _Do I ever
+want to use this package?_ If the answer is no, then it is a candidate
+for removal.
+
+ First, gzip all the .el files. Then go about package by package and
+start gzipping the .elc files. Then run XEmacs and do whatever it is
+you normally do. If nothing bad happens, then delete the directory. Be
+conservative about deleting directories, and it would be handy to have a
+backup around in case you get too zealous.
+
+ `prim', `modes', `packages', and `utils' are four directories you
+definitely do *not* want to delete, although certain packages can be
+removed from them if you do not use them.
+
+ Online texinfo sources in the `info' can either be compressed them
+or remove them. In either case, `C-h i' (info mode) will no longer
+work.
+
+\1f
+File: xemacs-faq.info, Node: Q2.0.3, Next: Q2.0.4, Prev: Q2.0.2, Up: Installation
+
+Q2.0.3: Compiling XEmacs with Netaudio.
+---------------------------------------
+
+ What is the best way to compile XEmacs with the netaudio system,
+since I have got the netaudio system compiled but installed at a weird
+place, I am not root. Also in the READMEs it does not say anything
+about compiling with the audioserver?
+
+ You should only need to add some stuff to the configure command line.
+To tell it to compile in netaudio support: `--with-sound=both', or
+`--with-sound=nas' if you don't want native sound support for some
+reason.) To tell it where to find the netaudio includes and libraries:
+
+ --site-libraries=WHATEVER
+ --site-includes=WHATEVER
+
+ Then (fingers crossed) it should compile and it will use netaudio if
+you have a server running corresponding to the X server. The netaudio
+server has to be there when XEmacs starts. If the netaudio server goes
+away and another is run, XEmacs should cope (fingers crossed, error
+handling in netaudio isn't perfect).
+
+ BTW, netaudio has been renamed as it has a name clash with something
+else, so if you see references to NAS or Network Audio System, it's the
+same thing. It also might be found at
+`ftp://ftp.x.org/contrib/audio/nas/'.