glibc doesn't seem to want to downgrade.

[AyaJulia]

Following a suggestion made elsewhere on these forums (here), I've been trying to downgrade my glibc from 2.3.2-r1 to 2.3.1-r4. This has been causing a few problems for me that I'm not aware of how to fix.

Turning autoclean off has fixed the obvious problem of having the version of glibc that everything is using go away, but I still don't know how to get everything to use the new (downgraded) version. emerge -ep world shows portage upgrading me to glibc 2.3.2-r1 early on and then much later (within the last ten packages compiled or so) building the version I actually want, even though I have 2.3.1-r4 pinned in my world file.

Can anyone help me with either (a) getting emerge -e world to make everything use the version of glibc I want or (b) somehow fooling the game into believing it's using glibc 2.3.1 so it will stop crashing?

Thanks in advance.

[stikboy]

Just because I found out about this today I'll suggest putting the following line in /usr/portage/profiles/package.mask

>=sys-libs/glibc-2.3.2

and then run emerge -up glibc

this will mask any version greater than 2.3.2, so should let you build the one you want