From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Dave Pawson" Newsgroups: gmane.emacs.help Subject: INSTALL file. Comments. Date: Sun, 9 Sep 2007 15:29:05 +0100 Message-ID: <711a73df0709090729q5fe13237x5b6faa9d13e151d6@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1189350160 10678 80.91.229.12 (9 Sep 2007 15:02:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 9 Sep 2007 15:02:40 +0000 (UTC) To: "emac list" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Sep 10 01:02:27 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IUVHI-00051G-3R for geh-help-gnu-emacs@m.gmane.org; Mon, 10 Sep 2007 00:29:16 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUNmv-0007Vw-JE for geh-help-gnu-emacs@m.gmane.org; Sun, 09 Sep 2007 10:29:25 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IUNmd-0007UF-PU for help-gnu-emacs@gnu.org; Sun, 09 Sep 2007 10:29:07 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IUNmd-0007Ta-8D for help-gnu-emacs@gnu.org; Sun, 09 Sep 2007 10:29:07 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUNmd-0007TR-30 for help-gnu-emacs@gnu.org; Sun, 09 Sep 2007 10:29:07 -0400 Original-Received: from rv-out-0910.google.com ([209.85.198.190]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IUNmc-0005fl-M5 for help-gnu-emacs@gnu.org; Sun, 09 Sep 2007 10:29:06 -0400 Original-Received: by rv-out-0910.google.com with SMTP id c27so742620rvf for ; Sun, 09 Sep 2007 07:29:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=vk3Q3L3IBhSTW+m6lHXDtuAWUUT0QAOXGS/QjX94kZQ=; b=bQniR7++qOM+Qhit8k5tC/CiJgkaVDHZRX1YHkaU9J3mt0L5WlS2Y2Dt9leIgZeZDhkDDG4eRokRR2vYttMzmdrGYF+RHkPoYxP281CbaNb7pOZIcGBU2FzmeH5+OAGm1Ai7QWQFStBbgVu8UqeQKIDyNv0RSprVhNDirJ8MiCc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Ey1lB0vZretXLLRcOBqbS+kOKmycnJSIH2t1ZBPwC+lb9jxAC+toMoZp8ib71FSXG8SPbHBrpMhBDBfAK0w593zfB3Pg1vwFfF1nkE51DqSDzPfEaRHt8DYehWZCEv9bBPBc7UWVCEYGQYNQLyhj//Ns3hAuxHAiXAsq42bxVhQ= Original-Received: by 10.140.186.18 with SMTP id j18mr1499810rvf.1189348145082; Sun, 09 Sep 2007 07:29:05 -0700 (PDT) Original-Received: by 10.141.3.17 with HTTP; Sun, 9 Sep 2007 07:29:05 -0700 (PDT) Content-Disposition: inline X-Detected-Kernel: Linux 2.6 (newer, 2) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:47402 Archived-At: To take proper advantage of Emacs 21's mule-unicode charsets, This in the 22.1 version of emacs INSTALL file. To take proper advantage of Emacs 21's mule-unicode charsets, you need a suitable font. For `Unicode' (ISO 10646) fonts for X, see (packaged in Debian), No mention of debian/.deb on that page. (packaged in Debian). Ditto, no mention of a debian package. General comment re fonts: No intimation of how emacs finds fonts, nor how they should be installed, either within the emacs code or how they are accessed from the system font locations. Further mentions of emacs 21 are made. e.g. On Debian, the packages necessary to build the installed version should be sufficient; they can be installed using `apt-get build-dep emacs21' in Debian 3 and above. quote. 3) You can build Emacs in the top-level Emacs source directory or in a separate directory. 3a) To build in the top-level Emacs source directory, go to that directory and run the program `configure' as follows: ./configure [CONFIGURATION-NAME] [--OPTION[=VALUE]] ... Since there is a 'src' directory for source, perhaps a more accurate description would be 3) You can build Emacs in the top-level Emacs INSTALLTION directory or in a separate directory. 3a) To build in the top-level Emacs source directory, go to that directory and run the program `configure' as follows: ./configure [CONFIGURATION-NAME] [--OPTION[=VALUE]] ... quote. If you don't want X support, specify `--with-x=no'. If you omit this option, `configure' will try to figure out for itself whether your system has X, and arrange to use it if present. Not strictly true? X is only used if the dev libraries are present? My (as built) system had X, but no dev libraries. quote. To get more attractive menus, you can specify an X toolkit when you configure Emacs; use the option `--with-x-toolkit=TOOLKIT', Is that the whole story? Isn't it for more than 'attractive menus'? I.e. since there is no default (mentioned in INSTALL) am I right in thinking I'll build the nox version without this option? Says, Use --without-sound to disable sound support. No mention of the --with-sound=yes option that was mentioned by a couple of people? quote. If the description of the system configuration printed by `configure' is not right, or if it claims some of the features or libraries are not available when you know they are, look at the `config.log' file for the trace of the failed tests performed by `configure' to check whether these features are supported. This doesn't cover the case where the libraries are missing? Perhaps a note to indicate, for instance, what to look for when configure failed to find a library? Or even a simple statement, that, for instance 'nox will be built, since no X headers found' or some such? quote. 3b) To build in a separate directory, go to that directory and run the program `configure' as follows: SOURCE-DIR/configure CONFIGURATION-NAME [--OPTION[=VALUE]] ... I'm not clear what is happening here. It *seems* to generate enough files to run make in the 'current' directory? I can run make from there quite happily? Does this mean that having built it, I can delete SOURCE-DIR completely? Would be useful if I've done a make install? This just for clarification. quote. 7) Run `make' in the top directory of the Emacs distribution This isn't true if I've run configure from another directory? Suggest "Run 'make' from the directory in which you ran 'configure'" quote. 8) Check the file `dir' in your site's info directory (usually /usr/local/share/info) to make sure that it has a menu entry for the Emacs info files. suggest adding how this might be done? $cat /usr/local/share/info/dir | grep Emacs: should show something like $ cat /usr/local/share/info/dir |grep Emacs: * Emacs: (emacs). The extensible self-documenting text quote. You can change where the build process installs Emacs and its data files by specifying values for `make' variables as part of the `make' command line. I think this needs disambiguating from the configure param --prefix='/wherever/to/install' I'm unclear what the difference is? One places 'source' files ready for the build process, the other executable (and other files used during execution perhaps) quote. `archlibdir' indicates where Emacs installs and expects the executable files and other architecture-dependent data it uses while running. Its default value, based on `libexecdir' (which see), Is that a typo? Xref missing? Nice to have feature: Re MAKE VARIABLES It would be nice to see guidance for users putting 'another' emacs on their system, perhaps to say how all the variables can be set such that the new values point to some non-standard location and it's subdirectories therefrom? No comments on the dos versions. Not used. HTH -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk