|
From: | Martin Neubauer |
Subject: | (*location*) returning no valid value while parsing embedded scheme on freebsd |
Date: | Sat, 2 May 2020 18:19:40 +0200 |
User-agent: | Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 |
I assume this is os specific because the issue makes openlilylib unusable and my understanding was that most of the oll developers were living on the 2.21 branch already before the release and should have run into the problem as well. Right now my understanding is that the separation of input and output parameters introduced by commit 5a4039b700f3a7447401780c720070d14e2891bd leads to a situation with no valid reference to the source file present in the output. My guess is that differences in the os' threading libraries influence if the issue manifests itself. The attached file location.ly demonstrates the issue. The file location.out contoins the out put of three different runs: 1. lilypond at commit 520c0c31d468f9112aa305b93c8f038bf5d7e996 (the last one unaffected) 2. lilypond at commit 5a4039b700f3a7447401780c720070d14e2891bd (first one affected) 3. lilypond release 2.21.1 with the attached patch applied Best regards, Martin -- My other computer is your Windows box.
location.ly
Description: Text Data
location.out
Description: Text document
0001-fix-location-on-freebsd.patch
Description: Text Data
signature.asc
Description: OpenPGP digital signature
[Prev in Thread] | Current Thread | [Next in Thread] |