Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Thomas Bushnell BSG schreef:
I'm distressed that nobody has bothered to fix the bug since then. In
the thread on the mailing list you can see that if LILYPONDPREFIX is
set correctly, the bug goes away.
This issue has been addressed in a more
On Tue, Jul 25, 2006 at 02:08:03AM -0700, Thomas Bushnell BSG wrote:
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Thomas Bushnell BSG schreef:
I'm distressed that nobody has bothered to fix the bug since then. In
the thread on the mailing list you can see that if LILYPONDPREFIX is
set
Thomas Bushnell BSG schreef:
The problem is that lilypond's build system assumes that lilypond is
already installed on the system.
Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out
in the thread, it is setting LILYPONDPREFIX *incorrectly*, and the
reason the builds are
Re,
I have found why it builed for you and not on
my system.
The python version installed on my system was a
2.4 version. I had backported on a 2.3 version,
and the problem seem solved.
It will be interesting to know why there is this problem
with new versions of python, because if one
day
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
Thomas Bushnell BSG schreef:
The problem is that lilypond's build system assumes that lilypond is
already installed on the system.
Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out
in the thread, it is setting LILYPONDPREFIX
On Sun, Jul 23, 2006 at 12:25:42PM +0200, Han-Wen Nienhuys wrote:
Thomas Bushnell BSG schreef:
I'm distressed that nobody has bothered to fix the bug since then. In
the thread on the mailing list you can see that if LILYPONDPREFIX is
set correctly, the bug goes away.
This issue has been
Thomas Bushnell BSG schreef:
I'm distressed that nobody has bothered to fix the bug since then. In
the thread on the mailing list you can see that if LILYPONDPREFIX is
set correctly, the bug goes away.
This issue has been addressed in a more robust manner in the 2.9 series,
and I would
On Fri, Jul 21, 2006 at 04:57:14PM -0700, Thomas Bushnell BSG wrote:
Ludovic RESLINGER [EMAIL PROTECTED] writes:
I saw in archive some messages about a problem to build lilypond in
debian unstable. I think this is not a problem of python's version, because
I tested to build with python2.4
On Wed, Jul 19, 2006 at 07:47:35PM +0200, Mats Bengtsson wrote:
If you run
scripts/out/convert-ly --help
from the lilypond/ directory, you will get a much more informative
error message that might
help you find out what the problem is.
/Mats
Hello
Thank you for your answer.
When I
Hello,
I saw in archive some messages about a problem to build lilypond in
debian unstable. I think this is not a problem of python's version, because
I tested to build with python2.4 and python2.5, and the problem stay the
same:
chmod 755 out/convert-ly
/usr/bin/perl
If you run
scripts/out/convert-ly --help
from the lilypond/ directory, you will get a much more informative
error message that might
help you find out what the problem is.
/Mats
Quoting Ludovic RESLINGER [EMAIL PROTECTED]:
Hello,
I saw in archive some messages about a problem to build
11 matches
Mail list logo