Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
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
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 and addressed by the patch at

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 ;-)


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

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.