It's common to tell configure where to put the files. For instance, if I want the binary (executable) to install to /usr/bin, I can use
./configure --prefix=/usrThat way binaries will go into /usr/bin/ , images / sound files into /usr/share/ etc. If you don't specify a prefix, most programs assume that the prefix = /usr/local, so the most logical place to look would be /usr/local/bin. for kde programs, VL uses --prefix=/opt/kde
Instead of "make install", try using
checkinstall -LThis will create a .tlz vector package that you can easily install and remove. It won't exactly be repo ready but it works great. Also, you'll be able to search for the binary in the package info file:
grep bin/ /var/log/packages/ksensors-0.7.3
"make clean" just cleans the building directory. The best way to get a clean building directory is to remove the thing and extract the tarball again. It's not needed after installing something.
Try searching for ksensor instead (no capitals!), that should find you something. Also, if you're using slocate make sure you run "updatedb" first, as files that are newly installed are not in the database yet.