lilypond-2.4.2 does not have a ppc (neither ~ppc) keyword at the moment. It compiled without errors on my PPC-machine (G3 iBook 800 MHz). But when I invoke lilypond on an arbitrary source file, I get: GNU LilyPond 2.4.2 Processing `petite-ouverture-a-danser.ly' Parsing... Interpreting music... error: can't find `feta20.afm' Music font has not been installed properly. Aborting This error does not seem PPC-specific to me. Some investigation: # slocate feta20.afm /usr/share/lilypond/2.4.2/fonts/afm/feta20.afm # ls -l /usr/share/lilypond/2.4.2/fonts/afm/feta20.afm -rw-r--r-- 1 root root 9518 Dec 27 23:24 /usr/share/lilypond/2.4.2/fonts/afm/feta20.afm # emerge info Portage 2.0.51-r8 (default-ppc-2004.1, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10 ppc) ================================================================= System uname: 2.6.10 ppc 750FX Gentoo Base System version 1.6.8 Python: dev-lang/python-2.2.2,dev-lang/python-2.3.4 [2.3.4 (#1, Sep 16 2004, 23:11:34)] distcc 2.18.3 powerpc-unknown-linux-gnu (protocols 1 and 2) (default port 3632)[disabled] dev-lang/python: 2.2.2, 2.3.4 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r2, 1.5, 1.9.3, 1.6.3, 1.7.9, 1.4_p6 sys-devel/binutils: 2.15.90.0.3-r3 sys-devel/libtool: 1.5.10-r2 virtual/os-headers: 2.4.18-r2, 2.4.22 ACCEPT_KEYWORDS="ppc ~ppc" AUTOCLEAN="yes" CFLAGS="-O2 -pipe -mcpu=750 -fsigned-char -mpowerpc-gfxopt" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config/usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe -mcpu=750 -fsigned-char -mpowerpc-gfxopt" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks" GENTOO_MIRRORS="ftp://gentoo.inode.at/source/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://gd.tuwien.ac.at/opsys/linux/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib alsa apache2 apm arts audiofile berkdb bitmap-fonts blas bzlib caps cdparanoia crypt cups dba divx4linux doc dvd encode exif f77 flac font-server fortran gcj gd gdbm gif gnome-libs gphoto2 gpm gtk gtk2 guile icq imlib innodb jack jack-tmpfs java jpeg kde ladcca lcms libcaca libwww live lzo mad maildir matroska monkey motif mpeg mysql ncurses nls objc offensive oggvorbis opengl pam pdflib perl png ppc python qt readline samba sasl sdl slang speex spell ssl tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts usb wmf xine xml xml2xmms xprint xv xvid xvmc zlib video_cards_radeon"
I have the same problem with an x86 (pentium4)
From the documentation : 1.1.3 Font problems If you are upgrading from a previous version of LilyPond, be sure to remove all old font files. These include .pk and .tfm files that may be located in /var/lib/texmf, /var/spool/texmf, /var/tmp/texmf or prefix/share/lilypond/fonts/. A script automating this has been included, see buildscripts/clean-fonts.sh. And you must set up some variable (problem for the zsh user) 4.3 Environment variables For processing both the TeX and the PostScript output, the appropriate environment variables must be set. The following scripts do this: * buildscripts/out/lilypond-profile (for SH shells) * buildscripts/out/lilypond-login (for C-shells) They should normally be sourced as part of the login process. If these scripts are not run from the system wide login process, then you must run it yourself. If you use sh, bash, or a similar shell, then add the following to your .profile: . /the/path/to/lilypond-profile If you use csh, tcsh or a similar shell, then add the following to your ~/.login: source /the/path/to/lilypond-login
entering source /usr/share/lilypond/2.4.2/buildscripts/out/lilypond-profile in bash before invoking lilypond fixes the problem, lilypond works fine then. My opinion is that this manual sourcing (or the manual altering of .profile) should not be necessary, lilypond should work "out of the box", as it did in the previous versions. Furthermore, the ~ppc keyword can be added to the ebuild. It existed in older versions, I do not understand why it got erased.
I don't think this is still a problem with lilypond-2.8. If you find it is, please re-open this bug.
