On Sunday 18 May 2008, David Breakey wrote:
> Hmm. Never messed with getlibs; I guess it automates the manual method
> I've always used. Will have to check it out.
>;
> On Sun, 2008-05-18 at 11:46 -0500, Tim Doty wrote:
> > They are very terse, but here are my current notes are:
>; >
>; > download getlibs
> > getlibs PageStream5Pro
> > getlibs -l libqtengine.so
>; > getlibs -l libqt-mt.so.3
> > getlibs -l highcontrast.so
> > getlibs -l libfile.so
> > getlibs -p libgnomevfs2-0
>; > sudo ln -s /usr/lib32 /usr/l32
> > sudo sed -i -e 's/usr/lib/usr/l32/g' /usr/lib32/libgnomevfs-2.so.
> > 0.2200.0
>
>; D'oh!
>
> Why didn't I think of that one? This is the very problem I had trying to
> run it against the 32-bit libs, and this should solve that very neatly.
>
> Just an FYI for anyone contemplating the same trick; notice that he
> substitutes 'l32' for 'lib'; this is VERY important, as you MUST match
> the byte-length exactly for whatever is being changed.
>
>; DO NOT try changing it to 'lib32'; that WILL cause things to break.
> Possibly in very nasty ways.
>
> If you're at all uncertain about this, use the chroot approach instead.
> It's substantially more resource-intensive, but is far safer.
>
> That said, this is a perfectly viable option as long as you're careful.
>
>; Apologies to anyone who already knows this; just wanted to warn anyone
> who might not be as tech-savvy.
an excellent observation I would have pointed out myself if I'd remembered. I
don't take credit for it, found it with respect to another 32-bit application
having similar problems.
Tim Doty
.
