You’re welcome. The issue here is that pango should never have been updated to 1.43.0 in MSYS2 since it’s an unstable development release, as are all GNOME releases with an odd minor version number. Linux distributions and macOS package managers would never have packaged this release.
Best, Tom > On 4 Jan 2019, at 13:30, Alan W. Irwin <alan.w.irwin1...@gmail.com> wrote: > > On 2019-01-04 11:47+0530 Tom Schoonjans wrote: > >> Hi all, >> >> >> I ran into the same problem a couple of weeks ago. It is in fact a bug in >> pango 1.43.0 which uses meson as buildsystem instead of autotools, and the >> pkg-config issue was introduced in the transition. >> >> I reported this as a bug >> <https://gitlab.gnome.org/GNOME/pango/merge_requests/22#note_390137> and >> submitted a patch <https://gitlab.gnome.org/GNOME/pango/merge_requests/38>, >> which is now in master and should end up in 1.44 (or possibly in 1.43.1 if >> this ever gets released). >> >> In the meantime, the problem can be fixed by executing: >> >> echo "Requires: gobject-2.0" >> /mingw64/lib/pkgconfig/pango.pc >> >> followed by building plplot… The cairo backend should build fine then. >> > > Thanks, Tom, for that really helpful comment about what appears to be a > widespread issue with pango 1.43.0. That's a heavily used free > library. So let's hope the upstream pango developers quickly release > 1.43.1 with your fix and that quickly propagates to free software > distributions for Linux (thousands of them), Mac OS X (fink, macports, > and homebrew), and Windows (Cygwin and MinGW-w64/MSYS2). > > @Günter: > > So to summarize, it looks like my recent tests on Debian Testing have > been fine because I have installed cairo 1.42.3, and that platform has > not (yet) got around to packaging cairo-1.43.0. Arjen's test was also > a success because he has cairo 1.42.1 currently installed (and has not > yet updated his system), but your recent test failed because you did > do such an update which exposed you to the bad pango 1.43.0 version. > So hopefully Tom's above echo command will sort out the issue for you > until upstream developers fix the issue, and that fix propagates to > MinGW-w64/MSYS2. > > At the same time, I also stand by my advice to drop "MinGW Makefiles" > and mingw32-make and use the "Unix Makefiles" or "MSYS Makefiles" > generators and bash and make instead simply because if you ever run > into PLplot trouble with the platform, the very much enhanced test > capability (via bash scripts) you have access to with the latter > method can be quite useful, e.g., the report tarball that can > be generated for that case makes it much easier to > understand your bug reports. > > @Arjen: you will likely also be affected by the same bug and have to do the > same fix > when you update your own MinGW-w64/MSYS2. > > And I will likely be affected by the same bug if Debian Testing starts > packaging > pango 1.43.0. > > Alan > __________________________ > Alan W. Irwin > > Programming affiliations with the FreeEOS equation-of-state > implementation for stellar interiors (freeeos.sf.net); the Time > Ephemerides project (timeephem.sf.net); PLplot scientific plotting > software package (plplot.sf.net); the libLASi project > (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); > and the Linux Brochure Project (lbproject.sf.net). > __________________________ > > Linux-powered Science > __________________________ _______________________________________________ Plplot-general mailing list Plplot-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-general
