I downloaded LAME from SourceForge and installed it using the following:

ROOT@/downloads/lame_3.97b2> gunzip lame-3.97b2.tar.gz
ROOT@/downloads/lame_3.97b2> tar -xf lame-3.97b2.tar
ROOT@/downloads/lame_3.97b2> cd lame-3.97/
ROOT@/downloads/lame_3.97b2/lame-3.97> ./configure
ROOT@/downloads/lame_3.97b2/lame-3.97> make
ROOT@/downloads/lame_3.97b2/lame-3.97> make install

It seemed to work fine and the command 'lame' works fine.

The problem is that none of the following commands work:

/usr/lame
/usr/bin/lame
/usr/sbin/lame
/bin/lame
/opt/lame

So where is the program installed? I'm using Suse 9.1 if that's any help.

"rpm -qi lame" gives:
"package lame is not installed"

The program pac cannot find it either, which kinda messes up my plans for converting all my wav music to mp3.

So 1, where is lame? and 2, how do I find out where a program is installed (instead of having to go through all the possiblities and using trial and error)?

when you run "make install" it will clearly show where it is placing the binaries. default location for a tarball is /usr/local/bin/. your rpm command will clearly not work as it's not an rpm...

Dude, you rock!

Thanks!

$which lame (for the app itself)
$whereis lame (for all the locations it has installed stuff to)

Hey, that's pretty cool... Thanks!

That $whereis command, does it find where all the config files and stuff for that program are installed? (The manual page says it only finds documentation and binaries).

Is there a way I can I find all the files a program uses? Ok, this is Linux, so not 'is there a way', but '*how* do I' find all the files a program uses?

there's is no way do this is completely, but then this might depend what you are referring to. you can use the ldd tool on a binary file to see what libraries it is linked to for function calls etc... but then this is in a totally different space to say, config files, which are arbitrary strings in a file. so files get opened in very different ways...

Yeah, I was actually thinking more of config files, but this still seems useful!

Ahh, looks like it's probably more trouble than it's worth. I'll probably come back to it sometime in the future - right now I have revision to do! :-( . Think I've kind of led the thread off topic a little anyway!

Probably best close it here. Thanks for all your help guys! You just never stop learning...

If you've got a bunch of files to convert, you might get some ideas from the people who have helped me here, here, and here.