Han-Wen Nienhuys wrote:
Paul Scott wrote:
Was this received or has anything new happened. I have several
machines I was running Lily on and now can't.
Thanks,
Paul
On Debian sid on a K6-II I get:
GNU LilyPond 2.7.37
Program received signal SIGILL, Illegal instruction.
0xb7e25423 in __
Graham Percival wrote:
Couldn't lily handle the size="a4" in exactly the same way as it handles
#(set-...) ?
No. size="a4" is just an assignment, and assignments don't have further
side effects.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
__
Paul Scott wrote:
Was this received or has anything new happened. I have several machines
I was running Lily on and now can't.
Thanks,
Paul
On Debian sid on a K6-II I get:
GNU LilyPond 2.7.37
Program received signal SIGILL, Illegal instruction.
0xb7e25423 in __gmpn_mod_1 () from
/usr/loc
Joe Neeman wrote:
This contains a bug-fix, an optimisation (been doing some profiling :)) and a
+ (combine_demerits): use pointers to reduce copying data
Are you sure about this? AFAIK references are internally handled in the
same way as pointers.
--
Han-Wen Nienhuys - [EMAIL PROTE
On Sat, 11 Mar 2006 06:13 am, Han-Wen Nienhuys wrote:
> Joe Neeman wrote:
> > This contains a bug-fix, an optimisation (been doing some profiling :))
> > and a
> >
> > + (combine_demerits): use pointers to reduce copying data
>
> Are you sure about this? AFAIK references are internally handled in
Was this received or has anything new happened. I have several machines
I was running Lily on and now can't.
Thanks,
Paul
On Debian sid on a K6-II I get:
GNU LilyPond 2.7.37
Program received signal SIGILL, Illegal instruction.
0xb7e25423 in __gmpn_mod_1 () from
/usr/local/lilypond/usr/bin
This contains a bug-fix, an optimisation (been doing some profiling :)) and a
new feature (adding page-turn-penalties). The bug-fix and the feature won't
affect 2.8 because 2.7 doesn't use the full capabilities of the
constrained-breaker, but I think the bug fix at least should go in.
Index: lil