From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.help Subject: Re: INSTALL file. Comments. Date: Sun, 09 Sep 2007 17:07:56 +0200 Organization: Organization?!? Message-ID: <85odgbq3lf.fsf@lola.goethe.zz> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1189356088 26994 80.91.229.12 (9 Sep 2007 16:41:28 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 9 Sep 2007 16:41:28 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Sep 10 02:41:15 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 1IUWOq-0000yh-TO for geh-help-gnu-emacs@m.gmane.org; Mon, 10 Sep 2007 01:41:09 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUOuM-0003J9-T6 for geh-help-gnu-emacs@m.gmane.org; Sun, 09 Sep 2007 11:41:10 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (gnu/linux) Cancel-Lock: sha1:nOOhVyuAvDPO6YNVBnCPvQlW72s= Original-Lines: 161 Original-NNTP-Posting-Date: 09 Sep 2007 17:07:56 CEST Original-NNTP-Posting-Host: 3e1d0af2.newsspool2.arcor-online.net Original-X-Trace: DXC=ig2mgWIC[T6n`gW2MTm]<3A9EHlD; 3Yc24Fo<]lROoR1<`=YMgDjhg2VOfWc=aZY\71_LiI6ENVa=3>5MOK`; S:bhJ<2jOm5QB6Y\7`K81b7eXaV3 Original-X-Complaints-To: usenet-abuse@arcor.de Original-Xref: shelby.stanford.edu gnu.emacs.help:151894 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:47406 Archived-At: "Dave Pawson" writes: > 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. Is this a joke? Use your package manager to install the package, for example by saying sudo apt-get install unifont on a console, or by clicking System/Administration/Synaptic Package manager or by doing whatever else is done to install a package on your system. It can't be the responsibility of INSTALL to teach you the minimal working steps of your Linux distribution. > (packaged in Debian). > Ditto, no mention of a debian package. apt-cache search efont spews out (among others) xfonts-efont-unicode - /efont/ Unicode fonts for X which cover various scripts xfonts-efont-unicode-ib - /efont/ Unicode fonts for X (italic and bold) and of course, you can get similar information using Synaptic. Again, the Emacs INSTALL file can't be a 101 class on using your distribution. > 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. Because just installing the packages will work. > 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. Wrong. The installation directory is where things get installed. The src directory contains just C sources, which looking at it will corroborate. > 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. Maybe. > 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? No, you'll get a toolkit-less X compilation. > Says, Use --without-sound to disable sound support. > No mention of the --with-sound=yes option that was mentioned > by a couple of people? If you have the development libraries available, they will be used by default. > 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? Why wouldn't it? > 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? Have you actually read the configure output? > 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? Only from there. > Does this mean that having built it, I can delete SOURCE-DIR > completely? You can always delete your source directories after installation if you want to. What is the point of your question? > 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'" Maybe. > 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? It depends on the distribution/info setup. So actually using a text editor is the most portable thing to do. > 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' Maybe one should warn that this should not be interesting for the normal user, but just for package creators. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum