in reply to Re^5: Installing Glib on Debian
in thread Installing Glib on Debian

I know where the warning comes from.

What I would like to understand is why on two very similar machines ExtUtils::Liblist knows where to find the libs on one but not on the other. And Glib builds fine on one but not on the other.

Do you have any idea on how to attack this systematically?

As far as perl is concerned the difference between the two machines is that one is 5.14.1 compiled from the source-tarball and the other is 5.16.2 installed via perlbrew.

LD_LIBRARY_PATH is emtpy in both cases.

Replies are listed 'Best First'.
Re^7: Installing Glib on Debian
by Anonymous Monk on Feb 22, 2013 at 03:34 UTC
Re^7: Installing Glib on Debian
by Intrepid (Curate) on Mar 26, 2013 at 06:46 UTC
    <meta http-equiv="Content-type" content="text/html;charset=cswindows1252">

    morgon wrote:

    Do you have any idea on how to attack this systematically?

    Well, no. I think that your conclusions about the malfunction are incomplete. You could visit this newer node and see if that does not provide some insight.

    I've just built Glib.pm on MS Whyyndwoes, a tougher platform in general when it comes to getting such things right; I did so in order to test the build procedures used by Glib.pm. The insights gained from doing this are written up in the node mentioned above.