On 11/17/2009 11:06 AM, Alan McKinnon wrote:
Yes, I have read this in /var/portage/sys-libs/glibc/files/eblits/pkg_setup.eblit and I understand the risks.if has_version '>'${CATEGORY}/${PF} ; then eerror "Sanity check to keep you from breaking your system:" eerror " Downgrading glibc is not supported and a sure way to destruction" die "aborting to save your system" fi I want to do it anyway.
I have never done this on a package-managed system but I did have to downgrade glibc on a slackware system once. It's very VERY ugly; all kinds of implementation details get exposed as special symbols, or new symbol versions, or whatever, that make going backwards a mess.
The way I was told to do it was to get a compiled copy of lower glibc version into an alternative install path, like /usr/local/glibc, and rebuild everything against that copy. You could have emerge build 2.10 into an alternative --root, or go get a binary package of 2.10 and uncompress it somewhere. Then update CFLAGS and LDFLAGS to include the correct -L and -I parameters pointing to /usr/local/glibc/{lib,usr/lib,include}.
When I did it, I rebuilt everything on my system twice, just to be safe. First time through, you build against the extra copy of glibc, including building a downgraded glibc in the proper system location, and having the build tools link to the correct lower version. Then you remove the CFLAGS/LDFLAGS and rebuild everything again, this time against the downgraded version in the correct location, and then you can remove your extra copy. I'm not entire positive that second one was strictly necessary but it worked.
Or you can just back up your data and reinstall :)
A multitude of apps that used to run just fine now give "free(): invalid pointer" errors since I upgraded to glibc-2.11
Make sure you file bug reports on these. The programs are probably doing buggy things that glibc used to be rather forgiving about. I believe in 2.11 they added extra checks to the memory management used by C++ programs, though I don't know specifics. This would catch things like using delete where they meant delete[], or free() on something allocated with new.
The standard says the behavior of this type of operation is undefined, so glibc is technically free to do "anything it wants". Unfortunately, when glibc is nice and make that "anything" be "what you wanted it to do anyway" it encourages people do keep doing bad things, thus the ever-increasing strictness of the library.
--Mike
