First, bug in parser.yy that older bison's let slip through, but bison-1.49
doesn't much like:
patch -p1 << \EOF
diff -ru lilypond-1.5.69.orig/lily/parser.yy lilypond-1.5.69/lily/parser.yy
--- lilypond-1.5.69.orig/lily/parser.yy 2002-07-22 03:21:58.000000000 -0700
+++ lilypond-1.5.69/lily/parser.yy 2002-07-30 10:20:17.000000000 -0700
@@ -1974,7 +1974,7 @@
chord_notes:
chord_step {
- $$ = $1
+ $$ = $1;
}
| chord_notes '.' chord_step {
$$ = gh_append2 ($$, $3);
EOF
Second, it would be extremely nice if lilypond's configure would handle
building in a separate build directory. I.e.,
tar xzf lilypond-1.5.69.tar.gz
mkdir lilypond-1.5.69-x86-build
cd lilypond-1.5.69-x86-build
../lilypond-1.5.69/configure
make
This is standard practice for most other GNU programs, and makes it nice to
be able to share sources for multiple platforms. It also makes it easier
for those of use that have created a build infrastructure that expects GNU
software to build like this.
With lilypond, it fails in mysterious ways. Even doing something like:
cd lilypond-1.5.69
../lilypond-1.5.69/configure
make
That is, running configure in the source dir, just with an unusual path,
fails.
mv parmesan26.log parmesan26.tfm /usr/src/lilypond/lilypond-1.5.69-build//mf/out
rm parmesan26.*gf
/usr/bin/python ../lilypond-1.5.69/buildscripts/mf-to-table.py
--package=/usr/src/lilypond/lilypond-1.5.69/mf
--outdir=/usr/src/lilypond/lilypond-1.5.69-build//mf/out --dep
/usr/src/lilypond/lilypond-1.5.69-build//mf/out/feta11.dep --afm
/usr/src/lilypond/lilypond-1.5.69-build//mf/out/feta11.afm --enc
/usr/src/lilypond/lilypond-1.5.69-build//mf/out/feta11.enc --tex
/usr/src/lilypond/lilypond-1.5.69-build//mf/out/feta11.tex --ly
/usr/src/lilypond/lilypond-1.5.69-build//mf/out/feta11list.ly
/usr/src/lilypond/lilypond-1.5.69-build//mf/out/feta11.log
/usr/bin/python: can't open file '../lilypond-1.5.69/buildscripts/mf-to-table.py'
make[2]: *** [/usr/src/lilypond/lilypond-1.5.69-build//mf/out/feta11.tex] Error 2
make[2]: Leaving directory `/usr/src/lilypond/lilypond-1.5.69/mf'
Please note two things:
First, it should be using ../../lilypond-....py
Second, why is it building anything in /lilypond-1.5.69/ when it should be
in /lilypond-1.5.69-build/ ?
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
