[EMAIL PROTECTED] writes:
> When using shell other than bash (or a bash restricted to POSIX), make web
> will fail to copy several .png and .ly files to their final destination.
> That's due to the use of the {,,,} globbing feature of bash within
> Documentation/user/GNUMakefile:
>
> -cp -f $(outdir)/*.{png,ly} $(outdir)/lilypond
>
> AFAIK, that globbing is very bash-specific. Fixed in attached
> lilypond-2.1.9.patch.
OK, fixed.
> The third problem is triggered by a bug in bison-1.875:
> compilation fails with "parse error before `goto'" in line
> 4922 due to a bug in bison. To fix, either recompile bison 1.875 with
> the attached bison-1.875.patch or:
Thanks, I've added a note in INSTALL.txt
> Unfortunately, after the failure of potrace, mftrace just continues,
> so does the whole LilyPond build. You'll end up with a running
> (but completely broken) LilyPond. It will vertically displace
> clefs, accidentals, stems, ... see attached lily-1269333678.ly and
> lily-1269333678.png (taken from the last example from section `Notation
> in LilyPond' of the user manual).
>
> Since that bug of mftrace/potrace is hard to find (it tokk me two days),
> it should me mentioned in INSTALL.txt and INSTALL.html, in *bold* face :-)
Actually the potrace "bug" is a non-bug; potrace crashes on empty
characters. What you see is a bug in mftrace .26. Upgrade to .27, and
you should be fine. (using potrace is about 3 times faster than autotrace).
Thanks for your comments and patches, enjoy LilyPond.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
