Kyle Burton on Fri, 20 Aug 1999 09:43:20 -0400 (EDT) |
Before you install packages like this (tar.gz archives) for software you already have installed on your redhat system, you should first use rpm to remove the software in question. If you take the time, you can build your own rpm our of the tar.gz arvhive, and then use rpm to 'upgrade' the existing package...or you can use someone else's binary rpm to upgrade your system. there are several reasons why it might not be working -- as you have suggested, the tar.gz archive may have installed it into a differnt location than where the rpm existed, or you may have to run ldconfig (which is usually done in the rc scripts when you boot) to rebuild the shared lib database. hope some of this helps... k ------------------------------------------------------------------------------ "Think determanisticly, act randomly." -- Unknown mortis@voicenet.com http://www.voicenet.com/~mortis ------------------------------------------------------------------------------ On Thu, 19 Aug 1999, Michael Leone wrote: > Having a problem installing the latest glib (1.2.3) - on Red Hat 5.2. > > I downloaded the program (to /tmp); unpacked the tgz; and followed the install directions: > > ./configure > make > make install > > while logged in as root; saw no errors. > > Looked like it worked. > > Went to install the latest gtk; it complained that my glib was an old version. To which I replied "Huh?". :-) > > Looked like the glib got installed to /usr/local/lib. Have no idea if that's right, or if I have an older glib still around somewhere. > > Clues, anyone? > > _______________________________________________ > Plug maillist - Plug@lists.nothinbut.net > http://lists.nothinbut.net/mail/listinfo/plug > _______________________________________________ Plug maillist - Plug@lists.nothinbut.net http://lists.nothinbut.net/mail/listinfo/plug
|
|