Abstract
========
- TODO: document xdeltas
-
This document explains what you need to install LilyPond, and what
you should do. If you are going to compile and install LilyPond often,
e.g. when doing development, you might want to check out the
_If you upgrade by patching do remember to rerun autoconf after
applying the patch_.
+ If you do not want to download the entire archive for each version,
+the safest method for upgrading is to use `xdelta', see
+`ftp://ftp.xcf.berkeley.edu/pub/xdelta/'
+
+ The following command produces `lilypond-1.1.55.tar.gz' from
+`lilypond-1.1.54' identical (up to compression dates) to the .55 on the
+FTP site.
+ xdelta patch lilypond-1.1.54-1.1.55.xd lilypond-1.1.54.tar.gz
+
Prerequisites
=============
compile if you use debugging information. If you are short on
disk-space run configure with `--disable-debugging'.
- Although we recommend to use Unix, LilyPond is known to run on
+ * Although we recommend to use Unix, LilyPond is known to run on
Windows NT/95/98 as well. See Section Windows NT/95,es.
- * EGCS 1.1 or newer. Check out ftp://ftp.gnu.org/pub/gcc/
- (ftp://ftp.gnu.org/pub/gcc/)
+ * EGCS 1.1 or newer. Check out `ftp://ftp.gnu.org/pub/gcc/'.
- * Python 1.5, Check out ftp://ftp.python.org (ftp://ftp.python.org)
- or ftp://ftp.cwi.nl/pub/python (ftp://ftp.cwi.nl/pub/python).
+ * Python 1.5, Check out `ftp://ftp.python.org' or
+ `ftp://ftp.cwi.nl/pub/python'.
* GUILE 1.3, check out http://www.gnu.org/software/guile/guile.html
(http://www.gnu.org/software/guile/guile.html).
* Doc++ (optional) to read the source code.
- You also have to install `buildscripts/out/ps-to-gifs' in a
-directory that is in the path.
-
configuring and compiling
=========================
/usr/local/man/man1/lilypond.1
/usr/local/bin/lilypond
/usr/local/bin/mi2mu
+ /usr/local/bin/convert-mudela
+ /usr/local/bin/mudela-book
+ /usr/local/bin/abc2ly
/usr/local/share/lilypond/*
/usr/local/share/locale/{it,nl}/LC_MESSAGES/lilypond.mo
`.pk' and `.tfm' files of the fonts. A script has been provided to do
the work for you, see `bin/clean-fonts.sh'.
-CAVEATS
-=======
-
- * The -O2 option triggers bugs on various platforms (PowerPC,
- Alpha). If you experience problems, you should first try
- turning off this.
-
- * On PPC you need at least EGCS-1.1.2f.
-
Redhat linux
============
Separate instructions on building for W32 are available; See file
README-W32, included with the sources.
-Bugs
-====
+Problems
+========
+
+ For help and questions use <help-gnu-music@gnu.org> and
+<gnu-music-discuss@gnu.org>. Please consult the faq before mailing
+your problems.
+
+ If you find bugs, please send bug reports to <bug-gnu-music@gnu.org>.
+
+ Known bugs that are LilyPond's fault are listed in `TODO', or
+demonstrated in `input/bugs/'.
+
+ Known bugs that are not LilyPond's fault are documented here.
+
+All platforms
+*************
+
+*GUILE 1.3.2
+ Guile 1.3.2 is buggy in several respects. Do not use it for
+ LilyPond.
+
+LinuxPPC Bugs:
+**************
+
+*R5, egcs-1.1.2-12c
+ Egcs-1.1.2-12c (stock LinuxPPC R5) has a serious bug, upgrade to
+ fixed in egcs-1.1.2-12f or gcc-2.95-0a,
+ `ftp://dev.linuxppc.org/users/fsirl/R5/RPMS/ppc/'
+
+*R4, egcs-1.0.2
+ All compiling with `-O2' is suspect, in particular guile-1.3, and
+ Lily herself will break.
+
+Linux-i386
+**********
+
+*SuSE6.2 and similar platforms (glibc 2.1, libstdc++ 2.9.0)
+ Lily will crash during parsing (which suggests a C++ library
+ incompatibility). Precise cause, precise platform description or
+ solution are not known.
+
+ Note that this only happens on some computers with the said
+ platform.
+
+*GUILE
+ A binary RPM of Guile 1.3 has been distributed from the LilyPond
+ ftp site. This binary was made in RedHat 5.x, and it will fail if
+ this RPM is used with RedHat 6.x.
+
+*libg++ 2.7
+ LilyPond occasionally crashes while parsing the initialisation
+ files. This is a very obscure bug, and usually entering the
+ commandline differently "fixes" it.
+
+ lilypond input.ly
+
+ and
+ lilypond -I. ./input.ly
+ makes a difference
+
+ Typical stacktrace:
+ SIGSEGV
+ __libc_malloc (bytes=16384)
+ ?? ()
+ yyFlexLexer::yy_create_buffer ()
+ Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
+
+ This behaviour has been observed with machines that have old libg++
+ versions (LinuxPPC feb '98, RedHat 4.x).
+
+Solaris:
+********
+
+*Sparc64/Solaris 2.6, GNU make-3.77
+ GNU make-3.77 is buggy on this platform, upgrade to 3.78.1 or
+ newer.
+
+*Sparc64/Solaris 2.6, ld
+ Not yet resolved.
+
+AIX
+***
+
+*AIX 4.3 ld
+ The following is from the gcc install/SPECIFIC file.
+ Some versions of the AIX binder (linker) can fail with a
+ relocation overflow severe error when the -bbigtoc option
+ is used to link GCC-produced object files into an
+ executable that overflows the TOC. A fix for APAR IX75823
+ (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
+ available from IBM Customer Support and from its
+ 27service.boulder.ibm.com website as PTF U455193.
+
+ Binutils does not support AIX 4.3 (at least through release
+ 2.9). GNU as and GNU ld will not work properly and one
+ should not configure GCC to use those GNU utilities. Use
+ the native AIX tools which do interoperate with GCC.
- Send bug reports to bug-gnu-music@gnu.org. For help and questions
-use help-gnu-music@gnu.org and gnu-music-discuss@gnu.org. Please
-consult the faq before mailing your problems.
+ add -Wl,-bbigtoc to USER_LDFLAGS, ie:
+ LDFLAGS='-Wl,-bbigtoc' ./configure
Authors
=======
projects / lilypond.git / blobdiff