lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

1.5.32 works (also with Guile 1.3.4), .33 and .34 broken


From: Heikki Johannes Junes
Subject: 1.5.32 works (also with Guile 1.3.4), .33 and .34 broken
Date: Wed, 27 Feb 2002 19:52:46 +0200 (EET)

>Yes, see my email entitled "PS output + 1.5.2x + old Guile broken"
>on the bug-lilypond archive from this month. The patch above seems
>to solve my remaining problem, but then my change in tex.scm should
>probably be updated correspondingly.
>
> /Mats

I could compile 1.5.32 in RH7.1 with Guile 1.3.4 and succeeded to use it. 

Instead, in later development versions there was problems.  The problems
in 1.5.34 (which I produced also in 1.5.33 with Guile 1.4 and Mandrake
8.1) have already been described in this mail list. They can be compiled
and installed but they do not produce a proper output.

( ... a cutted trace ...)

Preprocessing elements... 
Calculating column positions... warning: unknown time signature `C'; 
resorting to default layout with numbers
warning: unknown time signature `C'; resorting to default layout
with numbers
warning: unknown time signature `C'; resorting to default layout
with numbers
warning: unknown time signature `C'; resorting to default layout
with numbers
[3][6][9][12][15][18]
paper output to `test-1.tex'...
writing header field `title' to `test-1.title'...
writing header field `subtitle' to `test-1.subtitle'...
writing header field `piece' to `test-1.piece'...
ERROR: In expression (ps-output-expression expr):
ERROR: Wrong number of arguments to #<procedure ps-output-expression (expr
port)>
error: lilypond: command exited with value 512
Traceback (innermost last):
  File "/usr/local/bin/ly2dvi", line 843, in ?
    run_lilypond (files, outbase, dep_prefix)
  File "/usr/local/bin/ly2dvi", line 441, in run_lilypond
    system ('lilypond %s %s ' % (opts, fs))
  File "/usr/local/bin/ly2dvi", line 235, in system
    error (msg)
  File "/usr/local/bin/ly2dvi", line 133, in error
    raise _ ("Exiting ... ")
Exiting ... 

--
      Heikki Junes




reply via email to

[Prev in Thread] Current Thread [Next in Thread]