Am Sa., 12. Jan. 2019 um 16:06 Uhr schrieb Thomas Morley
:
> I'll redo testings with a 32-bit OS soon.
FWIW, I did a successful complete run of 'make lilypond' in LilyDev
4(?), based on debian-8, 32 bit
(only thing I had to install was missing 'unzip')
gub was amended with pull-requests 53, 54,
On 14.01.19 12:15, Knut Petersen wrote:
Nothing suspicious with one exception:
home/gub/NewGub/gub/target/tools/root/usr/lib/libdb-4.7.so is opened as well as
/usr/lib64/libdb-4.8.so. Why did we link against libdb-4.8?
No time left for today ... maybe someone else has an idea how to
Counted down, and pushed as
https://git.savannah.gnu.org/cgit/lilypond.git/commit/?h=staging=78225bc1b386e12dc1d03a5d2c7a017c0a52a22d
Thanks!
https://codereview.appspot.com/363880043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Hello,
Here is the current patch countdown list. The next countdown will be on the
January 17th.
A quick synopsis of all patches currently in the review process can be found
here:
http://philholmes.net/lilypond/allura/
Push:
5459 Avoid Ghostscript-specific max/min operators in PS -
Patch on countdown for January 17th
https://codereview.appspot.com/367880043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 13.01.19 13:59, Werner LEMBERG wrote:
Looks like it's `strace' time again...
Yes.
Building tools::python is broken on openSuSE tumbleweed as well as on ubuntu
18, but inspection reveals that the problems are _not_ identical. On ubuntu 18
the building of tools::python fails because libs
