* Q6.3.2:: What are the differences between the various MS Windows emacsen?
* Q6.3.3:: What is the porting team doing at the moment?
+Troubleshooting:
+* Q6.4.1:: XEmacs won't start on Windows. (NEW)
+
\1f
File: xemacs-faq.info, Node: Q6.0.1, Next: Q6.0.2, Prev: MS Windows, Up: MS Windows
Q6.1.2: What compiler do I need to compile XEmacs?
--------------------------------------------------
- You need Visual C++ 4.2 or 5.0, with the exception of the Cygwin
-port, which uses Gcc.
+ You need Visual C++ 4.2, 5.0, or 6.0, with the exception of the
+Cygwin port, which uses Gcc. There is also a MINGW32 port of XEmacs
+(using Gcc, but using native libraries rather than the Cygwin
+libraries). #### More information about this should be provided.
\1f
File: xemacs-faq.info, Node: Q6.1.3, Next: Q6.1.4, Prev: Q6.1.2, Up: MS Windows
* make sure HOME is set. This controls where you `.emacs' file comes
from;
- * CYGWIN32 needs to be set to tty for process support work. e.g.
- CYGWIN32=tty;
+ * CYGWIN needs to be set to tty for process support work. e.g.
+ CYGWIN=tty; (use CYGWIN32=tty under b19 and older.)
* picking up some other grep or other unix like tools can kill
configure;
`http://sourceware.cygnus.com/cygwin/'
- You will need version b19 or later.
+ You will need version b19 or later. The latest current version is
+1.1.1. Other common versions you will see are b20.1.
- You will also need the X libraries. There are libraries at
-`http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/', but these are
-not b19 compatible. You can get b19 X11R6.3 binaries, as well as
-pre-built ncurses and graphic libraries, from:
+ Another location, one of the mirror sites of the site just mentioned,
+is usually a last faster:
+
+ `ftp://ftp.freesoftware.com/pub/sourceware/cygwin/'
+
+ You can obtain the latest version (currently 1.1.1) from the
+`latest/' subdirectory of either of the above two just-mentioned URL's.
+
+ *WARNING: The version of GCC supplied under `latest/', as of June
+6th, 2000, does not appear to work. It generates loads of spurious
+preprocessor warnings and errors, which makes it impossible to compile
+XEmacs with it.*
+
+ You will also need the X libraries. You can get them on the XEmacs
+FTP site at
+
+ `ftp://ftp.xemacs.org/pub/xemacs/aux/cygwin/'
+
+ You will find b19 and b20 versions of the X libraries, plus b19 and
+b20 versions of stuff that should go into `/usr/local/', donated by
+Andy Piper. This includes pre-built versions of various graphics
+libraries, such as PNG, JPEG, TIFF, and XPM. (Remember, GIF support is
+built-in to XEmacs.)
+
+ (X libraries for v1 and beyond of Cygwin can be found on the Cygwin
+site itself - look in the `xfree/' subdirectory.)
+
+ _NOTE:_ There are two versions of the XPM library provided in Andy's
+packets. Once is for building with X support, and the other for
+building without. The X version should work if you're building with
+both X and Windows support. The two files are called `libXpm-X.a' and
+`libXpm-noX.a' respectively, and you must symlink the appropriate one
+to `libXpm.a'. *CAREFUL:* By default, the non-X version is symlinked
+in. If you then configure XEmacs with X, you won't run into problems
+until you start compiling `events.c', at which point you'll get strange
+and decidedly non-obvious errors.
+
+ Please see `http://www.xemacs.freeserve.co.uk/' (Andy Piper's home
+page) for more information.
- `ftp://ftp.parallax.co.uk/pub/andyp/'.
+ BTW There are also libraries at
+`http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/', but these are
+not b19 compatible, and may in fact be native-compiled.
\1f
File: xemacs-faq.info, Node: Q6.2.1, Next: Q6.2.2, Prev: Q6.1.6, Up: MS Windows
\1f
-File: xemacs-faq.info, Node: Q6.3.3, Prev: Q6.3.2, Up: MS Windows
+File: xemacs-faq.info, Node: Q6.3.3, Next: Q6.4.1, Prev: Q6.3.2, Up: MS Windows
Q6.3.3: What is the porting team doing at the moment?
-----------------------------------------------------
The porting team is continuing work on the MS Windows-specific code.
\1f
+File: xemacs-faq.info, Node: Q6.4.1, Prev: Q6.3.3, Up: MS Windows
+
+6.3: Troubleshooting
+====================
+
+Q6.4.1 XEmacs won't start on Windows. (NEW)
+-------------------------------------------
+
+ XEmacs relies on a process called "dumping" to generate a working
+executable. Under MS-Windows this process effectively fixes the memory
+addresses of information in the executable. When XEmacs starts up it
+tries to reserve these memory addresses so that the dumping process can
+be reversed - putting the information back at the correct addresses.
+Unfortunately some .dlls (For instance the soundblaster driver) occupy
+memory addresses that can conflict with those needed by the dumped
+XEmacs executable. In this instance XEmacs will fail to start without
+any explanation. Note that this is extremely machine specific.
+
+ 21.1.10 includes a fix for this that makes more intelligent guesses
+about which memory addresses will be free, and this should cure the
+problem for most people. Unfortunately, no binary is yet available for
+this version. Check back periodically at
+
+ `ftp://ftp.xemacs.org/pub/xemacs/binaries/'.
+
+ 21.2 implements "portable dumping" which will eliminate the problem
+altogether. You might have better luck with the 21.2 beta binary,
+available at
+
+ `ftp://ftp.xemacs.org/pub/xemacs/beta/binaries/'.
+
+\1f
File: xemacs-faq.info, Node: Current Events, Prev: MS Windows, Up: Top
7 What the Future Holds
projects / chise / xemacs-chise.git / blobdiff