If you can isolate the differences between pkg-config versions then it's worth logging an issue with PkgConfig

Yes, I'll try to reach an understanding of that and file an issue.

It would also be nice to not have to rename the Gtk static and import libs.
UPDATE:One way is to edit the Libs entry in the relevant pc file.
For example, in D:\msys64\mingw64\lib\pkgconfig\glib-2.0.pc change the entry: 
Libs: -L${libdir} -lglib-2.0 -lintl
to
Libs: -L${libdir} -lglib-2.0.dll -lintl.dll

[download]
That's probably less tedious than renaming the libraries, but it's still tedious :-(

And it would be good to not have to edit any of the generated Makefiles.
UPDATE: This is achieved by downgrading ExtUtils-Depends-0.8001 to ExtUtils-Depends-0.8000.

Finally, I'd like to see the G-I-O-0.050 test suite skip all of the tests as it should. (I actually managed to get that to happen a coupla nights back with my own build of perl-5.38.0 ... but haven't since been able to reproduce that "success".)
UPDATE: This is discussed at https://www.perlmonks.org/?node_id=11154072 and addressed by the patch at https://rt.cpan.org/Ticket/Display.html?id=149570

Unfortunately, there's a lot of opacity to get through when dealing with each of those issues ... but I'll plug away at it, at least util I get sick of it ;-)

Cheers,
Rob

In reply to Re^14: gmake error on Glib compile by syphilis
in thread gmake error on Glib compile by MikeMc69

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.