Re: Pango / Glib config problem

[Noah Levitt <nlevitt columbia edu>]

Directories called glib-2.0 are irrelevant; the problem is a
libglib-2.0.so, probably in /usr/lib, possibly somewhere
else.

Noah

On Sat, Sep 13, 2003 at 17:17:44 -0400, Anthony wrote:
> > 2.2.1 is coming from an installed library somewhere on your
> > system.
> 
> Of course it is; the question is *where*?  The error message tells me 
> that it found 2.2.1, and that I should remove it, but it doesn't tell me 
> *where* it found it.  Additionally boggling is the fact that I've 
> removed every glib-2.0 folder on my system, and it still gives me the error.
> 
> > put the location of
> > glib 2.2.3 ahead of it in LD_LIBRARY_PATH.
> 
> My LD_LIBRARY_PATH is null.  I'll try putting the location of 2.2.3 into 
> there and see if that fixes it.
> 
> -Anthony
> 
> 
> Noah Levitt wrote:
> >2.2.1 is coming from an installed library somewhere on your
> >system. You can either get rid of it or put the location of
> >glib 2.2.3 ahead of it in LD_LIBRARY_PATH.
> >
> >Noah
> >
> >On Sat, Sep 13, 2003 at  9:44:12 -0400, Anthony wrote:
> >
> >>I'm running Gnome 2.2 on Slackware 9.0, and I'm trying to upgrade to 
> >>Gnome 2.4.  I'm following the order of installation on this page:
> >>
> >>http://www.gnome.org/start/2.4/notes/rninstallation.html
> >>
> >>So I've intalled Glib 2.2.3.  But now Pango is giving me this error:
> >>
> >>
> >>checking for GLIB - version >= 2.1.3...
> >>*** 'pkg-config --modversion glib-2.0' returned 2.2.3, but GLIB (2.2.1)
> >>*** was found! If pkg-config was correct, then it is best
> >>*** to remove the old version of GLib. You may also be able to fix the 
> >>error
> >>*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing
> >>*** /etc/ld.so.conf. Make sure you have run ldconfig if that is
> >>*** required on your system.
> >>*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH
> >>*** to point to the correct configuration files
> >><<<
> >>
> >>It tells me where it's getting the 2.2.3 from, so why doesn't it tell me 
> >>where it's getting the 2.2.1 from??
> >>
> >>I've gone back and removed every directory on my system named glib-2.0 
> >>(after trying lots of other stuff with no success), and then 
> >>re-installed Glib 2.2.3, and it's still giving me the error.
> >>
> >>So...
> >>#1.  Where is the 2.2.1 coming from, and
> >>#2.  Wouldn't it make sense for the installer(s) be changed so that they 
> >>tell where they've found it, once they've found it?
> >>
> >>Thanks,
> >>Anthony
> >
> >
> >
> >