1 \input texinfo @c -*-texinfo-*-
2 @setfilename INSTALL.info
3 @settitle INSTALL - compiling and installing GNU LilyPond
10 @chapter INSTALL - compiling and installing GNU LilyPond
13 This document describes how to build LilyPond on Unix platforms. It is
14 also known to run and compile on Windows NT/95/98 as well. More
15 information on this topic can be found at the
16 @uref{http://www.lilypond.org/gnu-windows/, LilyPond on Windows page}.
20 <a name="download-source">
25 Even numbered versions are `stable'. The webpages for the stable version
26 (1.2) reside @uref{http://www.gnu.org/software/lilypond, on the GNU
27 servers}. Big enhancements go into the latest odd numbered version
28 (1.3), whose webpages are on @uref{http://www.lilypond.org/,the lilypond
31 @subsection source code
34 If you want to compile LilyPond from source, download here:
36 @item Download development releases from
37 @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/} by FTP and
38 @uref{http://ftp.cs.uu.nl/pub/GNU/LilyPond/}, by HTTP.
39 @item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror)
40 @item at @code{lilypond.org}
41 @uref{ftp://ftp.lilypond.org/pub/LilyPond/} by FTP and
42 @uref{http://www.lilypond.org/ftp/} by HTTP.
46 <a name="download-binaries">
53 Binaries are available, but are not updated for every version released.
55 @item @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/RedHat/RPMS/, Red Hat i386}
56 @item @uref{ftp://ftp.lilypond.org/pub/LilyPond/binaries/linuxppc/, LinuxPPC}
57 @item @uref{ftp://ftp.debian.org/debian/pool/main/l/lilypond/, Debian GNU/Linux}
59 @c @uref{http://home.austin.rr.com/jbr/jeff/lilypond/, Windows Stable}
60 @c @item @uref{ftp://ftp.lilypond.org/pub/lilypond/gnu-windows, Windows
62 @uref{http://www.lilypond.org/gnu-windows/, Windows Testing}
68 There are two options for upgrading sources.
71 @item if you have an unpacked source tree of a previous version, you
74 @emph{If you upgrade by patching do remember to rerun autoconf after
77 @item if you have the @code{.tar.gz} file of a previous release, you can
79 @uref{ftp://ftp.xcf.berkeley.edu/pub/xdelta/, xdelta}.
80 This is much safer than using patches, and is the recommended way.
82 The following command produces @file{lilypond-1.4.3.tar.gz} from
83 @file{lilypond-1.4.2.tar.gz} identical (up to compression dates) to the .3
86 xdelta patch lilypond-1.4.2-1.4.3.xd lilypond-1.4.2.tar.gz
92 @subsection Compilation
94 You need the following packages to compile Lilypond.
97 @item A reasonably new C++ compiler: EGCS 1.1, GCC 2.95.2 or
98 newer. Check out @uref{ftp://ftp.gnu.org/gnu/gcc/, the gcc site}.
101 Check out @uref{http://www.python.org, the python website}.
103 @item GUILE 1.3.4 or newer, check out
104 @uref{http://www.gnu.org/software/guile/guile.html,the GUILE webpage}.
105 Version 1.4 is recommended for better performance.
109 @uref{ftp://ftp.gnu.org/gnu/make/, the GNU
112 @item Flex (version 2.5.4a or newer).
113 Check out @uref{http://www.gnu.org/software/flex/,the Flex webpage}.
115 @item Bison (version 1.25 or newer).
116 Check out @uref{http://www.gnu.org/software/bison/,the bison webpage}
120 @TeX{} is used as an output backend.
122 Also, @TeX{}'s libkpathsea is used to find the fonts (@file{.mf}, @file{.afm}, @file{.tfm}).
123 Make sure you have tetex 1.0 or newer (1.0.6 is known to work). You may
124 need to install a tetex-devel or tetex-dev package too.
126 @item Texinfo (version 4.0 or newer).
127 The documentation of lily is written in texinfo. Check out
128 @uref{ftp://ftp.gnu.org/gnu/texinfo/,the texinfo FTP directory}.
130 @item The geometry package for LaTeX is needed to use ly2dvi.
132 @uref{ftp://ftp.ctan.org/tex-archive/macros/latex/contrib/supported/geometry,the
133 FTP directory for @code{geometry}}. This package is normally included
134 with the @TeX{} distribution.
136 @item MetaPost, needed for generating PostScript fonts. Please
137 note that tetex-0.4pl8 (included with Red Hat 5.x) does not include
138 @file{mfplain.mp}, which is needed for producing the scalable font
141 If you don't have MetaPost and don't want to use PostScript output, then
142 edit @file{mf/GNUmakefile}, removing the line saying @code{PFA_FILES=}.
144 @item kpathsea, a library for searching (@TeX{}) files. @code{kpathsea} is
145 usually included with your installation of @TeX{}. You may need to install
146 a tetex-devel or tetex-dev package too.
148 In the very unlikely case that kpathsea is not available for your
149 platform (ie, you're not running GNU/Linux, Windows, or any recent
150 UNIX), you can compile LilyPond without kpathsea support. In that case,
151 you'll probably have to indicate where @TeX{}'s tfm files live. Invoke
152 configure something like:
155 ./configure --without-kpathsea --enable-tfm-path=/usr/share/texmf/fonts/tfm/public/cm/:/usr/share/texmf/fonts/tfm/ams/symbols
160 @subsection Running requirements
162 GNU LilyPond does use a lot of resources. For operation you need the
167 @item Xdvi and Ghostscript
168 @item GUILE 1.3.4, or newer. Check out
169 @uref{http://www.gnu.org/software/guile.html,the GUILE webpage}
172 For running LilyPond successfully you have to help @TeX{} and MetaFont find
173 various files. The recommended way of doing so is adjusting the
174 environment variables in the start-up scripts of your shell. Appropriate
175 Csh and bourne sh scripts are left in
176 @file{buildscripts/out/lilypond-profile} and
177 @file{buildscripts/out/lilypond-login} after compilation.
179 LilyPond is a big and slow program. A fast CPU and plenty of RAM is
180 recommended for comfortable use.
182 @subsection Website requirements
184 The documentation comes in the form of a website. You can view this
185 website on the internet, but you can also build it locally. This process
186 requires a successful compile of lilypond. The website is built
194 Building the website requires some additional tools:
197 @item xpmtoppm (from the netpbm package: the Portable Bitmap Utilities).
199 @uref{ftp://ftp.x.org/contrib/utilities/netpbm-1mar1994.p1.tar.gz,the
202 @item pnmtopng. The original is
204 @uref{ftp://swrinde.nde.swri.edu/pub/png/applications/pnmtopng-2.37.2.tar.gz,in
205 the pnmtopng FTP site}.
207 @item @uref{http://www.lri.fr/~filliatr/ftp/bibtex2html/, Bibtex2html}, or
208 @uref{http://www.uni-koblenz.de/ag-ki/ftp/bib2html/, Bib2html}.
209 Bibtex2html is available in debian, while bib2html is in some rpm based
211 Bib2html, in turn depends on man2html for proper installation.
212 man2html can be had from @uref{http://askdonald.ask.uni-karlsruhe.de/hppd/hpux/Networking/WWW/Man2html-1.05,http://askdonald.ask.uni-karlsruhe.de/hppd/hpux/Networking/WWW/Man2html-1.05}.
214 The website will build without bib converter utility, but you will not
215 see our hypertextified bibliography.
217 @item texinfo (a development release)
218 The documentation will build with texinfo-4.0, but if you want split
219 html pages, you're best off using the lates pretest version from
220 @uref{ftp://texinfo.org/texinfo/pretests/texinfo-4.0b.tar.gz,
222 @uref{ftp://alpha.gnu.org/gnu/texinfo-4.0b.tar.gz,texinfo-4.0b}
225 @section Building LilyPond
227 to install GNU LilyPond, type:
229 gunzip -c lilypond-x.y.z | tar xf -
231 ./configure # run with --help to see appropriate options
234 sh buildscripts/clean-fonts.sh
237 If you are doing an upgrade, you should remove all @file{feta}
238 @code{.pk} and @file{.tfm} files. A script has been provided to do the
239 work for you, see @file{buildscripts/clean-fonts.sh}.
242 If you are not root, you should choose a @code{--prefix} argument that
243 points into your home directory, eg.
246 ./configure --prefix=$HOME/usr
250 In this case, you have to insert the contents of
251 @code{buildscripts/out/lilypond-login} or
252 @code{buildscripts/out/lilypond-profile} into your start up scripts by
257 @subsection Configuring for multiple platforms
259 If you want to build multiple versions of LilyPond with different
260 configuration settings, you can use the @code{--enable-config=CONF}
261 option of configure. You should use @samp{make conf=CONF} to generate
262 the output in @file{out-CONF}. Example: suppose I want to build with
263 and without profiling. Then I'd use the following for the normal build,
266 ./configure --prefix=~ --enable-checking
271 and for the profiling version, I specify a different configuration.
275 ./configure --prefix=~ --enable-profiling --enable-config=prof --disable-checking
277 make conf=prof install
287 An emacs mode for LilyPond is included with the source archive as
288 @file{lilypond-mode.el} and @file{lilypond-font-lock.el}. If you have
289 an RPM, it is in @file{/usr/share/doc/lilypond-X/}. You have to install
292 Add this to your @file{~/.emacs} or @file{~/.emacs.el}:
294 (load-library "lilypond-mode.el")
295 (setq auto-mode-alist
296 (cons '("\\.ly$" . LilyPond-mode) auto-mode-alist))
297 (add-hook 'LilyPond-mode-hook (lambda () (turn-on-font-lock)))
300 If you have the latest LilyPond-1.4.x Debian package, LilyPond-mode is
301 automatically loaded, so you need not modify your @code{~/.emacs} file.
303 @section Compiling for distributions
305 @subsection Red Hat Linux
307 Red Hat 7.0 i386 RPMS are available from
308 @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
310 You can also compile them yourself. A spec file is in
311 @file{make/out/redhat.spec}. This file is distributed along with the
312 sources. You can make the rpm by issuing
315 tar xfz lilypond-x.y.z.tar.gz
316 rpm -bb lilypond-x.y.z/make/out/redhat.spec
317 rpm -i /usr/src/redhat/RPMS/i386/lilypond-x.y.z
321 For running on a Red Hat system you need these packages: guile, tetex,
322 tetex-latex, tetex-dvips, libstdc++, python, ghostscript.
324 For compilation on a Red Hat system you need these packages, in addition
325 to the those needed for running: glibc-devel, gcc-c++, libstdc++-devel,
326 guile-devel, flex, bison, texinfo, tetex-devel, groff,
332 There appears to be a problem with the Xdvi shipped with Red Hat 7.1.
333 Symptoms: Xdvi responds very sluggishly or hangs while viewing
334 lilypond output. The cause for this problem is unknown; you are advised
335 to recompile Xdvi from source.
340 Some LinuxPPC RPMS should available from
341 @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
343 A LinuxPPC RPM can be made using the @file{redhat.spec} file.
347 Some SUSE RPMS should available from
348 @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
350 You can also compile a RPM for SUSE yourself. A spec file is in
351 @file{make/out/suse.spec}, see the instructions for building the Red Hat
354 You must have the following packages: guile tcsh tetex te_latex te_kpath
355 te_mpost libpng python gpp libgpp gettext autoconf netpbm libnetpb
356 gs_serv gs_lib gs_fonts guile
358 @subsection Slackware
360 No precompiled packages for Slackware are available.
362 Problems have been reported with Slackware 7.0; apparently, it ships
363 with a faulty compiler. Do not compile LilyPond with -O2 on this
368 Some binaries are available at rpmfind.net. Refer to
369 @uref{ftp://ftp.rpmfind.net/linux/Mandrake-devel/cooker/contrib/RPMS/}.
372 @subsection Debian GNU/Linux
374 A Debian package is also available. You may install it easily by running
375 @command{apt-get} as root:
378 apt-get install lilypond lilypond-doc
382 Debian's @TeX{} installation is a bit short on memory, you may want to
383 increase it like this:
385 --- /etc/texmf/texmf.cnf.dpkg Sun Jan 28 14:12:14 2001
386 +++ /etc/texmf/texmf.cnf Fri Apr 27 11:09:35 2001
388 main_memory.context = 1500000
389 main_memory.mpost = 1000000
390 main_memory = 263000 % words of inimemory available; also applies to inimf&mp
391 -extra_mem_top = 0 % extra high memory for chars, tokens, etc.
392 -extra_mem_bot = 0 % extra low memory for boxes, glue, breakpoints, etc.
393 +extra_mem_top = 100000 % extra high memory for chars, tokens, etc.
394 +extra_mem_bot = 100000 % extra low memory for boxes, glue, breakpoints, etc.
396 obj_tab_size.context = 256000
400 You could also export @env{extra_mem_top} and @env{extra_mem_bot} as
401 environment variables if you do not want to or cannot modify
402 @file{/etc/texmf/texmf.cnf}.
407 @item @uref{http://packages.debian.org/lilypond,http://packages.debian.org/lilypond}
408 @item @uref{http://people.debian.org/~foka/lilypond/,http://people.debian.org/~foka/lilypond/}
409 for latest semi-unofficial build of LilyPond 1.4.2 for Debian 2.2 (potato) users.
410 The official stable Debian 2.2 is stuck with the old LilyPond-1.3.24.
411 Since LilyPond-1.4 has been released, the older lilypond1.3 Debian
412 package is now obsolete.
415 Please contact Anthony Fok @email{lilypond@@packages.debian.org} for more
418 The build scripts are in the subdirectory @file{debian/}; you can
419 make the .deb by doing, for example:
423 # dpkg --purge lilypond lilypond1.3
425 $ tar xzf lilypond-1.4.3.tar.gz
427 $ dch -p -v 1.4.3-0.local.1 "Local build."
430 # dpkg -i ../lilypond_1.4.3*.deb
435 Use command @command{debuild} instead of @command{debuild -B} if you have
436 a very fast machine and want to build the HTML, PS and DVI documentation
439 For compilation on a Debian GNU/Linux system you need these packages,
440 in addition to the those needed for running:
443 @item g++, cpp, libc6-dev, libstdc++<@var{your-libstdc++-version-here}>-dev
444 @item libguile<@var{your-libguile-version-here}>-dev
445 @item make, m4, flex, bison
448 @item bibtex2html (not in Debian 2.2)
449 @item tetex-base, tetex-bin, tetex-extra, libkpathsea-dev or tetex-dev
450 @item dpkg-dev, debhelper, fakeroot
452 @item pnmtopng (only in Debian 2.2; pnmtopng has been merged with netpbm
453 in Debian testing/unstable.)
456 Most of these are listed on the @samp{Build-Depends} line in the
457 @file{debian/control} file. To ensure the creation of the lilypond deb is
458 trouble-free, we recommend that you first install the following packages
459 by running \@command{apt-get} as root before building the package:
464 apt-get install task-debian-devel task-c++-dev \
465 python-base libguile6-dev tetex-bin tetex-dev \
466 tetex-extra flex bison texinfo groff gs \
467 netpbm pnmtopng m4 gettext
470 For Debian in development ("unstable", the future 2.3 or 3.0):
473 apt-get install task-debian-devel task-c++-dev \
474 python-base libguile9-dev tetex-bin libkpathsea-dev \
475 tetex-extra flex bison texinfo bibtex2html groff gs \
479 And, just so that old fonts from previous versions of LilyPond won't
480 interfere with your build, you may want to do this before the build too:
483 dpkg --purge lilypond lilypond1.3
490 For help and questions use @email{help-gnu-music@@gnu.org} and
491 @email{gnu-music-discuss@@gnu.org}. Please consult the FAQ before
492 mailing your problems. If you find bugs, please send bug reports to
493 @email{bug-gnu-music@@gnu.org}.
495 Bugs that are not fault of LilyPond are documented here.
497 @unnumberedsubsec NetBSD
500 @item The flex precompiled in NetBSD-1.4.2 is broken.
501 Download flex-2.5.4a, build, install.
503 @item The configuration of Gcc (egcs-2.91.60 19981201 (egcs-1.1.1
504 release)) does not include @file{/usr/pkg} paths. Configure using:
507 CFLAGS='-I /usr/pkg/include' LDFLAGS='-L/usr/pkg/lib' ./configure
513 @unnumberedsubsec Solaris:
516 @item Sparc64/Solaris 2.6, GNU make-3.77
518 GNU make-3.77 is buggy on this platform, upgrade to 3.78.1 or newer.
520 @item Sparc64/Solaris 2.6, ld
526 @unnumberedsubsec AIX
531 The following is from the gcc install/SPECIFIC file.
533 Some versions of the AIX binder (linker) can fail with a relocation
534 overflow severe error when the -bbigtoc option is used to link
535 GCC-produced object files into an executable that overflows the TOC.
536 A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND
537 -BBIGTOC) is available from IBM Customer Support and from its
538 27service.boulder.ibm.com website as PTF U455193.
540 Binutils does not support AIX 4.3 (at least through release 2.9). GNU
541 as and GNU ld will not work properly and one should not configure GCC
542 to use those GNU utilities. Use the native AIX tools which do
543 interoperate with GCC.
546 add -Wl,-bbigtoc to USER_LDFLAGS, ie:
548 LDFLAGS='-Wl,-bbigtoc' ./configure