Re: [gentoo-amd64] Re: revdep-rebuild keep on detecting a broken link referred to libqt-mt.so.3

[Beso]

2008/3/1, Duncan <1i5t5.duncan@×××.net>:
>
> Chris Brennan <xaero@××××××××××.net> posted
>
> 47C8D787.5060100@××××××××××.net, excerpted below, on  Fri, 29 Feb 2008
> 23:11:51 -0500:
>
>
> > app-emulation/emul-linux-x86-qtlibs seems to have been the culprit, I
> > don't need it for anything that I can tell. It's been removed for now
> > and I have moved on to building the app I intended to build when all
> > this started (which was The Gimp). As of the writing of this, it is
> > building.
>
>
> Cool! =8^)
>
> Why it'd be putting a 32-bit lib in the standard lib dir is beyond me.
> It's certainly a bug.  It should be in a 32-bit compatibility dir (IDR
> what it was for sure because as I said I don't do multilib now), with 64-
> bit libs in lib64, which is usually symlinked one way or the other to lib
> on a Gentoo system.  The only stuff that should go in lib itself (as
> opposed to lib64, even tho the two are linked, the package manager should
> still say lib64 for 64-bit) is bitness independent stuff.  For example,
> bash/perl/python scripts are allowed to install to straight lib.
>
> So hopefully you don't end up needing that emul package for anything and
> don't have to worry about it any more.


try to control if /usr/lib symlink goes on /usr/lib64 or on /usr/lib32. it
should never go to the 32bit lib on a 64bit machine. the same goes for the
/lib symlink.
also you might control what files has the emul-linux-x86-qtlibs via "qlist
emul-linux-x86-qtlibs" and see if it has merged something in the 64bit lib
(which shouldn't happen). also you might control the same thing with the the
64bit qt and see if there are some overlaps.


-- 
dott. ing. beso