suvayu ali wrote:
> Not quite:

Yes, quite. Please don't snip my e-mails to exclude vital information.

$ ldd /opt/google/talkplugin/libnpgoogletalk64.so
        linux-vdso.so.1 =>  (0x00007ffff6562000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f48f6ead000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f48f6c92000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f48f698a000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f48f6706000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f48f636c000)
        /lib64/ld-linux-x86-64.so.2 (0x00000034c5c00000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f48f6156000)

As shown above (and in my original mail) Google supplies a *native 
64-bit binary*.

Google did not package the RPM properly (which is typical of them). The 
RPM calls for "lib4l2.so.0" in a non-arch specific manor, so yum 
installs both arches of the libv4l package. It never uses the 32-bit 
library.

$ rpm -q google-talkplugin --requires | grep libv4l
libv4l2.so.0

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Reply via email to