lilypond-devel
[Top][All Lists]
Advanced

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

Re: Staging broken.


From: Han-Wen Nienhuys
Subject: Re: Staging broken.
Date: Wed, 19 Feb 2020 09:19:12 +0100

On Wed, Feb 19, 2020 at 12:51 AM David Kastrup <address@hidden> wrote:

>
> >> Can you provide me with some recipe to reproduce the problem? Can you
> tell
> >> me what distribution you use? I could use Docker to recreate your setup.
> >
> > Just current Ubuntu eoan.
>
> The following patch makes the commit you pushed compile:
>
> diff --git a/lily/pango-font.cc b/lily/pango-font.cc
> index 8eece690c8..587ed3d4f3 100644
> --- a/lily/pango-font.cc
> +++ b/lily/pango-font.cc
> @@ -17,6 +17,10 @@
>    along with LilyPond.  If not, see <http://www.gnu.org/licenses/>.
>  */
>
> +// Necessary for supporting pango_context_new() and
> +// pango_context_set_font_map() in Pango < 1.22
> +#define PANGO_ENABLE_BACKEND
> +
>

aha.

this looks like fallout from

commit d21ea13a22b1cab8c9cb604aa3fcd2ca8073befd
Author: Matthias Clasen <address@hidden>
Date:   Thu Jul 4 20:36:00 2019 +0000

    Header cleanup

    Abolish the PANGO_ENABLE_BACKEND and PANGO_ENABLE_ENGINE
    defines. All backend-only apis are moved into private
    headers, all apis that were engine-only are marked as
    deprecated, since engines are.

which is

 $ git describe --contains d21ea13a22b1cab8c9cb604aa3fcd2ca8073befd
1.44~145^2

$ rpm -q pango
pango-1.44.7-1.fc31.x86_64

since you have 1.42 , that seems like the root cause.

I'm preparing a docker image for my lilypond-ci scripts that lets me check
for this case too.

-- 
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen


reply via email to

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