21883 – After an emerge -u world, i couldn't use emerge anymore (libpthread.so)

Bug 21883 - After an emerge -u world, i couldn't use emerge anymore (libpthread.so)

Summary: After an emerge -u world, i couldn't use emerge anymore (libpthread.so)

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	x86 Linux

Importance:	Low critical (vote)
Assignee:	Gentoo Release Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-05-29 05:04 UTC by Laurent PEQUIN
Modified:	2003-05-29 12:07 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Laurent PEQUIN 2003-05-29 05:04:31 UTC

I have made an emerge -u world, everything went right, but once the update was
complete, I couldn't use emerge anymore (even if i type 'emerge' without options) :
root sur locki # emerge
python2.2: /lib/libpthread.so.0: version `GLIBC_2.3.2' not found (required by
python2.2)

I know that the update was on gcc, glibc, emerge and python. But I can't tell
you more about this issue...

Comment 1 Jason Waldhelm 2003-05-29 12:01:08 UTC

have you tried running etc-update and env-update?

Comment 2 Jon Portnoy (RETIRED) gentoo-dev

2003-05-29 12:07:44 UTC

The problem is that you upgraded glibc at some point, probably by using ACCEPT_KEYWORDS="~x86" - then downgraded glibc, probably by removing those keywords (or switching between them).

You can recover from this by grabbing the glibc tarball from http://cvs.gentoo.org/~avenj/bins/ and installing it using the method specified in the README in that directory. Stick to using ACCEPT_KEYWORDS="~x86" after that.

For further assistance, please try the forums or the IRC channel.