On Tuesday 23 May 2006 15:31, Paul de Vrieze wrote:
> On Tuesday 23 May 2006 14:40, Hamish Marson wrote:
> > Peter Humphrey wrote:
> > > On Friday 12 May 2006 19:16, Duncan wrote:
> > >> You hit the infamous libexpat bug!
> > >
> > > I did too, and after several attempts to get revdep-rebuild to fix
> > > the problem I gave up and reinstalled from scratch. Now I can't get
> > > arts to run - it gobbles 95% CPU from when I log in to when artsd
> > > gets killed on a cpu overload. I've raised a bug on this.
> >
> > Infamous expat bug? Would this be where you update libexpat because
> > something wants the later verison & then everythig fails because it
> > can't find libexpat.0?
> >
> > Grr... I hit that last night... I'm still running an emerge -D world
> > to re-install everything (Since revdep-rebuild failed for me).
>
> What you can do to keep a useable system in the meantime is to create a
> symbolic link from "/usr/lib/libexpat.so.1" to "/usr/lib/libexpat.so.0". As
> the ABI did not actually change this is sufficient to keep things working
> while you recompile the stuff.

if you do that, and remove the libexpat.so.0 symlimk after the rebuild, a lot 
of things will stop working ;)

Been there, done that, did not help.

Removing libexpat.so.0 and revdep-rebuild did the job.
-- 
gentoo-amd64@g.o mailing list