On Thursday 01 July 2010 00:15:34 Mick wrote: > > I remember now what I eventually did to fix all my libpng problems back > > > > then: > > > > > > unmerge libpng > > delete everything left with libpng in it's name > > emerge -pvuND world just to see what was now busted > > same with revdep-rebuild > > re-emerge libpng and let portage pick the version to merge > > emerge -avuND world > > revdep-rebuild > > > > repeat till no problems reported > > > > > > and lafilefixer --justfixit somewhere in the mix as well just for good > > measure. > > > > > > > > This is called the "throw shit at the wall and hope some of it sticks" > > method of updating systems. By happy good fortune, it worked out for me. > > > > > > > > aka the dark underside of source-based systems :-) > > I'm sure that I followed your scientific approach too because my system > still works ... although I may have lost the will to live somewhere in > between the lafilefixer and revdep-rebuild for the nth time and decided to > emerge -e world. :-)) > > Strangely enough two other x86 boxen were updated without any much drama.
:-) On the front page of gentoo.org several blogs are reference that mention this issue. In one of them, the author shows evidence that the same binary was trying to link at one point to a 32 bit lib and at another point link to a 64 bit lib..... All random of course, causing no end of mysterious failures, and explains why some people had success re-merging cairo, other with something else .... Truly bizarre. But it might go a ways to explaining why your 32 bit systems were unaffected? -- alan dot mckinnon at gmail dot com
