aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--INSTALL46
1 files changed, 24 insertions, 22 deletions
diff --git a/INSTALL b/INSTALL
index 92349bd709e..e7be1359535 100644
--- a/INSTALL
+++ b/INSTALL
@@ -225,7 +225,8 @@ DETAILED BUILDING AND INSTALLATION:
225 225
226(This is for a Unix or Unix-like system. For MS-DOS and Windows 3.X, 226(This is for a Unix or Unix-like system. For MS-DOS and Windows 3.X,
227see below; search for MSDOG. For Windows 9X, Windows ME, Windows NT, 227see below; search for MSDOG. For Windows 9X, Windows ME, Windows NT,
228and Windows 2000, see the file nt/INSTALL.) 228Windows 2000, Windows XP/2003, and Windows Vista/2008, see the file
229nt/INSTALL.)
229 230
2301) Make sure your system has enough swapping space allocated to handle 2311) Make sure your system has enough swapping space allocated to handle
231a program whose pure code is 1.5 MB and whose data area is at 232a program whose pure code is 1.5 MB and whose data area is at
@@ -811,20 +812,21 @@ to run lisp/Makefile, as all the Lisp files are distributed in
811byte-compiled form as well. 812byte-compiled form as well.
812 813
813If you are building the MSDOG version of Emacs on an MSDOG-like system 814If you are building the MSDOG version of Emacs on an MSDOG-like system
814which supports long file names (e.g. Windows 95), you need to make 815which supports long file names (e.g. Windows 9X or Windows XP), you
815sure that long file names are handled consistently both when you 816need to make sure that long file names are handled consistently both
816unpack the distribution and compile it. If you intend to compile with 817when you unpack the distribution and compile it. If you intend to
817DJGPP v2.0 or later, and long file names support is enabled (LFN=y in 818compile with DJGPP v2.0 or later, and long file names support is
818the environment), you need to unpack Emacs distribution in a way that 819enabled (LFN=y in the environment), you need to unpack Emacs
819doesn't truncate the original long filenames to the DOS 8.3 namespace; 820distribution in a way that doesn't truncate the original long
820the easiest way to do this is to use djtar program which comes with 821filenames to the DOS 8.3 namespace; the easiest way to do this is to
821DJGPP, since it will note the LFN setting and behave accordingly. 822use djtar program which comes with DJGPP, since it will note the LFN
822DJGPP v1 doesn't support long filenames, so you must unpack Emacs with 823setting and behave accordingly. DJGPP v1 doesn't support long
823a program that truncates the filenames to 8.3 naming as it extracts 824filenames, so you must unpack Emacs with a program that truncates the
824files; again, using djtar after setting LFN=n is the recommended way. 825filenames to 8.3 naming as it extracts files; again, using djtar after
825You can build Emacs with LFN=n even if you use DJGPP v2, if some of 826setting LFN=n is the recommended way. You can build Emacs with LFN=n
826your tools don't support long file names: just ensure that LFN is set 827even if you use DJGPP v2, if some of your tools don't support long
827to `n' during both unpacking and compiling. 828file names: just ensure that LFN is set to `n' during both unpacking
829and compiling.
828 830
829(By the time you read this, you have already unpacked the Emacs 831(By the time you read this, you have already unpacked the Emacs
830distribution, but if the explanations above imply that you should have 832distribution, but if the explanations above imply that you should have
@@ -835,7 +837,7 @@ into problems during the build process.)
835It is important to understand that the runtime support of long file 837It is important to understand that the runtime support of long file
836names by the Emacs binary is NOT affected by the LFN setting during 838names by the Emacs binary is NOT affected by the LFN setting during
837compilation; Emacs compiled with DJGPP v2.0 or later will always 839compilation; Emacs compiled with DJGPP v2.0 or later will always
838support long file names on Windows 9X no matter what was the setting 840support long file names on Windows no matter what was the setting
839of LFN at compile time. However, if you compiled with LFN disabled 841of LFN at compile time. However, if you compiled with LFN disabled
840and want to enable LFN support after Emacs was already built, you need 842and want to enable LFN support after Emacs was already built, you need
841to make sure that the support files in the lisp, etc and info 843to make sure that the support files in the lisp, etc and info
@@ -876,12 +878,12 @@ rerun CONFIG.BAT. If you have neither ECHO.EXE nor DJECHO.EXE, you
876should be able to find them in your djdevNNN.zip archive (where NNN is 878should be able to find them in your djdevNNN.zip archive (where NNN is
877the DJGPP version number). 879the DJGPP version number).
878 880
879On Windows NT or Windows 2000, running "config msdos" might print an 881On Windows NT, Windows 2000/XP/Vista, running "config msdos" might
880error message like "VDM has been already loaded". This is because 882print an error message like "VDM has been already loaded". This is
881those systems have a program called `redir.exe' which is incompatible 883because those systems have a program called `redir.exe' which is
882with a program by the same name supplied with DJGPP, which is used by 884incompatible with a program by the same name supplied with DJGPP,
883config.bat. To resolve this, move the DJGPP's `bin' subdirectory to 885which is used by config.bat. To resolve this, move the DJGPP's `bin'
884the front of your PATH environment variable. 886subdirectory to the front of your PATH environment variable.
885 887
886To install the international fonts, chdir to the intlfonts-X.Y 888To install the international fonts, chdir to the intlfonts-X.Y
887directory created when you unpacked the intlfonts distribution (X.Y is 889directory created when you unpacked the intlfonts distribution (X.Y is