On 11 July 2008 at 7:59, Paul Davis <paul(a)linuxaudiosystems.com> wrote:
PACKAGERS and SOURCE BUILDERS please note that this
release sees a new
library dependency. Ardour 2.5 requires the aubio library, which is
small and fast to build. Many distributions do not currently package it.
You know what to do ...
Yup. I downloaded, ./configure'd, and ran make. The end of my
configure log looks like this:
**************************************************************
Summary:
Fftw3: yes (using fftw3f)
Libsndfile: yes
Libsamplerate: yes
JACK: yes
ALSA midi: yes
Lash: no
PureData: no
**************************************************************
Configuration completed successfully. Type 'make' to build aubio
After ~220 lines of make log, make errors out like this:
Making all in aubio
make[2]: Entering directory `/home/local/src/INCOMING/BUILD/aubio-0.3.2/python/aubio'
if /bin/sh ../../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../src -Wall
-Wextra -Wno-missing-prototypes -Wno-missing-declarations -Wno-strict-aliasing
-I../../src -I../../src -I../../ext -I/usr/include/python2.4
-I/usr/local/include/python2.4 -I/usr/include -I/usr/local/include -g -O2 -MT
aubio_wrap.lo -MD -MP -MF ".deps/aubio_wrap.Tpo" -c -o aubio_wrap.lo
aubio_wrap.c; \
then mv -f ".deps/aubio_wrap.Tpo" ".deps/aubio_wrap.Plo"; else rm -f
".deps/aubio_wrap.Tpo"; exit 1; fi
mkdir .libs
gcc -DHAVE_CONFIG_H -I. -I. -I../../src -Wall -Wextra -Wno-missing-prototypes
-Wno-missing-declarations -Wno-strict-aliasing -I../../src -I../../src -I../../ext
-I/usr/include/python2.4 -I/usr/local/include/python2.4 -I/usr/include
-I/usr/local/include -g -O2 -MT aubio_wrap.lo -MD -MP -MF .deps/aubio_wrap.Tpo -c
aubio_wrap.c -fPIC -DPIC -o .libs/aubio_wrap.o
aubio_wrap.c:112:20: error: Python.h: No such file or directory
aubio_wrap.c:719: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before
â*â token
All the rest of the errors look related to a missing Python.h.
I've looked all through my distribution (Mandriva 2007.0) package
file list and can't find a file of that name.
Where *should* Python.h come from? Maybe my installation is broken.
At least it seems incomplete somehow.
I've looked through the entire (short) aubio mailing list archives
for this, and didn't find anything that applies.
I looked through the ./configure --help to see if there was a way to
avoid depending on Python.h, but I didn't find anything obvious.
Any ideas on how to get aubio to finish compiling?
Thanks....
--
Kevin