1 \input texinfo @c -*-texinfo-*-
2 @setfilename INSTALL.info
3 @settitle INSTALL - compiling and installing GNU LilyPond
6 <!--- @@WEB-TITLE@@=Installation Instructions --->
14 @chapter INSTALL - compiling and installing GNU LilyPond
17 This document describes how to build LilyPond on Unix platforms. It is
18 also known to run and compile on Windows NT/95/98 as well. More
19 information on this topic can be found at the
20 @uref{http://www.lilypond.org/gnu-windows/, LilyPond on Windows page}.
24 <a name="download-source">
29 Even numbered versions are `stable'. The webpages for the stable version
30 (1.2) reside @uref{http://www.gnu.org/software/lilypond, on the GNU
31 servers}. Big enhancements go into the latest odd numbered version
32 (1.3), whose webpages are on @uref{http://www.lilypond.org/,the lilypond
35 @subsection Source code
37 If you want to compile LilyPond from source, download here:
39 @item Download development releases from
40 @c Hmm, these won't show up in lilypond.org/stats
41 @c Otoh, lilypond.org is not updated when release mail arrives
42 @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/} by FTP and
43 @uref{http://ftp.cs.uu.nl/pub/GNU/LilyPond/}, by HTTP.
44 @item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror)
45 @item at @code{lilypond.org}
46 @uref{ftp://ftp.lilypond.org/pub/LilyPond/} by FTP and
47 @uref{http://www.lilypond.org/ftp/} by HTTP.
50 Of course, if your platform supports LilyPond, such as Debian GNU/Linux,
51 FreeBSD, OpenBSD or NetBSD, you're encouraged to use the native build
54 For Red Hat Linux and SuSE Linux, @file{.spec} files are included in the
55 tarball; see instructions below.
58 <a name="download-binaries">
63 @subsection Precompiled binaries
65 If you want to track bleeding edge development, try:
68 @item @uref{ftp://ftp.debian.org/debian/pool/main/l/lilypond/, Debian
69 GNU/Linux} usually has the latest binaries for the most useful stable
70 and development versions, while
71 @item @uref{http://rpmfind.net/linux/mandrake/cooker/contrib/RPMS/,
72 Mandrake Cooker} also provides fairly recent versions.
75 Binaries are made available for other popular platforms, but as we need
76 to compile them ourselves, they are not updated for every version
80 @item @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/RedHat/RPMS/, Red Hat i386}
81 @item @uref{ftp://ftp.lilypond.org/pub/LilyPond/binaries/SuSE, SuSE}
82 @item @uref{ftp://ftp.lilypond.org/pub/LilyPond/binaries/linuxppc/,
85 @uref{http://www.lilypond.org/gnu-windows/, Windows}
90 There are two options for upgrading sources.
93 @item if you have an unpacked source tree of a previous version, you
96 @emph{If you upgrade by patching do remember to rerun autoconf after
99 @item if you have the @code{.tar.gz} file of a previous release, you can
101 @uref{ftp://ftp.xcf.berkeley.edu/pub/xdelta/, xdelta}.
102 This is much safer than using patches, and is the recommended way.
104 The following command produces @file{lilypond-1.4.3.tar.gz} from
105 @file{lilypond-1.4.2.tar.gz} identical (up to compression dates) to the .3
108 xdelta patch lilypond-1.4.2-1.4.3.xd lilypond-1.4.2.tar.gz
112 @section Requirements
114 @subsection Compilation
116 You need the following packages to compile Lilypond.
119 @item A reasonably new C++ compiler: EGCS 1.1, GCC 2.95.2 or
120 newer. Check out @uref{ftp://ftp.gnu.org/gnu/gcc/, the gcc site}.
123 Check out @uref{http://www.python.org, the python website}.
125 @item GUILE 1.3.4 or newer, check out
126 @uref{http://www.gnu.org/software/guile/guile.html,the GUILE webpage}.
127 Version 1.4 is recommended for better performance.
131 @uref{ftp://ftp.gnu.org/gnu/make/, the GNU
134 @item Flex (version 2.5.4a or newer).
135 Check out @uref{http://www.gnu.org/software/flex/,the Flex webpage}.
137 @item Bison (version 1.25 or newer).
138 Check out @uref{http://www.gnu.org/software/bison/,the bison webpage}
142 @TeX{} is used as an output backend.
144 Also, @TeX{}'s libkpathsea is used to find the fonts (@file{.mf}, @file{.afm}, @file{.tfm}).
145 Make sure you have tetex 1.0 or newer (1.0.6 is known to work). You may
146 need to install a tetex-devel or tetex-dev package too.
148 @item Texinfo (version 4.0 or newer).
149 The documentation of lily is written in texinfo. Check out
150 @uref{ftp://ftp.gnu.org/gnu/texinfo/,the texinfo FTP directory}.
152 @item The geometry package for LaTeX is needed to use ly2dvi.
154 @uref{ftp://ftp.ctan.org/tex-archive/macros/latex/contrib/supported/geometry,the
155 FTP directory for @code{geometry}}. This package is normally included
156 with the @TeX{} distribution.
158 @item MetaPost, needed for generating PostScript fonts. Please
159 note that tetex-0.4pl8 (included with Red Hat 5.x) does not include
160 @file{mfplain.mp}, which is needed for producing the scalable font
163 If you don't have MetaPost and don't want to use PostScript output, then
164 edit @file{mf/GNUmakefile}, removing the line saying @code{PFA_FILES=}.
166 @item kpathsea, a library for searching (@TeX{}) files. @code{kpathsea} is
167 usually included with your installation of @TeX{}. You may need to install
168 a tetex-devel or tetex-dev package too.
170 In the very unlikely case that kpathsea is not available for your
171 platform (ie, you're not running GNU/Linux, Windows, or any recent
172 UNIX), you can compile LilyPond without kpathsea support. In that case,
173 you'll probably have to indicate where @TeX{}'s tfm files live. Invoke
174 configure something like:
177 ./configure --without-kpathsea --enable-tfm-path=/usr/share/texmf/fonts/tfm/public/cm/:/usr/share/texmf/fonts/tfm/ams/symbols
182 @subsection Running requirements
184 GNU LilyPond does use a lot of resources. For operation you need the
189 @item Xdvi and Ghostscript
190 @item GUILE 1.3.4, or newer. Check out
191 @uref{http://www.gnu.org/software/guile.html,the GUILE webpage}
194 For running LilyPond successfully you have to help @TeX{} and MetaFont find
195 various files. The recommended way of doing so is adjusting the
196 environment variables in the start-up scripts of your shell. Appropriate
197 Csh and bourne sh scripts are left in
198 @file{buildscripts/out/lilypond-profile} and
199 @file{buildscripts/out/lilypond-login} after compilation.
201 LilyPond is a big and slow program. A fast CPU and plenty of RAM is
202 recommended for comfortable use.
204 @subsection Website requirements
206 The documentation comes in the form of a website. You can view this
207 website on the internet, but you can also build it locally. This process
208 requires a successful compile of lilypond. The website is built
216 Building the website requires some additional tools:
219 @item xpmtoppm (from the netpbm package: the Portable Bitmap Utilities).
221 @uref{ftp://ftp.x.org/contrib/utilities/netpbm-1mar1994.p1.tar.gz,the
224 @item pnmtopng. The original is
226 @uref{ftp://swrinde.nde.swri.edu/pub/png/applications/pnmtopng-2.37.2.tar.gz,in
227 the pnmtopng FTP site}.
229 @item @uref{http://www.lri.fr/~filliatr/ftp/bibtex2html/, Bibtex2html}, or
230 @uref{http://www.uni-koblenz.de/ag-ki/ftp/bib2html/, Bib2html}.
231 Bibtex2html is available in debian, while bib2html is in some rpm based
233 Bib2html, in turn depends on man2html for proper installation.
234 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}.
236 The website will build without bib converter utility, but you will not
237 see our hypertextified bibliography.
239 @item texinfo (a development release)
240 The documentation will build with texinfo-4.0, but if you want split
241 html pages, you're best off using the lates pretest version from
242 @uref{ftp://texinfo.org/texinfo/pretests/texinfo-4.0b.tar.gz,
244 @uref{ftp://alpha.gnu.org/gnu/texinfo-4.0b.tar.gz,texinfo-4.0b}
247 @section Building LilyPond
249 to install GNU LilyPond, type:
251 gunzip -c lilypond-x.y.z | tar xf -
253 ./configure # run with --help to see appropriate options
256 sh buildscripts/clean-fonts.sh
259 If you are doing an upgrade, you should remove all @file{feta}
260 @code{.pk} and @file{.tfm} files. A script has been provided to do the
261 work for you, see @file{buildscripts/clean-fonts.sh}.
264 If you are not root, you should choose a @code{--prefix} argument that
265 points into your home directory, eg.
268 ./configure --prefix=$HOME/usr
272 In this case, you have to insert the contents of
273 @code{buildscripts/out/lilypond-login} or
274 @code{buildscripts/out/lilypond-profile} into your start up scripts by
279 @subsection Configuring for multiple platforms
281 If you want to build multiple versions of LilyPond with different
282 configuration settings, you can use the @code{--enable-config=CONF}
283 option of configure. You should use @samp{make conf=CONF} to generate
284 the output in @file{out-CONF}. Example: suppose I want to build with
285 and without profiling. Then I'd use the following for the normal build,
288 ./configure --prefix=~ --enable-checking
293 and for the profiling version, I specify a different configuration.
297 ./configure --prefix=~ --enable-profiling --enable-config=prof --disable-checking
299 make conf=prof install
309 An Emacs mode for entering music and running LilyPond is included with
310 the source archive as @file{lilypond-mode.el} and
311 @file{lilypond-font-lock.el}. You should install these files somewhere
312 in your @var{load-path}. If you have installed a precompiled LilyPond
313 package, these files can be found in
314 @file{/usr/share/doc/lilypond-x.y.z/}.
316 Add this to your @file{~/.emacs} or @file{~/.emacs.el}, or install this
317 file in Emacs' @file{site-start.d}:
319 ;;; lilypond-init.el --- Startup code for LilyPond mode
321 (load-library "lilypond-mode.el")
322 (setq auto-mode-alist
323 (cons '("\\.ly$" . LilyPond-mode) auto-mode-alist))
324 (add-hook 'LilyPond-mode-hook (lambda () (turn-on-font-lock)))
327 If you have the latest LilyPond-1.4.x Debian package, LilyPond-mode is
328 automatically loaded, you not even need to modify your @code{~/.emacs}
331 @section Compiling for distributions
333 @subsection Red Hat Linux
335 Red Hat 7.0 i386 RPMS are available from
336 @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
338 You can also compile them yourself. A spec file is in
339 @file{make/out/lilypond.redhat.spec}. This file is distributed along
340 with the sources. You can make the rpm by issuing
343 tar xfz lilypond-x.y.z.tar.gz
344 rpm -bb lilypond-x.y.z/make/out/lilypond.redhat.spec
345 rpm -i /usr/src/redhat/RPMS/i386/lilypond-x.y.z
349 For running on a Red Hat system you need these packages: guile, tetex,
350 tetex-latex, tetex-dvips, libstdc++, python, ghostscript.
352 For compilation on a Red Hat system you need these packages, in addition
353 to the those needed for running: glibc-devel, gcc-c++, libstdc++-devel,
354 guile-devel, flex, bison, texinfo, tetex-devel, groff,
361 Some LinuxPPC RPMS should available from
362 @uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
364 A LinuxPPC RPM can be made using the @file{lilypond.redhat.spec} file.
368 Some SUSE RPMS should available from
369 @uref{ftp://ftp.lilypond.org/pub/LilyPond/binaries/SuSE}.
371 You can also compile a RPM for SUSE yourself. A spec file is in
372 @file{make/out/lilypond.suse.spec}, see the instructions for building
375 You must have the following packages: guile tcsh tetex te_latex te_kpath
376 te_mpost libpng python gpp libgpp gettext autoconf netpbm libnetpb
377 gs_serv gs_lib gs_fonts guile
379 @subsection Slackware
381 No precompiled packages for Slackware are available.
383 Problems have been reported with Slackware 7.0; apparently, it ships
384 with a faulty compiler. Do not compile LilyPond with -O2 on this
389 Some binaries are available at rpmfind.net. Refer to
390 @uref{http://rpmfind.net/linux/mandrake/cooker/contrib/RPMS/}.
392 You can also compile a RPM for Mandrake yourself. A spec file is in
393 @file{make/out/lilypond.mandrake.spec}, see the instructions for building
396 @subsection Debian GNU/Linux
398 A Debian package is also available. You may install it easily by running
399 @command{apt-get} as root:
402 apt-get install lilypond lilypond-doc
405 You can also compile the .deb for Debian yourself, do:
408 apt-get -b source lilypond
411 If you're real impatient, you may even do:
414 cd lilypond-x.y.z # a previous version
415 uscan # download and build latest directly from upstream
419 Debian's @TeX{} installation is a bit short on memory, you may want to
420 increase it like this:
422 --- /etc/texmf/texmf.cnf.dpkg Sun Jan 28 14:12:14 2001
423 +++ /etc/texmf/texmf.cnf Fri Apr 27 11:09:35 2001
425 main_memory.context = 1500000
426 main_memory.mpost = 1000000
427 main_memory = 263000 % words of inimemory available; also applies to inimf&mp
428 -extra_mem_top = 0 % extra high memory for chars, tokens, etc.
429 -extra_mem_bot = 0 % extra low memory for boxes, glue, breakpoints, etc.
430 +extra_mem_top = 100000 % extra high memory for chars, tokens, etc.
431 +extra_mem_bot = 100000 % extra low memory for boxes, glue, breakpoints, etc.
433 obj_tab_size.context = 256000
437 You could also export @env{extra_mem_top} and @env{extra_mem_bot} as
438 environment variables if you do not want to or cannot modify
439 @file{/etc/texmf/texmf.cnf}.
444 @item @uref{http://packages.debian.org/lilypond,http://packages.debian.org/lilypond}
445 @item @uref{http://people.debian.org/~foka/lilypond/,http://people.debian.org/~foka/lilypond/}
446 for latest semi-unofficial build of LilyPond 1.4.2 for Debian 2.2 (potato) users.
447 The official stable Debian 2.2 is stuck with the old LilyPond-1.3.24.
448 Since LilyPond-1.4 has been released, the older lilypond1.3 Debian
449 package is now obsolete.
452 Please contact Anthony Fok @email{lilypond@@packages.debian.org} for more
455 The build scripts are in the subdirectory @file{debian/}; you can
456 make the .deb by doing, for example:
460 # dpkg --purge lilypond lilypond1.3
462 $ tar xzf lilypond-1.4.3.tar.gz
464 $ dch -p -v 1.4.3-0.local.1 "Local build."
467 # dpkg -i ../lilypond_1.4.3*.deb
472 Use command @command{debuild} instead of @command{debuild -B} if you have
473 a very fast machine and want to build the HTML, PS and DVI documentation
476 For compilation on a Debian GNU/Linux system you need these packages,
477 in addition to the those needed for running:
480 @item g++, cpp, libc6-dev, libstdc++<@var{your-libstdc++-version-here}>-dev
481 @item libguile<@var{your-libguile-version-here}>-dev
482 @item make, m4, flex, bison
485 @item bibtex2html (not in Debian 2.2)
486 @item tetex-base, tetex-bin, tetex-extra, libkpathsea-dev or tetex-dev
487 @item dpkg-dev, debhelper, fakeroot
489 @item pnmtopng (only in Debian 2.2; pnmtopng has been merged with netpbm
490 in Debian testing/unstable.)
493 Most of these are listed on the @samp{Build-Depends} line in the
494 @file{debian/control} file. To ensure the creation of the lilypond deb is
495 trouble-free, we recommend that you first install the following packages
496 by running \@command{apt-get} as root before building the package:
501 apt-get install task-debian-devel task-c++-dev \
502 python-base libguile6-dev tetex-bin tetex-dev \
503 tetex-extra flex bison texinfo groff gs \
504 netpbm pnmtopng m4 gettext
507 For Debian in development ("unstable", the future 2.3 or 3.0):
510 apt-get install binutils cpp gcc libc6-dev \
511 g++ libstdc++2.10-dev \
512 python-base libguile-dev tetex-bin libkpathsea-dev \
513 tetex-extra flex bison texinfo bibtex2html groff gs \
517 And, just so that old fonts from previous versions of LilyPond won't
518 interfere with your build, you may want to do this before the build too:
521 dpkg --purge lilypond lilypond1.3
528 For help and questions use @email{lilypond-user@@gnu.org}. Please
529 consult the FAQ before mailing your problems. If you find bugs, please
530 send bug reports to @email{bug-lilypond@@gnu.org}.
532 Bugs that are not fault of LilyPond are documented here.
534 @unnumberedsubsec FLex-2.5.4a and gcc-3.0
536 Flex 2.5.4a does not produce g++-3.0 compliant C++ code. To compile
537 LilyPond with gcc-3.0 you may do:
540 CC=gcc-3.0 CXX=g++-3.0 ./configure --enable-config=gcc-3.0
541 make conf=gcc-3.0 -C lily out-gcc-3.0/lexer.cc
542 patch -p1 < lexer-gcc-3.0.patch
543 make conf=gcc-3.0 -C lily
546 Note that this is fixed in Debian/unstable for flex >= 2.5.4a-13.
548 @unnumberedsubsec NetBSD
551 @item The flex precompiled in NetBSD-1.4.2 is broken.
552 Download flex-2.5.4a, build, install.
554 @item The configuration of Gcc (egcs-2.91.60 19981201 (egcs-1.1.1
555 release)) does not include @file{/usr/pkg} paths. Configure using:
558 CFLAGS='-I /usr/pkg/include' LDFLAGS='-L/usr/pkg/lib' ./configure
564 @unnumberedsubsec Solaris:
567 @item Sparc64/Solaris 2.6, GNU make-3.77
569 GNU make-3.77 is buggy on this platform, upgrade to 3.78.1 or newer.
571 @item Sparc64/Solaris 2.6, ld
577 @unnumberedsubsec AIX
582 The following is from the gcc install/SPECIFIC file.
584 Some versions of the AIX binder (linker) can fail with a relocation
585 overflow severe error when the -bbigtoc option is used to link
586 GCC-produced object files into an executable that overflows the TOC.
587 A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND
588 -BBIGTOC) is available from IBM Customer Support and from its
589 27service.boulder.ibm.com website as PTF U455193.
591 Binutils does not support AIX 4.3 (at least through release 2.9). GNU
592 as and GNU ld will not work properly and one should not configure GCC
593 to use those GNU utilities. Use the native AIX tools which do
594 interoperate with GCC.
597 add -Wl,-bbigtoc to USER_LDFLAGS, ie:
599 LDFLAGS='-Wl,-bbigtoc' ./configure