LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   xmms ALSA plugin (https://www.linuxquestions.org/questions/linux-software-2/xmms-alsa-plugin-526860/)

merchtemeagle 02-08-2007 05:05 PM

xmms ALSA plugin
 
I'm using Slackware and build my packages from source by using pkgsrc. Now, when I want to compile xmms, I always get, at the end of the configure step:

Building ALSA plugin: no

What should I do to make sure this plugin is built?

Greenfuse 02-08-2007 05:20 PM

Don't know about pkgsrc but you might try looking in the INSTALL file of the xmms package for how to configure manually and select the appropriate options.

merchtemeagle 02-08-2007 06:15 PM

No, that's just a generic document. From examples I've seen, I think configure should pick it up that ALSA is installed and build the plugin automatically, but I'm not sure how it is searched for.

Greenfuse 02-08-2007 08:28 PM

does
Code:

./configure --help
from inside the unzipped xmms folder give any clues?

merchtemeagle 02-08-2007 08:48 PM

Code:

bash-3.1$ ./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE.  See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
  -h, --help              display this help and exit
      --help=short        display options specific to this package
      --help=recursive    display the short help of all the included packages
  -V, --version          display version information and exit
  -q, --quiet, --silent  do not print `checking...' messages
      --cache-file=FILE  cache test results in FILE [disabled]
  -C, --config-cache      alias for `--cache-file=config.cache'
  -n, --no-create        do not create output files
      --srcdir=DIR        find the sources in DIR [configure dir or `..']

Installation directories:
  --prefix=PREFIX        install architecture-independent files in PREFIX
                          [/usr/local]
  --exec-prefix=EPREFIX  install architecture-dependent files in EPREFIX
                          [PREFIX]

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc.  You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
  --bindir=DIR          user executables [EPREFIX/bin]
  --sbindir=DIR          system admin executables [EPREFIX/sbin]
  --libexecdir=DIR      program executables [EPREFIX/libexec]
  --datadir=DIR          read-only architecture-independent data [PREFIX/share]
  --sysconfdir=DIR      read-only single-machine data [PREFIX/etc]
  --sharedstatedir=DIR  modifiable architecture-independent data [PREFIX/com]
  --localstatedir=DIR    modifiable single-machine data [PREFIX/var]
  --libdir=DIR          object code libraries [EPREFIX/lib]
  --includedir=DIR      C header files [PREFIX/include]
  --oldincludedir=DIR    C header files for non-gcc [/usr/include]
  --infodir=DIR          info documentation [PREFIX/info]
  --mandir=DIR          man documentation [PREFIX/man]

Program names:
  --program-prefix=PREFIX            prepend PREFIX to installed program names
  --program-suffix=SUFFIX            append SUFFIX to installed program names
  --program-transform-name=PROGRAM  run sed PROGRAM on installed program names

X features:
  --x-includes=DIR    X include files are in DIR
  --x-libraries=DIR  X library files are in DIR

System types:
  --build=BUILD    configure for building on BUILD [guessed]
  --host=HOST      cross-compile to build programs to run on HOST [BUILD]

Optional Features:
  --disable-FEATURE      do not include FEATURE (same as --enable-FEATURE=no)
  --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
  --enable-one-plugin-dir  use a single plugin dir default=no
  --disable-user-plugin-dir disable per-user plugin dir
  --disable-dependency-tracking Speeds up one-time builds
  --enable-dependency-tracking  Do not reject slow dependency extractors
  --enable-static=PKGS  build static libraries default=no
  --enable-shared=PKGS  build shared libraries default=yes
  --enable-fast-install=PKGS  optimize for fast installation default=yes
  --disable-libtool-lock  avoid locking (might break parallel builds)
  --disable-glibtest      Do not try to compile and run a test GLIB program
  --disable-gtktest      Do not try to compile and run a test GTK program
  --disable-rpath        do not hardcode runtime library paths
  --disable-opengl        Disable OpenGL plugin(s) default=enabled
  --disable-esd          Disable esound output plugin default=enabled
  --disable-esdtest      Do not try to compile and run a test ESD program
  --disable-mikmod        Disable mikmod input plugin default=enabled
  --disable-libmikmodtest      Do not try to compile and run a test libmikmod program
  --disable-vorbis        Disable Ogg Vorbis input plugin default=enabled
  --disable-oggtest      Do not try to compile and run a test Ogg program
  --disable-vorbistest      Do not try to compile and run a test Vorbis program
  --disable-nls          do not use Native Language Support
  --enable-simd          build with x86 SIMD(3DNow!/MMX) instructions support (default=no)
  --enable-ipv6          enable IPv6 support (default=no)
  --disable-oss          disable the OSS output plugin
  --disable-alsatest      Do not try to compile and run a test Alsa program

Optional Packages:
  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  --without-PACKAGE      do not use PACKAGE (same as --with-PACKAGE=no)
  --with-dev-dsp=path    Path to OSS DSP data pipe, default is /dev/dsp.
  --with-dev-mixer=path  Path to OSS sound mixer, default is /dev/mixer.
  --with-cdda-device=path Path to default cdaudio device.
  --with-cdda-dir=path    Path to default cdaudio directory.
  --with-gnu-ld          assume the C compiler uses GNU ld default=no
  --with-pic              try to use only PIC/non-PIC objects default=use both
  --with-glib-prefix=PFX  Prefix where GLIB is installed (optional)
  --with-glib-exec-prefix=PFX Exec prefix where GLIB is installed (optional)
  --with-gtk-prefix=PFX  Prefix where GTK is installed (optional)
  --with-gtk-exec-prefix=PFX Exec prefix where GTK is installed (optional)
  --with-x                use the X Window System
  --with-libiconv-prefix[=DIR]  search for libiconv in DIR/include and DIR/lib
  --without-libiconv-prefix    don't search for libiconv in includedir and libdir
  --with-esd-prefix=PFX  Prefix where ESD is installed (optional)
  --with-esd-exec-prefix=PFX Exec prefix where ESD is installed (optional)
  --with-libmikmod-prefix=PFX  Prefix where libmikmod is installed (optional)
  --with-libmikmod-exec-prefix=PFX Exec prefix where libmikmod is installed (optional)
  --with-ogg=PFX  Prefix where libogg is installed (optional)
  --with-ogg-libraries=DIR  Directory where libogg library is installed (optional)
  --with-ogg-includes=DIR  Directory where libogg header files are installed (optional)
  --with-vorbis=PFX  Prefix where libvorbis is installed (optional)
  --with-vorbis-libraries=DIR  Directory where libvorbis library is installed (optional)
  --with-vorbis-includes=DIR  Directory where libvorbis header files are installed (optional)
  --with-included-gettext use the GNU gettext library included here
  --with-libintl-prefix[=DIR]  search for libintl in DIR/include and DIR/lib
  --without-libintl-prefix    don't search for libintl in includedir and libdir
  --with-alsa-prefix=PFX  Prefix where Alsa library is installed(optional)
  --with-alsa-inc-prefix=PFX  Prefix where include libraries are (optional)


studioj 02-08-2007 09:11 PM

if the configure script finds alsa headers and libs basically alsa develpement environment then plugin gets YES

merchtemeagle 02-08-2007 09:28 PM

Quote:

Originally Posted by studioj
if the configure script finds alsa headers and libs basically alsa develpement environment then plugin gets YES

The ALSA-headers, are those the files in my kernel source tree under include/sound ?

studioj 02-09-2007 02:04 PM

/usr/include/alsa
they are the interface to libasound

Greenfuse 02-09-2007 03:56 PM

What do you see under "checking for ALSA LDFLAGS" in config.log?

What version of alsa are you using? Xmms wants 0.9 or higher.

merchtemeagle 02-09-2007 10:57 PM

Quote:

Originally Posted by studioj
/usr/include/alsa
they are the interface to libasound

That directory doesn't exist on my system.

merchtemeagle 02-09-2007 10:58 PM

Quote:

Originally Posted by Greenfuse
What do you see under "checking for ALSA LDFLAGS" in config.log?

What version of alsa are you using? Xmms wants 0.9 or higher.

Code:

configure:15883: checking for ALSA LDFLAGS
configure:15896: result:  -lasound -lm -ldl -lpthread
configure:15900: checking for libasound headers version >= 0.9.0
configure:15969: gcc -c -O2 -march=athlon-xp -I/usr/pkg/include -DGLX_GLXEXT_LEGACY -I/usr/include -I/usr/pkg/include/freetype2 -DHAVE_ICONV_OPEN=1 -I/usr/pkg/include -DGLX_GLXEXT_LEGACY -I/usr/include -I/usr/pkg/include/freetype2 conftest.c >&5
configure:16002:28: alsa/asoundlib.h: No such file or directory
configure:16030:12: #error not present


merchtemeagle 02-10-2007 09:36 AM

When configuring xmms with
Code:

./configure --with-alsa-inc-prefix=/usr/pkg/include --with-alsa-prefix=/usr/pkg/lib
the plugin is built. Thanks for the help everyone.


All times are GMT -5. The time now is 03:30 PM.