Dirk, Just rebuild paludis, paludis -i paludis
it will go away. TBH i'm not positive what's doing it, I setup a 2008.0 chroot, installed 0.26.2, then updated to 0.28 and it went cleanly and perfectly. So i'm guessing it's some 2007.0 crud that is laying around that broke it. (I didn't update to libtool 2.2.4 either, so that may be also a plausability). On Jul 12, 2008, at 7:19 AM, Dirk Heinrichs wrote: > Am Samstag, 12. Juli 2008 schrieb Ciaran McCreesh: >> On Sat, 12 Jul 2008 16:05:48 +0200 >> >> Dirk Heinrichs <[EMAIL PROTECTED]> wrote: >>> Looks to me like /usr/lib/ruby/site_ruby/1.8/i686-linux/Paludis.so >>> was linked against version 26 which was already installed on the >>> system while compiling paludis 0.28 and which was then replaced with >>> the new version 28 during merge phase. >>> >>> To verify this, I installed paludis 0.28 again. This time, playman >>> is >>> linked with the correct lib and works as expected. >> >> Have a look at ticket:616. So far as we can see, this is hitting >> people >> who have LDPATH=/usr/lib set in their environment, which is making >> libtool ignore our explicit orders to link against the newly built >> library and use the one on / instead. > > Hmm, I have LDPATH set, but it doesn't contain /usr/lib. > > Bye... > > Dirk > > > !DSPAM:4878bd7d31281804284693! > _______________________________________________ > paludis-user mailing list > [email protected] > http://lists.pioto.org/mailman/listinfo/paludis-user > > > !DSPAM:4878bd7d31281804284693! _______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
