On Sat, 2016-07-09 at 20:19 +0100, Richard Shann wrote: > On Thu, 2016-07-07 at 22:14 -0500, Jeremiah Benham wrote: > > I was successful at compiling 1.40.1. Unfortunately lilypond now fails > > to compile because it can't tell if pango is installed when it is. The > > pango.pc file is in its standard location usr/lib/pkgconfig. I believe > > lilypond had fixed this in git but this would require to upgrade > > lilypond to 2.19.*. > > I think we should await the 2.20 LilyPond release then before upgrading > Pango. I've merged the Japanese translation and other fixes into the > 2.0.10 release so that we should be ready to go once it is building > again.
I see you got a build last night, but it seems it is from a tarball made earlier - can you re-make the tarball for the latest code on the 2.0.10 branch? Richard > > Richard > > > > > > > Jeremiah > > > > > > On Thu, Jul 7, 2016 at 2:57 AM, Richard Shann > > <[email protected]> wrote: > > Apparently this is caused by a bug in Pango, (Pango 1.36.8: > > bad, Pango > > 1.40.1: OK) > > Jeremiah, is there a possibility of building with a Pango > > version 1.40.1 > > or higher? > > > > Richard > > > > > > > > > > > > _______________________________________________ > Denemo-devel mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/denemo-devel _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
