> Hey Ed,
> I bumped the ebuild to the snapshot of 20110831 last evening, I've
> successfully compiled it, but then python goes crazy.
> It says that it cant find libutil.so.0, but it is actually in the correct
> lib dir. I'm going to look into this even more now.
Hi, uclibc can break if you don't do a binary compatible upgrade.
Because it's so configurable, it's much easier to break it if you
accidently change something in the config which has big implications.
For example I think it proved very difficult to switch uclibc from non
hardened to hardened because it breaks before you can re-install?
Additionally, I forget the details now, but I think this bug hit some
people before - not sure if it's properly resolved in current uclibc either?
It's not something I recall running into though, so possibly a config
change has caused / will rectify things?