Ah, I see... looks like there is a problem with the samba package.
I checked the SONAME (the library that is linked to when you do a -lsmbclient) of libsmbclient.so and it's libsmbclient.so.0, but the samba package doesn't include it at all. This is bad for samba.
the mystery clears up :-)
]]>I checked the SONAME (the library that is linked to when you do a -lsmbclient) of libsmbclient.so and it's libsmbclient.so.0, but the samba package doesn't include it at all. This is bad for samba.
]]>These are dynamically loaded modules that are only used by gnome and kde if samba is installed. The post install scripts of both explain that if you want samba you'll have to install the samba package.
I think this is the best way to handle optional dependencies.
yes, it is
but the mystery is:
i have samba installed
[damir@Asteraceae /]$ pacman -Q samba
samba 3.0.6-2
should there not be libsmbclient.so.0 somewhere to work?
]]>I think this is the best way to handle optional dependencies.
]]>Have you tried making a symlink with the name libsmbclient.so.0 going to libsmbclient.so?
i don't use samba, because have nowhere to connect to, so i don't mind
ln is for sure a solution, but what's the reason?
experiments with ldd'ing all bins of my system gave me this results i wonder about
]]>/opt/gnome/lib/gnome-vfs-2.0/modules/libsmb.so:
libsmbclient.so.0 => not found
/opt/kde/lib/kde3/kio_smb.so:
libsmbclient.so.0 => not found
however, this file do not exist in my system
what exsist is this:
[damir@Asteraceae ~]$ locate libsmbclient.so
/usr/lib/samba/libsmbclient.so
/usr/lib/libsmbclient.so
is this normal?
]]>