Re: gtk+ 2.24 installation problems




Hello all,

I've figured out a bit more with my installation issues but am still
stuck. There are actually a number of pkgconfig directories on my CentOS
6.2 system. There's a whole scad of .pc files in /usr/lib64/pkgconfig,
including glib-2.0.pc, so that would seem to be where CentOS originally
put all of them. (I should note if I haven't already that this is an
x86_64 system.) My recent glib install dumped the new .pc file into
/lib64/pkgconfig, however -- /lib64 is the original CentOS location
of libglib-2.0.so.0.2200.5, so I eventually re-ran my own glib configure
to dump the new libglib-2.0.so.0.2793.0 into the same directory, i.e.,
I did './configure --prefix=/usr --libdir=/lib64'. The glib install
wasn't entirely happy with this, however:

Making install in gthread
make[1]: Entering directory `/export/ctrobotv0d/glib-2.27.93/gthread'
Making install in .
make[2]: Entering directory `/export/ctrobotv0d/glib-2.27.93/gthread'
make[3]: Entering directory `/export/ctrobotv0d/glib-2.27.93/gthread'
test -z "/lib64" || /bin/mkdir -p "/lib64"
 /bin/sh ../libtool   --mode=install /usr/bin/install -c   libgthread-2.0.la '/lib64'
libtool: install: error: cannot install `libgthread-2.0.la' to a directory not ending in /usr/lib
make[3]: *** [install-libLTLIBRARIES] Error 1
make[3]: Leaving directory `/export/ctrobotv0d/glib-2.27.93/gthread'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/export/ctrobotv0d/glib-2.27.93/gthread'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/export/ctrobotv0d/glib-2.27.93/gthread'
make: *** [install-recursive] Error 1

It otherwise seemed to complete OK, however, so after I manually copied
my new glib-2.0.pc into /usr/lib64/pkgconfig where pkg-config wanted to
find it, I got my gdk-pixbuf configure to complete without complaining
that there was an outdated glib installed. Unfortunately the gdk-pixbuf
build did not go so well:

mv -f .deps/gdk-pixbuf-csource.Tpo .deps/gdk-pixbuf-csource.Po
/bin/sh ../libtool  --tag=CC   --mode=link gcc -std=gnu99  -DGDK_PIXBUF_DISABLE_DEPRECATED 
-DG_DISABLE_DEPRECATED -g -O2 -Wall   -o gdk-pixbuf-csource gdk-pixbuf-csource.o libgdk_pixbuf-2.0.la 
-L/lib64 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lpng12 -lm 
libtool: link: gcc -std=gnu99 -DGDK_PIXBUF_DISABLE_DEPRECATED -DG_DISABLE_DEPRECATED -g -O2 -Wall -o 
.libs/gdk-pixbuf-csource gdk-pixbuf-csource.o  ./.libs/libgdk_pixbuf-2.0.so -L/lib64 -lgio-2.0 -lgobject-2.0 
/lib64/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so -lrt -lpng12 -lm
./.libs/libgdk_pixbuf-2.0.so: undefined reference to `g_simple_async_result_take_error'
collect2: ld returned 1 exit status
make[4]: *** [gdk-pixbuf-csource] Error 1

Does anyone know what's up with g_simple_async_result_take_error? I found
a few of reports of similar errors on the web but nothing that has led
me to a solution so far.

My problems seem to be rooted in the multiplicity of library directories
on my CentOS x86_64 system (/lib, /lib64, /usr, /usr/lib64) and the related
configure/pkg-config/libtool confusion. Can anyone with any experience with
this point me to a path out of this swamp before I corrupt my whole GTK+
compilation environment, new or old?

Thanks!

Roger Davis



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]