mplayer audio in fedora18

[rholme]

Built and installed mplayer on Fedora 18 (had working before in F-16, 12).

I had some issues with needed development versions of gtk and zlib to build - apparently the .h files needed are only in the development release, even though the libraries appear to be here by default.
The below fixed the config and make for mplayer for me (64 bit version).
yum install zlib-devel.x86_64 gtk2-devel.x86_64

However my mplayer has NO SOUND AT ALL and it used to work fine. Other system sound tests work fine as does Skype.
The only difference I see is that in Fedora 16 (and 12), the system-settings sound showed both the intenal (on the monitor) speakers AND the external plugged in SONY speakers that I use.
The fedora 18 system-settings sound menu now only shows ONE output device (internal), but when I test THERE, it uses the speakers (as does skype)..

I tried mplayer -ao XXX with each of the 5 below options (well not null).
Most of them just say "No Audio" as there is no device.
"mplayer -ao help" yields:

Available audio output drivers:
oss OSS/ioctl audio output
mpegpes DVB audio output
v4l2 V4L2 MPEG Audio Decoder output
null Null audio output
pcm RAW PCM/WAVE file writer audio output

Suggestions appreciated.

[bonedome]

Hello
I've been away for a while but looking at that list of audio drivers, neither alsa or pulse are listed, have a look in the configue log near the bottom should be a list of enabled drivers.
mplayer should find everything required i.e you don't need to add any options to configure but if something is not found you might find in the log it just says something like alsa (not found) I've never come across this so maybe there is some alsa or pulse devel package required.
You will have to do a make clean (or is it distclean) before make again if memory serves

[george_toolan]

You don't really have to compile mplayer yourself. Just enable rpmfusion repository and

yum install mplayer

Now if this mplayer (probably located in /usr/bin/mplayer) has SOUND then you compiled it wrong ;-)

[vallimar]

You really, really need to pay more attention to the configure status output about what will/won't be compiled and install dependencies for the options you want. You should install alsa-libs-devel and pulseaudio-libs-devel (and dependencies) to get usable audio since I'm almost certain you aren't setup to use oss audio.

Until you get more experience with what sorts of things you will/won't need, you should install the source rpm packages and at least go over the spec file to get an idea of what options and dependencies a working build has/uses.

You should also learn how to build your own rpm's and install those, as mixing hand-compiled, loose packages with rpm's can lead to problems.

[rholme]

You hit the nail on the head. Although I had alsa installed, it was not finding it.

I had to install the alsa-devel package - then reconfigure and install

SOUND now works using alsa.

It is interesting that three installed packages require development versions in order for the configure script to work.

THANKS