[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PDF docs for 2.19.82 broken/missing fonts

From: Knut Petersen
Subject: Re: PDF docs for 2.19.82 broken/missing fonts
Date: Mon, 25 Jun 2018 21:53:08 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

Hi everybody!

Back at home. Never had a look at GUB previously.

   git clone http://github.com/gperciva/gub
   cd gub
   make bootstrap

fails after 2+ minutes with:

   building package: tools::make
     *** Stage: download (make, tools)
     *** Stage: untar (make, tools)
     *** Stage: patch (make, tools)
     *** Stage: autoupdate (make, tools)
     *** Stage: configure (make, tools)
     *** Stage: compile (make, tools)
   Command barfed: cd /home/knut/sources/gub/target/tools/build/make-3.81 && sh 
build.sh && PATH=$(pwd):$PATH make -j16

   Tail of target/tools/log/make.log >>>>>>>>
        glob.c:(.text+0x16fc): undefined reference to `__alloca'
        glob.o:glob.c:(.text+0x17d7): more undefined references to `__alloca' 
        collect2: error: ld returned 1 exit status
        Command barfed: cd /home/knut/sources/gub/target/tools/build/make-3.81 && sh 
build.sh && PATH=$(pwd):$PATH make -j16
   <<<<<<<< Tail of target/tools/log/make.log

   *** Failed target: tools::make
   make: *** [compilers.make:49: bootstrap-git] Fehler 1

So there seems to be no quick'n easy way to have a look at a live gub build on 
my system ...
Does anybody have specific instructions how to setup gub quickly on an openSuSE 
Tumbleweed system?

release/2.19.82-1 builds fine on the native openSuSE Tumblewee system.

The most interesting hint is that only the english version of notation*pdf in 
the broken GUB build is affected.

*It would be very helpfull to know the answer to the following question:**
**Which commands / scripts are used to build lilypond during the gub build? *

Knut, the following patches from you are in master but not in stable.
Would we need to transfer more of them?  Particularly the middle one
looks like a candidate but I don't really know whether we'll need
additional ones.

The problem with the newest one would be that you generated it
automatically from the newest version of Emmentaler but the patch itself
does not consult the actual Emmentaler version and the commit you list
as breaking encodingdefs.ps (by adding a Haydn turn to Emmentaler) is
not present in the stable branch.  So I considered it best to leave that
one off.  Any chance for doing this automatically at some point in

commit 68d904661e8539c77d37eba212d97f8cff082c09
Author: Knut Petersen <address@hidden>
Date:   Sun Jun 24 11:33:39 2018 +0100

     Issue 5338 - Fix 'out of sync' ps script defs
Commit 12fe78825798191ecb7e5a4ee3064679773ae1ab
     broke encodingdefs.ps.

You are right. 68d9... should be applied to lilypond 2.20  12fe... and
both need to be applied after 398c....
commit 398c2e17d45bf4d18723e14d52531e4e7d006dea
Author: Knut Petersen <address@hidden>
Date:   Tue Oct 3 15:05:56 2017 +0100

     Adapt lilypond to ghostscript 9.22, change command line options

We need 398c2... for recent versions of ghostscript, but this patch is 
certainly unrelated to the current problem.
commit e8b2544334fa66858c09028719fa82c447037291
Author: Knut Petersen <address@hidden>
Date:   Wed Jul 26 12:36:38 2017 +0200

     Fix issue 5110: Don't use fixed color for LyricHyphens
Signed-off-by: Knut Petersen <address@hidden>

e8b2.. is a bugfix that should be part of lily 2.20, but it is certainly 
unrelated to the current problem.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]