-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Hartman wrote: > On Mon, Aug 24, 2009 at 3:38 PM, Keith Dart<ke...@dartworks.biz> wrote: >> === On Mon, 08/24, Paul Hartman wrote: === >>> After switching to the 10.0 >>> profile, Xcb and other X-related things were emerged/upgraded, though, >>> and I ran xcb-rebuilder.sh and revdep-rebuild both of which found no >>> problems. >> === >> >> interesting. On my system some library named libxcb-xlib is used: >> >> >> 315 $ ldd /opt/vmware/workstation/lib/vmware/bin/vmware | grep xcb >> libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 >> (0x00007ff7f67be000) >> >> But the new X libraries in 10.0 profile remove that file so it fails to >> dynamically link that library. >> >> Maybe I need to run the overlay... > > I've always been using vmware overlay, when new kernels and other > things that break vmware, it usually has a fixed version within a few > days. Right now I'm using vmware-modules 1.0.0.25 and > vmware-workstation 6.5.3.185404. > > $ ldd /opt/vmware/workstation/lib/vmware/bin/vmware | grep xcb > libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f7de0aac000) > > Seems vmware has updated it in the newer version. > >
Just because ldd reports a library doesn't mean that there is a hard dependency on that library. If ../bin/vmware links against libX11.so.6, but not libxcb*, and libX11.so.6 is linked against libxcb-xlib.so.0, then ldd will report libxcb-xlib.so.0, because it is an indirect dependency. To find direct dependencies, you can use `scanelf -qF '#F%n' /path/to/file`, which will output a comma-separated list of libraries (for instance, "libxcb.so.1,libdl.so.2,libc.so.6"). - -- ABCD -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqTH98ACgkQOypDUo0oQOoX8QCcCbmyWpDdzL7KpjYsK2togFFa 4qUAoLJAh64H0hOYQtyR8w4L8iIChhiy =93An -----END PGP SIGNATURE-----
