On Wed, Jun 18, 2008 at 11:37 AM, Ryan Lewon <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 11:29 AM, James G. Sack (jim) <[EMAIL PROTECTED]>
> wrote:
>>
>> Carl Lowenstein wrote:
>> >..
>> > Answer to second question is rather verbose. Well, 37 lines,
>> > including the command synopsis.
>> >
>> > $ mkdir /tmp/foo; cd /tmp/foo
>> > $ rpm2cpio /data/transfer/opera-9.50.gcc4-shared-qt3.x86_64.rpm | cpio
>> > -idv
>> > $ cd /tmp/foo/usr/lib/opera/9.50
>> > $ ldd opera
>> > linux-vdso.so.1 => (0x00007fffe91fe000)
>> .
> That is odd, if the binary is looking for it in the right places, your
> safe bet is you can try to launch it and if it works, just rpm -ivh
> --nodeps opera-9.50.gcc4-shared-qt3.x86_64.rpm and it should play
> nice.
>
I can't launch it from /tmp/foo because there are some hard-coded
absolute paths. The executable is in
/tmp/foo/usr/lib/opera/9.50/
It wants to read from /usr/share/opera/locale/ If it had been
properly built, it should look in
../../../share/opera/locale/ if I counted the ../ correctly.
So I just did the "rpm -ivh --nodeps" thing and Opera seems to be
working. See kplug-newbie for my initial impressions, formed while
running the 32-bit version.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
