> > > > > > Perhaps you should go back to a lower glib version. Latest versions of > > > such important packages might always have issues. > > > > What is the approved way to do this? > > There is no approved way to downgrade glibc. The output message from the > error you posted tells you why the devs will not provide you with a method > to do it. If you *really* want to do it, your could comment out the "if" > statement between lines 159 and 163 of the latest glibc ebuild. > > The only correct way I know of is to perform a reinstall. It'll probable be > quicker, easier and far less painful than trying to recover from ripping > the foundation out from under your OS... > > > However, did you notice that the parent poster mentioned glib and you have > attempted to downgrade glibc? > >
The issue that I have is that glibc is broken, probably due to my profile having at some point switched from a 64 bit profile back to i386. After discovering this, I tried to fix this by switching the profile back, and that's when my problems began. glibc appears to be broken, and causes errors when trying to compile (specifically, lib cpp fails the sanity check). Reinstalling glibc from a binary was recommended as a way to fix this, but I don't have access to a binary of the same or more recent vintage as the one already installed on my system. Trying to install an older version that I could find caused the glibc error. emerge -eav system causes the same errors, as glibc appears to require glibc to compile, and since it's not working, I have a circular dependency that I can't resolve. If its OK to do so, and has a chance of working, I could install an older version of glib. All I need to know is how to do this. Any pointers gratefully received. I'd really rather not have to rip out everything and re-install the OS (several days of work), as it's basically working right now - just won't upgrade at the moment. Thanks Jeff Jeff
