On Sun, 23 Nov 2003 21:12:52 +0200 Alexandru GHERMAN <[EMAIL PROTECTED]> wrote:
> Hello, > > I just made an unsuccesfull attempt tu install a new version of glibc. The new > > glibc 2.3.3 with emerge -u system. The emerge stopped with the following > output : > > >>> Regenerating /etc/ld.so.cache... > * Caching service dependencies... > > [ ok ] > >>> Auto-cleaning packages ... > !!! Invalid db entry: /var/db/pkg/*sys-fs/devfsd!!! Invalid db > entry: /var/db/pkg/*sys-fs/devfsd > >>> No outdated packages were found on your system. > > > * Regenerating GNU info directory index... > * Processed 63 info files: 2 errors; run with emerge --verbose to view > errors. > > Now any emerge I try I get : > comosicus root # emerge -u system > /usr/bin/python: /lib/libc.so.6: version `GLIBC_2.3.3' not found (required > by /usr/lib/libpython2.3.so.1.0) > > Can anybody help me please. It seems that glibc didnt installed correctly > because I have still the old version : > > comosicus root # qpkg -I -v | grep glibc > sys-libs/glibc-2.3.2-r3 * > > Is there somewhere some GLIBC version variable I shoud change ? > Check bugzilla and the archives. I believe this was thoroughly discussed a few weeks/months ago. -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
