Hi, I recently needed to upgrade to a newer version of gtk / glib and compiled from source. Having succeded, I used YAST to uninstall the rpms of those packages that I had installed as part of my SuSE 7.0 distro and ran a make install on the new versions. All went well, and the new versions were installed to /usr/local/bin. I ran ldconfig and found a few unresolved references. Investigation showed that the original libraries were still in /usr/bin. In the end, after making some symlinks I have managed to get all working, but I am left with the feeling that I have been working in the dark and that there should be a better and more certain way of doing things. I am also puzzled as to why the uninstall of the rpms did not clear out the original libraries. Can anyone offer any general advice on what to do when upgrading libraries ? Thanks, Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Hi, Did you also uninstall any glib/gtk-devel packages? In my experience, it often proved sensible to uninstall libraries before compiling / building new versions. Possibly, your new libgtk included old glib headers and got linked against the old glib, though the configure script normally detects this. This should be mentioned in the accompanying README and INSTALL files. In your case, I should proceed as follows: uninstall glib, gtklib and any development packages. configure, compile, build and install the new glib. configure, compile, build and install the new gtklib. In these cases, I often find it helpfull to install the SuSE source rpm and examine the spec file to see how the SuSE version has been built. Sometimes, adapting it to a new version and building your own rpm package is quite straightforward. Good luck, Tim On Fri, Sep 14, 2001 at 09:03:55AM +0100, quintaq@yahoo.co.uk wrote:
Hi,
I recently needed to upgrade to a newer version of gtk / glib and compiled from source. Having succeded, I used YAST to uninstall the rpms of those packages that I had installed as part of my SuSE 7.0 distro and ran a make install on the new versions. All went well, and the new versions were installed to /usr/local/bin. I ran ldconfig and found a few unresolved references. Investigation showed that the original libraries were still in /usr/bin. In the end, after making some symlinks I have managed to get all working, but I am left with the feeling that I have been working in the dark and that there should be a better and more certain way of doing things. I am also puzzled as to why the uninstall of the rpms did not clear out the original libraries.
Can anyone offer any general advice on what to do when upgrading libraries ?
Thanks,
Geoff
On Fri, 14 Sep 2001 21:57:40 +0200
Tim van Venrooij
Hi,
Did you also uninstall any glib/gtk-devel packages? In my experience, it often proved sensible to uninstall libraries before compiling / building new versions.
Thank-you for the response. I had the devel packages installed and I did unintall using YAST. I also checked using xrpm that the packages were not present. I am trying to keep to a policy of having only software that I have compiled on my system and what I do is to compile the sources before uninstalling any existing rpms (in case I run into compilation problems). If compilation succeeds I unistall the rpms and then do a make install of the new version.
Possibly, your new libgtk included old glib headers and got linked against the old glib, though the configure script normally detects this. This should be mentioned in the accompanying README and INSTALL files. In your case, I should proceed as follows:
uninstall glib, gtklib and any development packages. configure, compile, build and install the new glib. configure, compile, build and install the new gtklib.
I will do it that way in future.
In these cases, I often find it helpfull to install the SuSE source rpm and examine the spec file to see how the SuSE version has been built. Sometimes, adapting it to a new version and building your own rpm package is quite straightforward.
I will also give that a try. I think also that if I am going to keep to my policy of compiling everything I install I had better make time to complete my "Teach Yoursel C for Linux Programming" course as soon a possible and get a better knowledge of libraries in general. Thanks again, Regards, Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
participants (2)
-
quintaq＠yahoo.co.uk -
Tim van Venrooij