Re: GUB
In May, when we were discussing the limitations of 32 bit MinGW, I asked Jan for an estimate of how much work it would be to add a 64-bt MinGW to GUB. His answer was that GUB is a hack, and that he wasn't interested in putting any more effort into fixing up GUB, although he would certainly provide me advice if I asked for it. His recommendation was to move to Guix[1], which is an existing and supporting package for maintaining appropriate package versions for a particular user. He said he would be willing to help with that, as it's making things better, not just spending more effort on a hack. Are there any opinions on whether we should pursue a move to Guix? Thanks, Carl 1. https://www.gnu.org/software/guix/manual/en/html_node/Package-Management.html ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Context_handle
On Jul 8, 2018, at 14:11, David Kastrup wrote: > > I think it's for providing a definite point of time for running the > finishing hooks of a context's iterators and making the context > unavailable for \context ... [= ...] continuations. > > Garbage collection is not determinate. I think I see. If a reference-holder is expected to drop its reference at a specific point, then if the reference is still held at the time of destruction, it is a programming error. Whether to reduce the reference count at destruction or leave it permanently above zero is then just a question of robustness given the failure of the reference-holder to follow protocol. — Dan ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB
Hi Phil! Ubuntu 14 for both. Thanks. With a few patches to correct broken download links that worked. After cleaning up I'll send those patches to you. Knut ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: make doc bombs out in MusicXML
Am 16.06.2018 um 15:47 schrieb James Lowe:
Hello
On Sat, 16 Jun 2018 14:20:43 +0100 (BST), "James Lowe"
wrote:
Hello
On Sat, 16 Jun 2018 09:10:10 -0400, Dan Eble wrote:
On Jun 16, 2018, at 08:46, James Lowe wrote:
Well before I applied those patches on behalf of Alexander's patches I did a
full patch test with the patches applied and had no problems.
However ... I know that there are some 'prgramming errors' reported that do not
break patch testing. I wonder if this is something like that.
My work machine will be running merge every 4 hours, but I'll kick one off from
home now (~ 13:45 BST)
I assume that I should wait until this situation is resolved before pushing my
own patch. If it does not matter, please let me know.
—
It should be done quite soon. I'll send an email either way.
Well it pushed to master without complaint.
I don't know what else to add.
Hi everybody!
Finally I succeeded to "make bootstrap" GUB. But building lilypond master with
GUB is broken. The log is quite clear:
make[1]: Entering directory
`/home/knut/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-master/python'
PYTHONOPTIMIZE= /home/knut/gub/target/tools/root/usr/bin/python -tt -c 'import
py_compile; py_compile.compile ("out/musicexp.py")'
File "out/musicexp.py", line 1880
omit = '' if self.visible else '\omit Staff.TimeSignature'
^
SyntaxError: invalid syntax
GUB uses the ancient Python 2.4.5. Building lilypond outside of GUB with python
2.7.15 succeeds without problems.
James, do you use GUB for your tests?
Knut
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Context_handle
Things happen when contexts go out of scope (eg. end of staff), so it
should happen deterministically.
On Sun, Jul 8, 2018 at 8:12 PM David Kastrup wrote:
> Dan Eble writes:
>
> > What is the purpose of Context_handle? It looks like a scoped
> > contribution to a reference count until the destructor:
> >
> >> Context_handle::~Context_handle ()
> >> {
> >> /*
> >> Don't do
> >> if (outlet_)
> >> down ();
> >> with GC, this is asynchronous.
> >> */
> >> }
> >
> > I can understand garbage collection, and I can imagine coordinating
> > garbage collection with reference counting, but coordinating garbage
> > collection with leaky reference counting is hard to appreciate.
>
> I think it's for providing a definite point of time for running the
> finishing hooks of a context's iterators and making the context
> unavailable for \context ... [= ...] continuations.
>
> Garbage collection is not determinate.
>
> I might be mistaken.
>
> --
> David Kastrup
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>
--
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB
David Kastrup writes: > Masamichi Hosoda writes: > Ubuntu 14 for both. I would expect Ubuntu 16 to work but have not tried it. >>> >>> Not sure about that. We had several incompatibilities in the LilyPond >>> code base since then (2.18.2 does not compile on current GCC versions) >>> and GCC is written in C++ these days. Though the bootstrap process >>> might actually go through C-written GCC to get to its C++ compiler: not >>> sure about that. >> >> I tried to use GUB in Ubuntu 16.04 LTE 64 bit. >> But It failed with some errors. >> >> So I use GUB in Ubuntu 14.04 LTE 64 bit. >> I have not tried Ubuntu 18.04 LTE yet. > > Seems like we don't have a lot of options other than porting the > bootstrap forward and I am not sure that all operating systems will stay > with us. I'd actually be more comfortable with regard to licensing > clarity to move the MacOSX bootstrap The crosscompilation actually. > to OpenDarwin, but I seem to remember that OpenDarwin more or less is > dead due to Apple not keeping their promises. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB
Masamichi Hosoda writes: >>> Ubuntu 14 for both. I would expect Ubuntu 16 to work but have not tried it. >> >> Not sure about that. We had several incompatibilities in the LilyPond >> code base since then (2.18.2 does not compile on current GCC versions) >> and GCC is written in C++ these days. Though the bootstrap process >> might actually go through C-written GCC to get to its C++ compiler: not >> sure about that. > > I tried to use GUB in Ubuntu 16.04 LTE 64 bit. > But It failed with some errors. > > So I use GUB in Ubuntu 14.04 LTE 64 bit. > I have not tried Ubuntu 18.04 LTE yet. Seems like we don't have a lot of options other than porting the bootstrap forward and I am not sure that all operating systems will stay with us. I'd actually be more comfortable with regard to licensing clarity to move the MacOSX bootstrap to OpenDarwin, but I seem to remember that OpenDarwin more or less is dead due to Apple not keeping their promises. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB
>> Ubuntu 14 for both. I would expect Ubuntu 16 to work but have not tried it. > > Not sure about that. We had several incompatibilities in the LilyPond > code base since then (2.18.2 does not compile on current GCC versions) > and GCC is written in C++ these days. Though the bootstrap process > might actually go through C-written GCC to get to its C++ compiler: not > sure about that. I tried to use GUB in Ubuntu 16.04 LTE 64 bit. But It failed with some errors. So I use GUB in Ubuntu 14.04 LTE 64 bit. I have not tried Ubuntu 18.04 LTE yet. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB
"Phil Holmes" writes: > Ubuntu 14 for both. I would expect Ubuntu 16 to work but have not tried it. Not sure about that. We had several incompatibilities in the LilyPond code base since then (2.18.2 does not compile on current GCC versions) and GCC is written in C++ these days. Though the bootstrap process might actually go through C-written GCC to get to its C++ compiler: not sure about that. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB
Ubuntu 14 for both. I would expect Ubuntu 16 to work but have not tried it. -- Phil Holmes - Original Message - From: Knut Petersen To: Phil Holmes ; David Kastrup Cc: lilypond-devel ; Masamichi Hosoda Sent: Monday, July 09, 2018 10:53 AM Subject: Re: GUB Am 09.07.2018 um 10:19 schrieb Phil Holmes: FWIW I can accept pull requests for the GUB repo, so if anybody has a patch that should be applied, I can get the patch into the build system. Which version of which distribution are you using on the computer running GUB? Which version of the distribution did you use for the bootstrap of GUB? Knut ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB
Am 09.07.2018 um 10:19 schrieb Phil Holmes: FWIW I can accept pull requests for the GUB repo, so if anybody has a patch that should be applied, I can get the patch into the build system. Which version of which distribution are you using on the computer running GUB? Which version of the distribution did you use for the bootstrap of GUB? Knut ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Let \raise and \lower heed font-size (issue 343330043 by d...@gnu.org)
On 2018/07/09 09:07:43, Malte Meyn wrote:
This needs an entry in changes.tely, maybe with an example like
\markup {
A \raise #1.5 A
\fontsize #6 {
A \raise #1.5 A
}
}
And maybe one should explain further effects like correct scaling of
ChordNames?
https://codereview.appspot.com/343330043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Let \raise and \lower heed font-size (issue 343330043 by d...@gnu.org)
This needs an entry in changes.tely, maybe with an example like
\markup {
A \raise #1.5 A
\fontsize #6 {
A \raise #1.5 A
}
}
https://codereview.appspot.com/343330043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB
FWIW I can accept pull requests for the GUB repo, so if anybody has a patch that should be applied, I can get the patch into the build system. -- Phil Holmes - Original Message - From: Knut Petersen To: David Kastrup Cc: lilypond-devel ; Phil Holmes ; Masamichi Hosoda Sent: Monday, July 09, 2018 9:08 AM Subject: Re: GUB Am 06.07.2018 um 10:29 schrieb David Kastrup: At any rate, if we need to update our bootstrap setup in order to be able to continue using it on newer platforms, this is likely something that is more apparent to new users of GUB since old users will be reusing their already bootstrapped stuff and thus won't notice easily when it would stop being compilable. It may well be that GUB needs either more patches on top or newer base versions to do its job. It's one of the most obscure parts of getting out LilyPond to the world. An updated GUB status: 1: Graham informed me that he does not have the energy to do open-source work outside of his job these days. 2: The version of make used in GUB needs a fix to be compatible with glibc 2.27. 3: The versions of glibc and glibc-core used in GUB need a fix to be compatible with make 4.x.y. (Frédéric Bron already mentioned that problem in septemter 2016 on lilypond-devel) 4: The download link of libpng12 is broken. 5: The download link of jpegsrc.v6b.tar.gz is broken. 6: ghostscript really should be updated. 7: GUB fails to correctly build the English documentation of the latest stable prerelease, up to now nobody understands why. Even with fixes for the problems 2-5 mentioned above bootstrapping or using GUB fails to work on openSuSE Tumbleweed, openSuSE 11.3 and on the fedora-27 based LilyDev because of problems not mentioned above. It would be nice to have a list of linux distributions that were/are compatible to GUB ... usually it's much easier to debug a broken system if you have a working starting point. Knut ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB
Am 06.07.2018 um 10:29 schrieb David Kastrup: At any rate, if we need to update our bootstrap setup in order to be able to continue using it on newer platforms, this is likely something that is more apparent to new users of GUB since old users will be reusing their already bootstrapped stuff and thus won't notice easily when it would stop being compilable. It may well be that GUB needs either more patches on top or newer base versions to do its job. It's one of the most obscure parts of getting out LilyPond to the world. An updated GUB status: 1: Graham informed me that he does not have the energy to do open-source work outside of his job these days. 2: The version of make used in GUB needs a fix to be compatible with glibc 2.27. 3: The versions of glibc and glibc-core used in GUB need a fix to be compatible with make 4.x.y. (Frédéric Bron already mentioned that problem in septemter 2016 on lilypond-devel) 4: The download link of libpng12 is broken. 5: The download link of jpegsrc.v6b.tar.gz is broken. 6: ghostscript really should be updated. 7: GUB fails to correctly build the English documentation of the latest stable prerelease, up to now nobody understands why. Even with fixes for the problems 2-5 mentioned above bootstrapping or using GUB fails to work on openSuSE Tumbleweed, openSuSE 11.3 and on the fedora-27 based LilyDev because of problems not mentioned above. It would be nice to have a list of linux distributions that were/are compatible to GUB ... usually it's much easier to debug a broken system if you have a working starting point. Knut ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
