Tilted Forum Project Discussion Community - View Single Post

n0nsensical · 02-14-2005, 03:19 AM

They're linker errors...some library with the function g_return_if_fail_warning is not being linked. I searched, and apparently it has to do with having two glibs installed. This is related to why pkg-config --modversion glib-2.0 returned 2.2.3 when you just installed 2.6.2. What's probably happening is you have 2.2.3 in /usr and 2.6.2 in /usr/local. gaim is being compiled with the 2.6.2 versions of the headers with g_return_if_fail_warning, but ld (the linker) is getting the 2.2.3 version of the library where it's not defined.

The best solution is to get rid of one of the two versions entirely, most likely the old one if you can, which you can probably do with the package manager. In the meantime, you can get the gaim binary built by pointing ld to the right library. Generally the configure script deals with getting the right version of a library, and yes, as it suggests, setting that environment variable will probably solve the problem. I think the one you're looking for is PKG_CONFIG_PATH. If you're using bash (you probably are), do
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
but I've never used pkg-config so I can't help much with the details on that one.

You might also try
export LD_LIBRARY_PATH="/usr/local/lib:$LD_LIBRARY_PATH"
but I don't think it will matter because the linker is already getting that -L/usr/local/lib.

Of course, as was suggested you can probably just use the package manager to get the gaim binaries without having to screw around with this stuff as it can be really complicated and confusing. Upgrading libraries tends to cause problems especially when they come from different places.

02-14-2005, 03:19 AM	#8 (permalink)
n0nsensical Junkie Location: San Francisco	They're linker errors...some library with the function g_return_if_fail_warning is not being linked. I searched, and apparently it has to do with having two glibs installed. This is related to why pkg-config --modversion glib-2.0 returned 2.2.3 when you just installed 2.6.2. What's probably happening is you have 2.2.3 in /usr and 2.6.2 in /usr/local. gaim is being compiled with the 2.6.2 versions of the headers with g_return_if_fail_warning, but ld (the linker) is getting the 2.2.3 version of the library where it's not defined. The best solution is to get rid of one of the two versions entirely, most likely the old one if you can, which you can probably do with the package manager. In the meantime, you can get the gaim binary built by pointing ld to the right library. Generally the configure script deals with getting the right version of a library, and yes, as it suggests, setting that environment variable will probably solve the problem. I think the one you're looking for is PKG_CONFIG_PATH. If you're using bash (you probably are), do export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig but I've never used pkg-config so I can't help much with the details on that one. You might also try export LD_LIBRARY_PATH="/usr/local/lib:$LD_LIBRARY_PATH" but I don't think it will matter because the linker is already getting that -L/usr/local/lib. Of course, as was suggested you can probably just use the package manager to get the gaim binaries without having to screw around with this stuff as it can be really complicated and confusing. Upgrading libraries tends to cause problems especially when they come from different places. __________________ "Prohibition will work great injury to the cause of temperance. It is a species of intemperance within itself, for it goes beyond the bounds of reason in that it attempts to control a man's appetite by legislation, and makes a crime out of things that are not crimes. A Prohibition law strikes a blow at the very principles upon which our government was founded." --Abraham Lincoln Last edited by n0nsensical; 02-14-2005 at 03:27 AM..