Re: output-distance.py: Support relative font paths. (issue 349090043 by lemzw...@googlemail.com)

I got it. Vào 9:37 CN, 13 Th1 2019 https://photos.app.goo.gl/KCakjdAeKg6WSURT7 > > my wife > > > > https://codereview.appspot.com/349090043/diff/20001/scripts/build/output-distance.py > File scripts/build/output-distance.py (left): > > > https://codereview.appspot.com/349090043/diff/20001/scripts

Re: output-distance.py: Support relative font paths. (issue 349090043 by lemzw...@googlemail.com)

Van de 349090043 https://codereview.appspot.com/349090043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: "Well, here's another nice mess I've gotten myself into!" Previously Please test new lilypond installers

Hi, Michael! On Thu, Jan 31, 2019 at 10:28 AM Michael Hendry wrote: > > On 29 Jan 2019, at 19:00, Urs Liska wrote: > > > > If you use alternative notation fonts you have to "install" them for > every new LilyPond installation. > > [With apologies to Laurel & Hardy]. > > Having successfully inst

Re: Please test new lilypond installers

Hi, Knut, et al! On Tue, Jan 29, 2019 at 2:19 AM Knut Petersen wrote: > Hi everybody > > Urs Liska provides installers for branch master of lilypond, generated by > an updated version of our build system GUB: > > https://cloud.ursliska.de/s/QPINwLqJNeVslCu > > There you'll find > ... >

"Well, here's another nice mess I've gotten myself into!" Previously Please test new lilypond installers

> On 29 Jan 2019, at 19:00, Urs Liska wrote: > > If you use alternative notation fonts you have to "install" them for every > new LilyPond installation. [With apologies to Laurel & Hardy]. Having successfully installed 2.21.0, I’ve tried to install Lilyjazz according to the instructions here:

Re: Please test gub

On 31.01.19 16:15, Karlin High wrote: On 1/31/2019 9:04 AM, Alexander Kobel wrote: BTW, can we actually add images in Lily? Encapsulated PostScript images are fair game with \epsfile I know I used that once, but I forget

Re: Please test gub

On 1/31/2019 9:04 AM, Alexander Kobel wrote: BTW, can we actually add images in Lily? Encapsulated PostScript images are fair game with \epsfile I know I used that once, but I forget which program I used to make the EPS f

Re: Please test gub

Hi, On 31.01.19 13:25, Alexander Kobel wrote: Indeed, LLVMgold.so pops up in the trace. On my system, the symlink for liblto_plugin.so already exists, so I only had to remove (rename wasn't enough) LLVMgold.so. Building tools::guile succeeds after that modification; I'll test the further pro

Re: Please test gub

Addendum: On 31.01.19 15:39, Alexander Kobel wrote: Whenever I can, I "correct" shebangs to python2 (without ever having looked up this PEP), and nobody ever complained that it breaks their workflow. That is to say: I've yet to encounter a system where python points to python2.x, but at the

Re: Please test gub

Hi, On 31.01.19 15:21, David Kastrup wrote: Knut Petersen writes: On 31.01.19 08:43, Alexander Kobel wrote: Hi, fails on Arch Linux (up-to-date, Intel Core i5-3317U). First, all Python scripts seem to require Python2 (but python -> python3 is the default on Arch). I don't think that matc

Re: Please test gub

Knut Petersen writes: > On 31.01.19 08:43, Alexander Kobel wrote: >> Hi, >> >> fails on Arch Linux (up-to-date, Intel Core i5-3317U). >> >> First, all Python scripts seem to require Python2 (but python -> >> python3 is the default on Arch). I don't think that matches Python's own recommendation.

Re: Please test gub

> On my system, the symlink for liblto_plugin.so already exists, so I > only had to remove (rename wasn't enough) LLVMgold.so. > > Building tools::guile succeeds after that modification; [...] OK! BTW, It took me some weeks to identify this very problem... > # pacman -Qo /usr/lib/bfd-plugins/

Re: Please test gub

Hi, strace according to Knut's instructions is attached. On 31.01.19 12:54, Werner LEMBERG wrote: Apart from that minor buzz, `make lilypond` does a good chunk of work, but fails building tools::guile; log attached. I see. libtools segfauls. ../libtool: line 950: 23645 Segmentation f

Re: Please test gub

>>../libtool: line 950: 23645 Segmentation fault  (core dumped) >>ar cru .libs/libguile.a [...] > > This is probably the same bug I've encountered on my openSUSE box. > Try to remove the file (or link) `/usr/lib/bfd-plugins/LLVMgold.so' > and replace it with the gcc variant `liblto_plu

Re: Please test gub

>> Apart from that minor buzz, `make lilypond` does a good chunk of work, >> but fails building tools::guile; log attached. > > I see. libtools segfauls. >../libtool: line 950: 23645 Segmentation fault  (core dumped) >ar cru .libs/libguile.a [...] This is probably the same bug I've

Re: Please test gub

On 31.01.19 08:43, Alexander Kobel wrote: Hi, fails on Arch Linux (up-to-date, Intel Core i5-3317U). First, all Python scripts seem to require Python2 (but python -> python3 is the default on Arch). I placed a symlink to python -> python2 in a high-priority $PATH as a workaround, but it might b

Re: Please test new lilypond installers

Hi, On 29.01.19 10:19, Knut Petersen wrote: Urs Liska provides installers for branch master of lilypond, generated by an updated version of our build system GUB: [...]    lilypond-2.21.0-1.linux-64.sh    lilypond-2.21.0-1.linux-x86.sh Work like a charm on Arch Linux. Cheers, Alex smime