> /home/hanwen/lilypond/usr/lib/libfreetype.so.6.3.22(FT_Stream_Open+0x10d)
This is interesting. If the normal libtool versioning system is used,
`6.3.22' corresponds to FreeType version 2.3.11, released in 2009!
The current FreeType release is 2.7.1, corresponding to 6.13.0.
Please check that!
After a intricate upgrade of laptop, I now have some stacktraces. They
don't tell me much,
read(16, "OTTO\0\r\0\200\0\3\0PCFF
\26g\353\377\0\0\r\30\0\0\366\253FFTM"..., 4096) = 4096
> /usr/lib64/libc-2.24.so(__read_nocancel+0x7) [0xf7bd0]
> /usr/lib64/libc-2.24.so(_IO_file_seekoff+0x34b) [0x7a4
Alexander Kobel writes:
> On 2017-04-09 11:24 AM, David Kastrup wrote:
>> Alexander Kobel writes:
>>> On 2017-04-07 11:24 AM, David Kastrup wrote:
Hi folks,
tomorrow morning I'll be leaving for my annual climbing trip in Italy
(not that I could afford it but there is no point
On 2017-04-09 11:24 AM, David Kastrup wrote:
Alexander Kobel writes:
On 2017-04-07 11:24 AM, David Kastrup wrote:
Hi folks,
tomorrow morning I'll be leaving for my annual climbing trip in Italy
(not that I could afford it but there is no point in postponing all
living until death).
Sounds g
On Apr 10, 2017, at 08:43, David Nalesnik wrote:
>
> It's strange -- it seems that the value of
> ly:tuplet-bracket::calc-x-offset is used sometimes regardless of the
> ly:grob-set-property! and there's no predictability to it.
>
> No idea :(
Maybe there’s a race against the garbage collector.
Hello,
On Mon, 10 Apr 2017 12:47:57 +0200
Thomas Morley wrote:
> 2017-04-10 12:36 GMT+02:00 Thomas Morley :
> > Hi all,
> >
> > with the code below I experienced some pretty strange behaviour.
> >
> > The visual output changes every few compilations, although I
> > changed _nothing_!! In average
