Re: [GUB] libc.so.6: undefined reference to `_dl_out_of_memory@GLIBC_PRIVATE'

On 16.01.19 14:47, Federico Bruni wrote: My latest attempt to build GUB (on LilyDev Debian 9, gcc version 6.3.0) failed when building guile for linux-x86. Here's the tail: libtool: link: (cd ".libs" && rm -f "libguile.so.17" && ln -s "libguile.so.17.3.1" "libguile.so.17") libtool: link: (cd "

Re: gub: I can now completely build lilypond

Hi Werner! But building of lilypond-test fails. ./target/linux-64/build/lilypond-git.sv.gnu.org--lilypond.git-master/input/regression/lilypond-book/suffix-tely.texi2pdf.log: /home/gub/NewGub/gub/target/tools/root/usr/bin/texi2dvi: texinfo.tex appears to be broken. This may be due to

Re: gub: I can now completely build lilypond

>> Obviously another linking path issue: While executing the external >> TeX binaries, DLL stuff from `target/...' must not be used. > > I think the easiest solution is a simple etex wrapper script in > tools/root that clears LD_LIBRARY_PATH and then executes the > system's etex. Excellent solu

Google Summer of Code

Hi everyone, I was just wondering if I want to contribute to the development, where should I start from? I notice that LilyPond was part of Google Summer of Code in the past few years, except last year. Let's say if I want to do something at GSoC this year with LilyPond, who should I get in touch

Re: Google Summer of Code

On 1/17/2019 12:52 AM, Tsz Kiu Pang wrote: I was just wondering if I want to contribute to the development, where should I start from? For development in general, the Contributor's Guide: For Google Summer of Code, probably t

Re: Google Summer of Code

Am 17.01.19 um 17:11 schrieb Karlin High: On 1/17/2019 12:52 AM, Tsz Kiu Pang wrote: I was just wondering if I want to contribute to the development, where should I start from? For development in general, the Contributor's Guide:

Re: patches for python in gub

Werner LEMBERG writes: >> There's another feature we added in the patches: dynamic/runtime >> relocation of the install prefix. You may have to keep that bit. > > I seem to be blind since I can't find that feature in the patches. > Could you please give a link to a relevant spot in the gub patch

Re: patches for python in gub

>>> There's another feature we added in the patches: dynamic/runtime >>> relocation of the install prefix. You may have to keep that bit. >> >> I seem to be blind since I can't find that feature in the patches. >> Could you please give a link to a relevant spot in the gub patch >> files for, say,