Mercurial > emacs
comparison INSTALL @ 15444:66a9ef0892a2
Explain about MSDOS installation and long file name support.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Mon, 17 Jun 1996 22:25:58 +0000 |
parents | 884b7293ccc7 |
children | e3d77845180c |
comparison
equal
deleted
inserted
replaced
15443:7a3398850d94 | 15444:66a9ef0892a2 |
---|---|
509 | 509 |
510 | 510 |
511 Installation on MSDOG (a.k.a. MSDOS) | 511 Installation on MSDOG (a.k.a. MSDOS) |
512 | 512 |
513 To install on MSDOG, you need to have the GNU C compiler for MSDOG | 513 To install on MSDOG, you need to have the GNU C compiler for MSDOG |
514 (also known as djgpp), GNU Make, rm, mv, chmod, and sed. See the | 514 (also known as djgpp), GNU Make, rm, mv, and sed. See the remarks in |
515 remarks in config.bat for more information about locations and | 515 config.bat for more information about locations and versions. The |
516 versions. | 516 file etc/FAQ includes pointers to Internet sites where you can find |
517 | 517 the necessary utilities; search for "MS-DOS". The configuration step |
518 If you are compiling on an MSDOG-like system which has long file | 518 (see below) will test for these utilities and will refuse to continue |
519 names, you may need to do `SET LFN=y' for some of the commands, | 519 if any of them isn't found. |
520 especially the compilation commands. It might be more convenient to | 520 |
521 unpack the Emacs distribution with djtar, which comes with djgpp; if | 521 If you are building the MSDOG version of Emacs on an MSDOG-like system |
522 you do `SET LFN=n' before unpacking, djtar truncates file names to 8.3 | 522 which supports long file names (e.g. Windows 95), you need to make |
523 naming as it extracts files, even if the system allows long file | 523 sure that long file names are handled consistently both when you |
524 names, and this ensures that build procedures designed for 8.3 file | 524 unpack the distribution and compile it. If you intend to compile with |
525 names still work. Use djtar with the command `djtar -x foo.tar' or | 525 DJGPP v2.0 or later, and long file names support is enabled (LFN=y in |
526 `djtar -x foo.tgz'. | 526 the environment), you need to unpack Emacs distribution in a way that |
527 | 527 doesn't truncate the original long filenames to the DOS 8.3 namespace; |
528 Some users report that running Emacs 19.29 requires dpmi memory | 528 the easiest way to do this is to use djtar program which comes with |
529 management. We do not know why this is so, since 19.28 did not need | 529 DJGPP, since it will note the LFN setting and behave accordingly. |
530 it. If we find out what change introduced this requirement, we may | 530 DJGPP v1 doesn't support long filenames, so you must unpack Emacs with |
531 try to eliminate it. ("May" because perhaps djgpp version 2's | 531 a program that truncates the filenames to 8.3 naming as it extracts |
532 improved dpmi handling means this is no longer a problem.) | 532 files; again, using djtar after setting LFN=n is the recommended way. |
533 | 533 You can build Emacs with LFN=n even if you use DJGPP v2, if some of |
534 It is possible that this problem happens only when there is not enough | 534 your tools don't support long file names: just ensure that LFN is set |
535 physical memory on the machine. | 535 to `n' during both unpacking and compiling. |
536 | 536 |
537 You can find out if you have a dpmi host by running go32 (part of | 537 (By the time you read this, you have already unpacked the Emacs |
538 djgpp) without arguments; it will tell you if it uses dpmi memory. | 538 distribution, but if the explanations above imply that you should have |
539 For more information about dpmi memory, consult the djgpp FAQ. | 539 done it differently, it's safer to delete the directory tree created |
540 | 540 by the unpacking program and unpack Emacs again, than to risk running |
541 To build and install Emacs, type these commands: | 541 into problems during the build process.) |
542 | |
543 It is important to understand that the runtime support of long file | |
544 names by the Emacs binary is NOT affected by the LFN setting during | |
545 compilation; Emacs compiled with DJGPP v2.0 or later will always | |
546 support long file names on Windows 95 no matter what was the setting | |
547 of LFN at compile time. | |
548 | |
549 To unpack Emacs with djtar, type this command: | |
550 | |
551 djtar -x emacs.tgz | |
552 | |
553 (This assumes that the Emacs distribution is called `emacs.tgz' on | |
554 your system.) There are a few files in the archive whose names | |
555 collide with other files under the 8.3 DOS naming. If you have set | |
556 LFN=n, djtar will ask you to supply alternate names for these files; | |
557 you can just press `Enter' when this happens (which makes djtar skip | |
558 these files) because they aren't required for MS-DOS. | |
559 | |
560 When unpacking is done, a directory called `emacs-XX.YY' will be | |
561 created, where XX.YY is the Emacs version. To build and install | |
562 Emacs, chdir to that directory and type these commands: | |
542 | 563 |
543 config msdos | 564 config msdos |
544 make install | 565 make install |
545 | 566 |
546 Building Emacs creates executable files in the src and lib-src | 567 Building Emacs creates executable files in the src and lib-src |
547 directories. Installing Emacs on MSDOS moves these executables to a | 568 directories. Installing Emacs on MSDOS moves these executables to a |
548 sibling directory called bin. For example, if you build in directory | 569 sibling directory called bin. For example, if you build in directory |
549 /emacs, installing moves the executables from /emacs/src and | 570 /emacs, installing moves the executables from /emacs/src and |
550 /emacs/lib-src to the directory /emacs/bin, so you can then delete the | 571 /emacs/lib-src to the directory /emacs/bin, so you can then delete the |
551 subdirectories /emacs/src and /emacs/lib-src if you wish. The only | 572 subdirectories /emacs/src and /emacs/lib-src if you wish. The only |
552 subdirectories you need to keep are bin, lisp, etc and info. | 573 subdirectories you need to keep are bin, lisp, etc and info. The bin |
574 subdirectory should be added to your PATH. The msdos subdirectory | |
575 includes a PIF and an icon file for Emacs which you might find useful | |
576 if you run Emacs under MS Windows. | |
553 | 577 |
554 Emacs on MSDOS finds the lisp, etc and info directories by looking in | 578 Emacs on MSDOS finds the lisp, etc and info directories by looking in |
555 ../lisp, ../etc and ../info, starting from the directory where the | 579 ../lisp, ../etc and ../info, starting from the directory where the |
556 Emacs executable was run from. You can override this by setting the | 580 Emacs executable was run from. You can override this by setting the |
557 environment variable HOME; if you do that, the directories lisp, etc | 581 environment variable HOME; if you do that, the directories lisp, etc |