SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-20-2008, 01:35 PM
| ||||
| ||||
 glibc *.so files location... Hi all, I'm sure that You can help me... I'm using 10.0 upgraded since last current. I upgraded from current glibc-2.3.6 but what is the default directory for glibc files ? Now I have *.so in: /lib /lib/tls and for example ld-2.3.5.so is still present with ld-2.3.6.so from the last glibc-2.3.6-i486-2.tgz I saw that ld.2.3.6.so is in: lib/tls/incoming/ld-2.3.6.so lib/incoming/ld-2.3.6.so but with the same date (When I upgraded) ld-2.3.6.so is also in my /lib Furthermore after the upgrade from 2.3.5 to 2.3.6. in /lib and /lib/tls is still present ld-2.3.5.so. and no trace for the directory lib/incoming/ with all the *.so listed in tgz file Any idea to solve this MESS ? TIA Andrea      |
|
02-20-2008, 01:35 PM
| ||||
| ||||
| Re: glibc *.so files location... On Sun, 12 Feb 2006 23:51:31 +0100, "" wrote: > but with the same date (When I upgraded) ld-2.3.6.so is also in my > /lib > Furthermore after the upgrade from 2.3.5 to 2.3.6. > in /lib and /lib/tls is still present > ld-2.3.5.so. > and no trace for the directory > lib/incoming/ > with all the *.so listed in tgz file > Any idea to solve this MESS ? This is normal. Inside the .tgz package you will find the lib/incoming directory: it's a staging area. You will also find install/doinst.sh. This script does what is necessary to upgrade glibc on a running system -- which includes the requirement to use the lib/incoming staging directory. Check out /var/log/scripts/glibc* The reason that there remains the glibc-2.3.5 shared objects is simple: When removepkg runs, it determines the package contents by examining /var/log/packages/glibc-2.3.5-blah It finds /lib/incoming in that file: but since the install/doinst.sh script moved the libs from that directory into /lib, it is unable to remove the 2.3.5 versions from the filesystem. You will find this with other packages where the .config file is named .conf.new -- removepkg simply has no clue about it thus you will occasionally find orphaned file and dirs on your filesystem. s. -- The Biscuit Appreciation Society : www.biscuit.org.uk Experimental ARM Linux distribution: www.armedslack.org | "Washing machines live longer with Calgon" |
Linear Mode
