[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 716 in lilypond: --disable-optimisation causes `Parsed object shou
From: |
codesite-noreply |
Subject: |
Issue 716 in lilypond: --disable-optimisation causes `Parsed object should be dead' |
Date: |
Sun, 28 Dec 2008 22:09:58 +0000 |
Status: Accepted
Owner: lemzwerg
Labels: Type-Defect
New issue 716 by lemzwerg: --disable-optimisation causes `Parsed object
should be dead'
http://code.google.com/p/lilypond/issues/detail?id=716
[git 2008-12-27]
Even the simplest lilypond input (like `{ c }') causes
programming error: Parsed object should be dead: static scm_unused_struct*
Prob::mark_smob(scm_unused_struct*)
continuing, cross fingers
programming error: Parsed object should be dead: static scm_unused_struct*
Context_def::mark_smob(scm_unused_struct*)
continuing, cross fingers
if compiled with --disable-optimisation. It apparently has no negative
impact on the output since it happens after creation of the PDF file.
This is a GNU/Linux box using guile 1.8.1 (from April 2007); I can't say
when this problem has started since I previously haven't compiled lilypond
with disabled optimisation.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 716 in lilypond: --disable-optimisation causes `Parsed object should be dead',
codesite-noreply <=