Nope. In fact, what I did was to install (or re-install) esd with yast2. Once that was done, I did the ./configure and make bit for glame.

Would it be better to download esd and install from scratch, or is the yast2 route ok?

that might have been it. i know that the older suse distros didn't bother to take future compilation into consideration with thier package management. you can get esd from the gnome website - compiling it manually should do the trick if yast2 didn't get it.

I downloaded EsounD 0.2.8 and tried to install it. The ./configure seemed to work ok, but the make gave the output here below:

****************************
/bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -c audio.c
gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -c -fPIC -DPIC audio.c -o audio.lo
In file included from audio.c:28:
audio_alsa.c: In function `esd_audio_open':
audio_alsa.c:42: `snd_pcm_playback_params_t' undeclared (first use in this function)
audio_alsa.c:42: (Each undeclared identifier is reported only once
audio_alsa.c:42: for each function it appears in.)
audio_alsa.c:42: parse error before `params'
audio_alsa.c:76: warning: passing arg 1 of `snd_ctl_open' from incompatible pointer type
audio_alsa.c:102: warning: passing arg 1 of `snd_pcm_open' from incompatible pointer type
audio_alsa.c:136: structure has no member named `channels'
audio_alsa.c:147: `SND_PCM_OPEN_RECORD' undeclared (first use in this function)
audio_alsa.c:156: `params' undeclared (first use in this function)
audio_alsa.c:174: structure has no member named `channels'
audio_alsa.c:179: too few arguments to function `snd_pcm_file_descriptor'
make: *** [audio.lo] Error 1
****************************
If I understand the esd INSTALL file correctly, it is simply a matter of untar, cd to directory, ./configure, make and make install.
I once again installed EsounD from Yast2 and tried to install glame but ./configure pulls up with this message:
****************************
checking for ESD - version >= 0.2.0... no
*** The esd-config script installed by ESD could not be found
*** If ESD was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the ESD_CONFIG environment variable to the
*** full path to esd-config.
configure: error: GNOME needs esd library and development
********************************

If somebody can shed some light on this or point me in the right direction, it would be most appreciated.

Thanks
Joe

maybe alsa isn't working right. try ./configure --with-alsa=no or something similar

I tried it with ./configure --enable-alsa=no

The result was different from the previous times, but still no cigar. Here's the output:

esddsp.c: In function `open':
esddsp.c:172: `RTLD_NEXT' undeclared (first use in this function)
esddsp.c:172: (Each undeclared identifier is reported only once
esddsp.c:172: for each function it appears in.)
esddsp.c: In function `ioctl':
esddsp.c:373: `RTLD_NEXT' undeclared (first use in this function)
esddsp.c: In function `close':
esddsp.c:392: `RTLD_NEXT' undeclared (first use in this function)
make: *** [esddsp.lo] Error 1

Any ideas, help, addresses of psychiatrists, etc, etc?

Hi, Joe

I also use SuSe 7.3, and the first posts in this thread gave me the idea to try glame. I was lucky:
I only had to download and install the glame-0.6.3 tarball, previously satisfying its all dependencies (since I have a one CD SuSe installation, I had to download and install many rpms from the d1, d2, d3, gnm1, gnm2, gnm3, gnm4, gra2, snd1, snd2, xap2, xdev2 and xwm directories in the suseftp site), but nothing more.
It took no more than three days (cos my connection is sloooow), but the installation was smooth and glame works well on my SuSe 7.3.
I note here, that I also installed esound by the esound and esound-devel rpms found at the suseftp website.
I think your problem may be due to the esd installation, so, why do not you remove esd, and reinstall it by the esound and esound-devel rpms from suseftp? They worked for me.

Thanks mate, that sounds like good advice. I'll give it a shot.