> usually it's autodetected. > > search your configure.log file for 'lame' and find out why it wasn't > detected. And if that doesn't work, try grepping the source for every instance of <lame.h>, and replace it with <lame/lame.h>, the file seems to live in that location on some systems...