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{ftp://ftp.lilypond.org/pub/LilyPond/gnu-windows/, LilyPond on Windows
21 <a name="download-source">
26 Even numbered versions are `stable'. The webpages for the stable version
27 (1.2) reside @uref{http://www.gnu.org/software/lilypond, on the GNU
28 servers}. Big enhancements go into the latest odd numbered version
29 (1.3), whose webpages are on @uref{http://www.lilypond.org/,the lilypond
32 @subsection source code
35 If you want to compile LilyPond from source, download here:
37 @item Download development releases from
38 @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/development/} by FTP and
39 @uref{http://ftp.cs.uu.nl/pub/GNU/LilyPond/development/}, by HTTP.
40 @item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror)
41 @item at @code{lilypond.org}
42 @uref{ftp://ftp.lilypond.org/pub/LilyPond/} by FTP and
43 @uref{http://www.lilypond.org/ftp/} by HTTP.
47 <a name="download-binaries">
54 Binaries are available, but are not updated for every version released.
56 @item @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/RedHat/RPMS/, RedHat i386}
57 @item @uref{ftp://ftp.lilypond.org/pub/LilyPond/binaries/linuxppc, LinuxPPC}
59 @uref{ftp://ftp.debian.org/debian/pool/main/l/lilypond,
60 Debian GNU/Linux Stable}
62 @uref{ftp://ftp.debian.org/debian/pool/main/l/lilypond1.3,
63 Debian GNU/Linux Unstable}
64 @item @uref{http://home.austin.rr.com/jbr/jeff/lilypond/, Windows Stable}
65 @c @item @uref{ftp://ftp.lilypond.org/pub/lilypond/gnu-windows, Windows
67 @uref{http://www.lilypond.org/gnu-windows, Windows Testing}
73 There are two options for upgrading sources.
76 @item if you have an unpacked source tree of a previous version, you
79 @emph{If you upgrade by patching do remember to rerun autoconf after
82 @item if you have the @code{.tar.gz} file of a previous release, you can
84 @uref{ftp://ftp.xcf.berkeley.edu/pub/xdelta/, xdelta}.
85 This is much safer than using patches, and is the recommended way.
87 The following command produces @file{lilypond-1.3.122.tar.gz} from
88 @file{lilypond-1.3.121} identical (up to compression dates) to the .122
91 xdelta patch lilypond-1.3.121-1.3.122.xd lilypond-1.3.121.tar.gz
97 @subsection Compilation
99 You need the following packages to compile Lilypond.
102 @item A reasonably new C++ compiler: EGCS 1.1, GCC 2.95.2 or
103 newer. Check out @uref{ftp://ftp.gnu.org/gnu/gcc/, the gcc site}.
106 Check out @uref{http://www.python.org, the python website}.
108 @item GUILE 1.3.4 or newer, check out
109 @uref{http://www.gnu.org/software/guile/guile.html,the GUILE webpage}.
110 Version 1.4 is recommended for better performance.
114 @uref{ftp://ftp.gnu.org/gnu/make/, the GNU
117 @item Flex (version 2.5.4a or newer).
118 Check out @uref{http://www.gnu.org/software/flex/,the Flex webpage}.
120 @item Bison (version 1.25 or newer).
121 Check out @uref{http://www.gnu.org/software/bison/,the bison webpage}
125 @TeX{} is used as an output backend.
127 Also, @TeX{}'s libkpathsea is used to find the fonts (.mf, .afm, .tfm).
128 Make sure you have tetex 1.0 or newer (1.0.6 is known to work). You may
129 need to install a tetex-devel or tetex-dev package too.
131 @item Texinfo (version 4.0 or newer).
132 The documentation of lily is written in texinfo. Check out
133 @uref{ftp://ftp.gnu.org/gnu/texinfo/,the texinfo FTP directory}.
135 @item The geometry package for LaTeX is needed to use ly2dvi.
137 @uref{ftp://ftp.ctan.org/tex-archive/macros/latex/contrib/supported/geometry,the
138 FTP directory for @code{geometry}}. This package is normally included
139 with the @TeX{} distribution.
141 @item MetaPost, needed for generating PostScript fonts. Please
142 note that tetex-0.4pl8 (included with Red Hat 5.x) does not include
143 @file{mfplain.mp}, which is needed for producing the scalable font
146 If you don't have MetaPost and don't want to use PostScript output, then
147 edit @file{mf/GNUmakefile}, removing the line saying @code{PFA_FILES=}.
149 @item kpathsea, a library for searching (TeX) files. @code{kpathsea} is
150 usually included with your installation of TeX. You may need to install
151 a tetex-devel or tetex-dev package too.
153 In the very unlikely case that kpathsea is not available for your
154 platform (ie, you're not running GNU/Linux, Windows, or any recent
155 UNIX), you can compile LilyPond without kpathsea support. In that case,
156 you'll probably have to indicate where @TeX{}'s tfm files live. Invoke
157 configure something like:
160 ./configure --without-kpathsea --enable-tfm-path=/usr/share/texmf/fonts/tfm/public/cm/:/usr/share/texmf/fonts/tfm/ams/symbols
165 @subsection Running requirements
167 GNU LilyPond does use a lot of resources. For operation you need the
172 @item Xdvi and ghostscript
173 @item GUILE 1.3.4, or newer. Check out
174 @uref{http://www.gnu.org/software/guile.html,the GUILE webpage}
177 For running LilyPond successfully you have to help TeX and MetaFont find
178 various files. The recommended way of doing so is adjusting the
179 environment variables in the start-up scripts of your shell. Appropriate
180 Csh and bourne sh scripts are left in
181 @file{buildscripts/out/lilypond-profile} and
182 @file{buildscripts/out/lilypond-login} after compilation.
184 LilyPond is a big and slow program. A fast CPU and plenty of RAM is
185 recommended for comfortable use.
187 @subsection Website requirements
189 The documentation comes in the form of a website. You can view this
190 website on the internet, but you can also build it locally. This process
191 requires a successful compile of lilypond. The website is built
199 Building the website requires some additional tools:
202 @item xpmtoppm (from the netpbm package: the Portable Bitmap Utilities).
204 @uref{ftp://ftp.x.org/contrib/utilities/netpbm-1mar1994.p1.tar.gz,the
207 @item pnmtopng. The original is
209 @uref{ftp://swrinde.nde.swri.edu/pub/png/applications/pnmtopng-2.37.2.tar.gz,in
210 the pnmtopng FTP site}.
212 @item @uref{http://www.lri.fr/~filliatr/ftp/bibtex2html/, Bibtex2html}, or
213 @uref{http://www.uni-koblenz.de/ag-ki/ftp/bib2html/, Bib2html}.
214 Bibtex2html is available in debian, while bib2html is in some rpm based
216 Bib2html, in turn depends on man2html for proper installation.
217 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}.
219 The website will build without bib converter utility, but you will not
220 see our hypertextified bibliography.
224 @section Building LilyPond
226 to install GNU LilyPond, type:
228 gunzip -c lilypond-x.y.z | tar xf -
230 ./configure # run with --help to see appropriate options
233 sh buildscripts/clean-fonts.sh
236 If you are doing an upgrade, you should remove all @file{feta}
237 @code{.pk} and @file{.tfm} files. A script has been provided to do the
238 work for you, see @file{buildscripts/clean-fonts.sh}.
241 If you are not root, you should choose a @code{--prefix} argument that
242 points into your home directory, eg.
245 ./configure --prefix=$HOME/usr
249 In this case, you have to insert the contents of
250 @code{buildscripts/out/lilypond-login} or
251 @code{buildscripts/out/lilypond-profile} into your start up scripts by
256 @subsection Configuring for multiple platforms
258 If you want to build multiple versions of LilyPond with different
259 configuration settings, you can use the @code{--enable-config=CONF}
260 option of configure. You should use @samp{make conf=CONF} to generate
261 the output in @file{out-CONF}. Example: suppose I want to build with
262 and without profiling. Then I'd use the following for the normal build,
265 ./configure --prefix=~ --enable-checking
270 and for the profiling version, I specify a different configuration.
274 ./configure --prefix=~ --enable-profiling --enable-config=prof --disable-checking
276 make conf=prof install
286 An emacs mode for LilyPond is included with the source archive as
287 @file{lilypond-mode.el} and @file{lilypond-font-lock.el}. If you have
288 an RPM, it is in @file{/usr/share/doc/lilypond-X/}. You have to install
291 Add this to your @file{~/.emacs} or @file{~/.emacs.el}:
293 (load-library "lilypond-mode.el")
294 (setq auto-mode-alist
295 (cons '("\\.ly$" . LilyPond-mode) auto-mode-alist))
296 (add-hook 'LilyPond-mode-hook (lambda () (turn-on-font-lock)))
299 If you have the latest LilyPond-1.3.x Debian package, LilyPond-mode is
300 automatically loaded, so you need not modify your @code{~/.emacs} file.
302 @section Compiling for distributions
304 @subsection Red Hat Linux
306 Red Hat 7.0 i386 RPMS are available from
307 @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/RedHat/}.
309 You can also compile them yourself. A spec file is in
310 @file{make/out/redhat.spec}. This file is distributed along with the
311 sources. You can make the rpm by issuing
314 rpm -tb lilypond-x.y.z.tar.gz
315 rpm -i /usr/src/redhat/RPMS/i386/lilypond-x.y.z
319 For running on a Red Hat system you need these packages: guile, tetex,
320 tetex-latex, tetex-dvips, libstdc++, python, ghostscript.
322 For compilation on a Red Hat system you need these packages, in addition
323 to the those needed for running: glibc-devel, gcc-c++, libstdc++-devel,
324 guile-devel, flex, bison, texinfo, tetex-devel, groff,
329 You can also compile them yourself. A spec file is in
330 @file{make/out/suse.spec}. This file is distributed along with the
333 You must have the following packages: guile tcsh tetex te_latex te_kpath
334 te_mpost libpng python gpp libgpp gettext autoconf netpbm libnetpb
335 gs_serv gs_lib gs_fonts guile
341 @subsection Debian GNU/Linux
343 A Debian package is also available. You may install it easily by using
347 apt-get install lilypond1.3
353 @item @uref{http://packages.debian.org/lilypond,http://packages.debian.org/lilypond}
354 @item @uref{http://ftp.debian.org/debian/pool/main/l/lilypond1.3/,http://ftp.debian.org/debian/pool/main/l/lilypond1.3/}
355 for latest package uploaded to Debian unstable;
356 @item @uref{http://people.debian.org/~foka/lilypond/,http://people.debian.org/~foka/lilypond/}
357 for latest semi-unofficial build of LilyPond 1.3.121 for Debian 2.2r2 (potato) users.
358 The official stable Debian 2.2r2 is stuck with the old LilyPond-1.3.24.
361 You may contact Anthony Fok @email{foka@@debian.org} for more information.
363 The build scripts are in the subdirectory @file{debian/}; you can
364 make the .deb by doing, for example:
368 # dpkg --purge lilypond lilypond1.3
370 $ tar xzf lilypond-1.3.122.tar.gz
371 $ cd lilypond-1.3.122
372 $ dch -p -v 1.3.122-0.local.1 "Local build."
375 # dpkg -i ../lilypond1.3_1.3.122*.deb
380 For compilation on a Debian GNU/Linux system you need these packages,
381 in addition to the those needed for running:
384 @item g++, cpp, libc6-dev, libstdc++<your-libstdc++-version-here>-dev
385 @item libguile<your-libguile-version-here>-dev
386 @item make, m4, flex, bison
388 @item groff, texinfo, bibtex2html (not in 2.2r2)
389 @item tetex-base, tetex-bin, tetex-extra, libkpathsea-dev or tetex-dev
390 @item dpkg-dev, debhelper, fakeroot
391 @item gs, netpbm, pnmtopng
394 Most of these are listed on the Build-Depends line in the
395 debian/control file. To ensure the creation of the lilypond deb is
396 trouble-free, we recommend that you first install the following packages
397 before starting dpkg-buildpackage by running apt-get as root.
399 For Debian 2.2 (or 2.2r2, 2.2r3):
402 apt-get install task-debian-devel task-c++-dev \
403 python-base libguile6-dev tetex-bin tetex-dev \
404 tetex-extra flex bison texinfo groff gs \
405 netpbm pnmtopng m4 gettext
408 For Debian in development ("unstable", the future 2.3 or 3.0):
411 apt-get install task-debian-devel task-c++-dev \
412 python-base libguile9-dev tetex-bin libkpathsea-dev \
413 tetex-extra flex bison texinfo bibtex2html groff gs \
414 netpbm pnmtopng m4 gettext
417 And, just so that old fonts from previous versions of LilyPond won't
418 interfere with your build, you may want to do this before the build too:
421 dpkg --purge lilypond lilypond1.3
428 For help and questions use @email{help-gnu-music@@gnu.org} and
429 @email{gnu-music-discuss@@gnu.org}. Please consult the faq before
430 mailing your problems. If you find bugs, please send bug reports to
431 @email{bug-gnu-music@@gnu.org}.
433 Bugs that are not fault of LilyPond are documented here.
435 @unnumberedsubsec NetBSD
438 @item The flex precompiled in NetBSD-1.4.2 is broken.
439 Download flex-2.5.4a, build, install.
441 @item The configuration of Gcc (egcs-2.91.60 19981201 (egcs-1.1.1
442 release)) does not include @file{/usr/pkg} paths. Configure using:
445 CFLAGS='-I /usr/pkg/include' LDFLAGS='-L/usr/pkg/lib' ./configure
451 @unnumberedsubsec Solaris:
454 @item Sparc64/Solaris 2.6, GNU make-3.77
456 GNU make-3.77 is buggy on this platform, upgrade to 3.78.1 or newer.
458 @item Sparc64/Solaris 2.6, ld
464 @unnumberedsubsec AIX
469 The following is from the gcc install/SPECIFIC file.
471 Some versions of the AIX binder (linker) can fail with a relocation
472 overflow severe error when the -bbigtoc option is used to link
473 GCC-produced object files into an executable that overflows the TOC.
474 A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND
475 -BBIGTOC) is available from IBM Customer Support and from its
476 27service.boulder.ibm.com website as PTF U455193.
478 Binutils does not support AIX 4.3 (at least through release 2.9). GNU
479 as and GNU ld will not work properly and one should not configure GCC
480 to use those GNU utilities. Use the native AIX tools which do
481 interoperate with GCC.
484 add -Wl,-bbigtoc to USER_LDFLAGS, ie:
486 LDFLAGS='-Wl,-bbigtoc' ./configure