If you do; ls -l /usr/lib/libgphoto2.so.2
what do you see? On Thu, 22 Sep 2005, Leslie Katz wrote: > I have not found it possible to compose this post in my email program. > I am composing it instead in a text editor and will then copy it to an > email form. That means that I will not be repeating in my email as > posted any history. > > In his most recent post, Alan first suggested searching in various > locations to try to find whether v 2.1.5 of libgphoto2 is still hanging > around and being used, instead of v 2.1.6. > > My following the letter of that suggestion would have been pointless, > given my state of knowledge. I simply don't know how to determine > whether any files I might find are part of v 2.1.6 or v 2.1.5, apart > from their having the appropriate number in their name. > > I therefore searched the entire filesystem for any files or folders > with "2.1.5" in their name. I got the following results only: > > /var/cache/yum/updates-released/headers/gphoto2-2.1.5-1.1.i386.hdr > /var/cache/yum/updates-released/packages/gphoto2-2.1.5-1.1.i386.rpm > > Alan next suggested that I should find gphoto2's process number while > it was running and then run a command based on that process number to > find which library file was being used. > > Again, my ignorance prevented my doing that. I found reference on the > Web to the "ps" command, which I assume would be used to find the > process number, but, since gphoto2 isn't like a service, I couldn't > figure out how to take a snapshot with "ps" while gphoto2 ran very > briefly. > > As I understood Stephen's suggestion that I use "ldd", it might be an > alternative to Alan's suggestion just mentioned, so I tried it. > > When I ran "ldd /usr/bin/gphoto2", I got the following results: > > libexif.so.9 => /usr/lib/libexif.so.9 (0x03f4c000) > libm.so.6 => /lib/tls/libm.so.6 (0x00834000) > libgphoto2.so.2 => /usr/lib/libgphoto2.so.2 (0x00ae6000) > libgphoto2_port.so.0 => /usr/lib/libgphoto2_port.so.0 (0x00aaa000) > libpopt.so.0 => /usr/lib/libpopt.so.0 (0x00caf000) > libc.so.6 => /lib/tls/libc.so.6 (0x00708000) > /lib/ld-linux.so.2 (0x006ee000) > libdl.so.2 => /lib/libdl.so.2 (0x00859000) > > Trying to think of anything useful I might do with that information, I > used the file search facility, which turned up some things which seemed > to me to be of significance. > > Searching for "libexif.so.9" found two files, both said to be in > /usr/lib: "libexif.so.9.1.2", said to be a shared library of 75 KB; and > "libexif.so.9", said to be a "link (broken)" of 16 bytes. > > Searching for "libm.so.6", found three files of that name, one said to > be in /lib, one said to be in /lib/i686 and one said to be in /lib/tls. > Each was said to be 13 bytes in size and of type "link (broken)". > > Searching for "libgphoto2.so.2" found two files said to be in /usr/lib. > One was said to be "libgphoto2.so.2", 19 bytes long and "link > (broken)". The other was said to be "libgphoto2.so.2.0.3", a shared > library of 256.9 KB. > > Searching for "libgphoto2_port.so.0" found two files said to be in > /usr/lib. One was said to be "libgphoto2_port.so.0.5.1" a shared > library of 54.5 KB; the other was said to be "libgphoto2_port.so.0", a > "link (broken)" of 24 bytes. > > Searching for "libpopt.so.0" found two files said to be in /usr/lib. > One was said to be "libpopt.so.0.0.0" a shared library of 27.2 KB; the > other was said to be "libpopt.so.0", a "link (broken)" of 16 bytes. > > Searching for "libc.so.6" found three files with that name, one said to > be in /lib, another in /lib/i686 and the last in /lib/tls. Each was a > "link (broken)" of 13 bytes. > > Searching for "/lib/ld-linux.so.2" found a single broken link of that > name of 11 bytes. > > Searching for "libdl.so.2" found a single file of that name in /lib. It > was a broken link of 14 bytes. > > If I've got this right, each of the files said to be one of gphoto2's > shared library dependencies is a link going anywhere. > > Finally, Alan suggested I post the complete log file from my gphoto2 > run. Yet again, I don't know how. gphoto2's error messages speak of > issuing commands with debugging on and I tried to do that. However, I > could find no file especially created by gphoto2 with the debugging > information in it, nor could I find anything that seemed to me to be > relevant in /var/log/messages, which was the only other place I knew of > in which to look. > > I know my ignorance must be irritating. Again, I apologise for it. I'm > hopeful, though, that the "ldd" output may point to the end of this > saga. > > Leslie > > > > > > > > > > > ____________________________________________________ > Do you Yahoo!? > The New Yahoo! Movies: Check out the Latest Trailers, Premiere Photos and > full Actor Database. > http://au.movies.yahoo.com > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > [email protected] > To unsubscribe, use the last form field at: > https://lists.sourceforge.net/lists/listinfo/linux-usb-users > -- /------------------------------------+-------------------------\ |Stephen J. Gowdy | SLAC, MailStop 34, | |http://www.slac.stanford.edu/~gowdy/ | 2575 Sand Hill Road, | |http://calendar.yahoo.com/gowdy | Menlo Park CA 94025, USA | |EMail: [EMAIL PROTECTED] | Tel: +1 650 926 3144 | \------------------------------------+-------------------------/ ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
