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

You have what? Where is it?
> pkg-config --libs gobject-2.0 -lgobject-2.0 -lglib-2.0 > find /usr/lib -name \*libglib-2.0\* /usr/lib/vmware-installer/2.0/lib/lib/libglib-2.0.so.0 /usr/lib/vmware-installer/2.0/lib/lib/libglib-2.0.so.0/libglib-2.0.so. +0 /usr/lib/vmware/lib/libglib-2.0.so.0 /usr/lib/vmware/lib/libglib-2.0.so.0/libglib-2.0.so.0 /usr/lib/x86_64-linux-gnu/libglib-2.0.a /usr/lib/x86_64-linux-gnu/libglib-2.0.so > find /usr/lib -name \*libgobject-2.0\* /usr/lib/vmware-installer/2.0/lib/lib/libgobject-2.0.so.0 /usr/lib/vmware-installer/2.0/lib/lib/libgobject-2.0.so.0/libgobject-2 +.0.so.0 /usr/lib/vmware/lib/libgobject-2.0.so.0 /usr/lib/vmware/lib/libgobject-2.0.so.0/libgobject-2.0.so.0 /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3200.4 /usr/lib/x86_64-linux-gnu/libgobject-2.0.so /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 /usr/lib/x86_64-linux-gnu/libgobject-2.0.a > dpkg -l |grep libglib2.0- ii libglib2.0-0:amd64 2.33.12+really2.32 +.4-5 GLib library of C routines ii libglib2.0-bin 2.33.12+really2.32 +.4-5 Programs for the GLib library ii libglib2.0-cil 2.12.10-3 + CLI binding for the GLib utility library 2.12 ii libglib2.0-cil-dev 2.12.10-3 + CLI binding for the GLib utility library 2.12 ii libglib2.0-data 2.32.0-4 + Common files for GLib library ii libglib2.0-dev 2.33.12+really2.32 +.4-5 Development files for the GLib library
I really would like to understand why I get the warning on this machine but not on the other...


Comment on Re^4: Installing Glib on Debian
Download Code
Re^5: Installing Glib on Debian
by Anonymous Monk on Feb 22, 2013 at 01:57 UTC

    I really would like to understand why I get the warning on this machine but not on the other...

    The warning (probably harmless) is simple to explain, ExtUtils::Liblist issues it because it doesn't know where to find those libraries (the ....so)

    The error (can't load) is because of those gtk .so's not being found in LD_LIBRARY_PATH or other hardcoded path

      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.

        <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.