> OK. I searched my disk for libg*-2.0.so* and deleted everything it > found. Then I searched my disk for glib-2.0 folders and deleted every > one. Re-installed glib-2.2.3 (to its default location, /usr/local), > and FINALLY Pango is happy.
I did need to run ldconfig before Pango would accept the setup (but I hadn't modified my /etc/ld.so.conf).
-Anthony
PS - still haven't gotten past the ORBit2 problem.
Anthony wrote:
OK. I searched my disk for libg*-2.0.so* and deleted everything it found. Then I searched my disk for glib-2.0 folders and deleted every one. Re-installed glib-2.2.3 (to its default location, /usr/local), and FINALLY Pango is happy.
Now I'm at the point of installing ORBit2. Its configure goes OK, but its make dies with this:
>>>
/bin/sh ../../libtool --mode=link gcc -g -O2 -o orbit-idl-2 orbit-idl-main.o orbit-idl-driver.o orbit-idl-backend.o orbit-idl-utils.o orbit-idl-c-backend.o orbit-idl-c-stubs.o orbit-idl-c-skels.o orbit-idl-c-headers.o orbit-idl-c-common.o orbit-idl-c-imodule.o orbit-idl-c-skelimpl.o orbit-idl-c-utils.o orbit-idl-c-typecode.o orbit-idl-c-deps.o -lpopt -lm -Wl,--export-dynamic -L/usr/local/lib -lIDL-2 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
mkdir .libs
libtool: link: cannot find the library `/usr/lib/libglib-2.0.la'
make[3]: *** [orbit-idl-2] Error 1
<<<
Why is it looking for that file in /usr when I just installed glib to /usr/local? pkg-config confirms the location:
bash-2.05b# pkg-config --modversion glib-2.0 2.2.3 bash-2.05b# pkg-config --libs glib-2.0 -L/usr/local/lib -lglib-2.0
And as you can see in the /bin/sh line above, ORBit2 gets the "-L/usr/local/lib" passed right into it... so why doesn't it look there?
-Anthony
Anthony wrote:
To recap: I installed Slackware 9.0 two weeks ago, which included glib 2.2.1. Now I'm trying to install Gnome 2.4, which means I need to install glib 2.2.3.
After installing glib 2.2.3, I get to the "install Pango" step, but Pango complains that it's found both glib 2.2.3 and 2.2.1.
I run Slackware's pkgtool and remove glib 2.2.1. It tells me that it was removed.
Re-run Pango's configure script, and now it says it can't find glib at all.
Re-install glib 2.2.3 (using the default location which is /usr/local), then re-run Pango's configure script, which still says it can't find glib at all.
Re-install glib 2.2.3, this time with --prefix=/usr, which is where glib 2.2.1 had been installed. Re-run Pango's configure script, and now it tells me that it AGAIN sees BOTH versions of glib, 2.2.3 and 2.2.1.
How can Pango possibly be finding v2.2.1, when I REMOVED it, and then installed 2.2.3 ON TOP OF where it the old version used to be??
Can anyone help me sort out this crap, or else just kill me? Thanks.
_______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
_______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
_______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
